Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Key re-assignment | Event Espresso - Staging Server
I recently purchased the Business License for this plugin and installed it on our Development domain so we can continue build-out for the client. We ran into some issues with the WP theme we had installed, as well as the WP installation itself. For a number of reasons, it was best to scrap that dev site and start fresh using this plugin for the “core” features (as opposed to an “event” based theme with the plugin handling some of the features.)
When I attempt to “reset the license key” to the new url/domain/installation, (which is merely a different folder on the same domain) the system prompts me to pay $10 to do so. While I understand that there may be some work required on the back end to accomplish this, it seems like most installations would require it, as devs generally develop and test on a development installation, and later move it to the live site. It seems like I’m getting “nickeled and dimed” to death with this plugin; everywhere I turn there’s a buy it now button! Maybe the key isn’t needed on the dev server, though your documentation doesn’t delineate that. If such is the case, it would be a good idea to notify the devs that they should not install the key until it gets to it’s final home. The problem with this is that you are prompted from the dashboard to insert it in order to update the plugin – and the verbiage in the prompt makes it sound like the plugin is already outdated and requires updating. If I am developing a site using your product, of course I want it updated!
Am I missing something here?
This topic was modified 12 years, 4 months ago by nine.
The support post ‘Key re-assignment’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.