Testing New Pro Version on Dev Server Per Your Instructions

[gcasst]

We bought the pro version so we could have recurring events. Now we’re being told to upgrade or else BUT to test the upgrade on a dev site. How can we do that when you require a license key to upgrade and that license key is only good for one site?

I’m also disturbed by the number of errors this upgrade has caused other users, as evidenced by the posts on this forum. Not inclined to update now if there are going to be costly errors in your code…. Updates should be quick. If you’re going to make us go through hoops like some other pro plugin developers that I no longer use, well, you can see where this is heading….

So to return to the question, please tell me how to test this 4.1 update on a dev server. We can’t afford to take chances with our client on this one. The calendar is central to their site.

[Cliff]

Hi Lise. Thanks for sharing your concerns in a candid yet polite manner.

I hope to provide you with information that helps you pull off fantastic results for your client.

===

Please reference Using one license for your live and dev sites.

Additionally, it’s always best practice to have some setup like a testing/staging version of your site and the production version of your site. The workflow would be to update and manually test (click through, create new events, general quality assurance stuff) on your staging site and if all looks like it’s working on your specific site with your specific setup (theme, active plugins, code customizations)… then update your production site.

Some web hosts make this setup easier to pull off. Some people just don’t want to mess with this. I don’t know your scenario or preferences, but I wanted to share this best practices information.

Our Manual Updates page has a bit more “warning, warning, warning!” backups verbiage than our Automatic Updates page, but backups are always a good idea even if updating automatically.

===

As far as the quality and safety of our updates, no software can be guaranteed to be perfect for all use cases and customization scenarios. However, we spend a lot of effort automatically and manually testing each release.

While we probably won’t ever be “bug free”, we take it seriously and regularly release maintenance updates to squash as many bugs as possible.

===

Thanks for your attention to detail with all this information. Please let me know if there’s anything more I can do for you.

[gcasst]

Gotcha, so I should browse this site for the software and install it manually on the dev side and test it there. I was so focused on switching the license to get the auto update working that it didn’t occur to me to look for downloads here. I found and downloaded it and will test before I try to install it on the live site. This isn’t practical for a lot of plugins all the time, but I’ll do it on this one (we manage a lot of web sites and none of them pay particularly well…..)

Hopefully, it all goes smoothly. The calendar has been problematic for these clients since the beginning so I was hoping this would be quick and easy, but no. 😉

That said — thanks for your help! I do appreciate it.

[Cliff]

Glad to help where I can. Support doesn’t have control over development or QA testing, but they do listen when we speak up to share users’ experiences.

We’re always trying to do well for everyone. I hope your experience with our products improves over time.

[Support Droid]

This topic has not been active for quite some time and will now be closed.

If you still need assistance please simply open a new topic (linking to this one if necessary)
and one of the team will be only too happy to help.

[Author]

Posts