NOTICE: We've Moved to a Ticket System for Support
As of August 31, 2017 (12am EST) our support forums will be retired (read-only), and we will be moving to a support ticket system. This will allow us to better organize and answer support requests, and provide a more personalized experience as we assist our customers.
For the time being, we will leave our forums open for reading and learning while we work on creating a more robust Knowledge Base for everyone to use.
If you are a WC Vendors Pro customer please open a support ticket here. If you are a WC Vendors user please open a support ticket on the Wordpress.org forums.
The information on this forum is outdated and in most instances no longer relevant. Please be sure to check our documentation for the most up to date information.
Thank you to all of our customers!
- This topic has 1 reply, 2 voices, and was last updated 7 years, 2 months ago by
.
-
Posts
-
@ben
I had thought this discussion is best under its own topic. I had read your comment to this in this threadand I wanted to follow up on this.
What is the downside to having the WC Pro licence activated on the DEV server instead of the LIVE server? With my set up I can only do code and plugin updates on my DEV site server and then those changes are migrated over to the LIVE site server.
Do you see any issue with this set up? Is it critical that the licence be activated on the LIVE site?
Thanks a bunch.
@thrivinglocally
Nothing– really. As long as you are ok with doing the Pro updates manually on your live site.
If you first test out updates in your dev environment (recommended for any plugin , theme, change..) then it is fine to activate it there if you prefer.
Without the license you can’t get automatic updates or notifications of updates to Pro (you can subscribe to the updates forum topic for Pro for a notification). But you can manually update. And the red box will nag you to enter your license key.
- The forum ‘WC Vendors Pro Support’ is closed to new topics and replies.