Tagged: x
-
AuthorPosts
-
July 29, 2016 at 11:42 am #1109049
JoaoModeratorHi There,
It will be updated.
Hope that helps,
Joao
July 29, 2016 at 11:47 am #1109057
goalsarecoolParticipantThis reply has been marked as private.July 29, 2016 at 12:00 pm #1109067
RahulModeratorHey There,
The current version of WooCommerce will automatically be updated with the one which you want i.e. 2.6.3.
Hope that helps!
July 29, 2016 at 12:41 pm #1109119
goalsarecoolParticipantDid you see the error message I sent? Are you saying I should just ignore the error message because when I go back to plugins it still says v 3.6.2
July 29, 2016 at 6:59 pm #1109541
Rue NelModeratorHello There,
The supported version of WooCommerce in X 4.6.1 is WooCommerce 2.6.3. You can check the plugin compatibility with X by visiting this link: https://community.theme.co/kb/version-compatibility/
There is no need to install another version because it is already installed. What you need is just an update. You can simply hit the update button right in your Plugin section and find the WooCommerce. (http://prntscr.com/bza98g)
To know more how you can update WooCommerce, please check out the documentation:
https://docs.woocommerce.com/document/updating-woocommerce/Hope this helps.
July 29, 2016 at 7:13 pm #1109552
goalsarecoolParticipantTHAT DOESNT WORK! When i click the update button it updates to version 2.6.4 not 2.6.3
July 29, 2016 at 9:39 pm #1109748
John EzraMemberHi there,
Thanks for updating the thread! I have gone and read each post from the beginning. It seems that you had and issue where WooCommerce released and update v2.6.4 recently while most of the team were still on 2.6.3, thus suggesting to just update regularly. I apologize for the confusion this has caused you.
To install a version manually, you can do two things. One is to delete the old plugin and install the new one. Or if your folder permissions permit it you can install the new version over the old one only overwriting the the needed files. Either way you will want to have a back up in case something goes wrong during manual update.
You can leave it at v2.6.4 as well as long as there is nothing that is causing an incompatibility error. Once we are able to do and update on our end, we will update compatibility soon. You only really need to roll back when something is explicitly not working. Some updates from third party integrations work fine unless they changed something major.
I also went back to the original question and it seems WooCommerce is working fine and the issue you have is an email sent to you asking you to activate your subscription?
Would you mind providing a screenshot of this email or wherever this came up? Did you install any WooCommerce extensions or any third party extensions that integrates with WooCommerce?
The main WooCommerce platform is free and we have integration with it so X will take over styling but WooCommerce should still function normally. There is no subscription needed. If you did add an extension which require purchase or a subscription, then you will get this message. Usually you will have already purchased before you are able to download and install a paid extension. Then you would just need to verify / activate it and you’re good to go, unless you downloaded a demo or trial version where you need to purchase / subscribe to unlock or to continue using.
If it is that case, then this is something you will need to work out with WooCommerce directly as X and Theme.co have no control over this.
If after reading the above, you don’t have any third party extensions to WooCommerce, please check if the email was pertaining to this site or if it meant other sites you may own. If you feel that it really is this site and something is definitely wrong, then please provide us with login credentials so we can take a closer look. To do this, you can make a post with the following info:
– Link to your site
– WordPress Admin username / password
– FTP credentialsDon’t forget to select Set as private reply. This ensures your information is only visible to our staff.
Thanks and again we apologize for the confusion.
-
AuthorPosts
- <script> jQuery(function($){ $("#no-reply-1091848 .bbp-template-notice, .bbp-no-topic .bbp-template-notice").removeClass('bbp-template-notice'); }); </script>
