I'm a toolset contractor, and I've been working with a couple of clients each of whom have single-site toolset licenses.
I like to work with staging sites when I'm making changes, and I consider this a 'best practice'.
When I create a staging site for these clients, their license key from the main site does not work on the staging site, and it's not possible to generate a second key because they only have single site license. In one case i added the staging site to my own lifetime account to get around this, in the other we worked on the live site. Neither of these workarounds is acceptable.
I suggest you find a way to support staging sites even on the single-site plan. One easy way to do it would be to permit creation of temporary keys, maybe good for a week or so -- even 24 or 48 hours would help. We need to encourage users to test changes before they are live.
This is a valid idea, yes, but the Toolset does not require registration to be used in a staging site.
You can just activate and develop, and actually, if you do that for a client, it's fine to have your own key for this staging site, and remove that once you deliver the project.
Does that help?
I've been working with it based on what you describe and it is a hassle. My workflow involves re-creating the staging site frequently after integrating my changes into the live site. Every time I re-stage I have to re-register Toolset. Further, if the client later chooses to work on her own she'll not be able to create a staging site that can have updates. I think this is a big flaw in your licensing model.
Hi, Beda manages feature requests, so I will ask him to follow up with you here shortly regarding your suggestion to create temporary keys. I understand it's inconvenient when only one environment can receive automatic updates. The current supported workflow is to download any plugin updates directly from https://toolset.com/account/downloads and install them manually on an unregistered development or staging site.
I agree there is room for improvement and invited our responsible personnel to take a look at it.
However, as illustrated in my previous post, this can be easily avoided currently (the need to register Toolset to have it "working").
I will let you know here if there are any major decisions or feedbacks.
Thank you!
I still find this cumbersome. Among the ways to fix it would be a temporary key setup or extension of key use to include the entire domain rather than just the main site.
Yes, our developers will look into it, as previously stated.
It is however not possible to me to grant or state what we will do exactly.
I can update this thread once I have better news.
