[Larry KParticipant]

hello,

what is Themeco’s thoughts on how frequent or updated the ‘supported’ or ‘compatible’ version of Woo can be run?

Because woo is extremely important (commerce = sales = client site making money)…

what do to when woo has update and X is not supporting it?

curious about Themeco’s thought on the woo topic 🙂

thanks

[DarshanaModerator]

Hi there,

Thanks for writing in! Latest compatible versions can be viewed from the following link (https://community.theme.co/kb/version-compatibility/).

Also make sure to check our changelog (https://theme.co/changelog/).

Thanks!

[Larry KParticipant]

thanks… BUT was looking for more about the “concept” or a discussion on priorities?

as you know:
currently 2.6.4 is support of Woo,
but 2.6.7 is latest Woo

As a concept, what if for example:
woo 2.6.6 solved a problem for my site (which was causing me to loose money)…

do you see why I’m bring this up?

Then, what if upgrading (for example) to a non supported version of woo, caused
another problem? IN that situation, the site would loose money both way?

So, I wanted to inquire about the issue of upgrading for “money loosing” plugin priority…
plugins like woo (i would say deserve a VERY, very high place in the priority list)

thanks

[DarshanaModerator]

Hi there,

We usually run a compatibility check before recommending the latest update. Also our developers will consider special security issues and patches when a particular update is released and based on that we recommend to update on our changelog.

However as you may understand, there is simply no way to account for all of the potential variables at play when using another developer’s plugin or script. In such cases, it is best to contact the original plugin developer for speedy recovery.

Thank you for your understanding.

[Larry KParticipant]

so if I understand you correctly,

Themeco will or could “speed up’ the compatibility check, IF a security issue arises…
but you don’t mention anything else?

So while I agree “security” is a very important feature in both X theme, as well as the 3rd party plugins X theme support.

I’m confused on your statement about “…it is best to contact the original plugin developer for speedy recovery.”

Let me restate my concern:

X theme releases its updates based on MANY things/variables. (more than I could imagine)

X Theme users (website owners who buy X) who use X theme to run their company websites.
These same users also rely on Woo Commerce to generate revenue for their company.

So technically, a company who uses X and Woo… rely on both to stay in business.

As of right now, X supports Woo 2.6.4, but Woo 2.6.7 is the latest.
So that means X is 3 versions behind.

While I understand there might not be a ‘security’ issue at stake. So
there might not be a security reason to upgrade Woo, more than likely,
there is functionality that is causing loss of revenue in not upgrading.

I’m saying Woo has a much higher priority than other plugins, due to its nature.
Woo is directly related to revenue.
As opposed to say a 3rd party photo gallery plugin.

I REALLY HOPE that Themeco does not treat Woo as an equal to all other 3rd party plugins.

What type of priority does Themeco place on Woo, compared to other plugins?

thanks

[JackKeymaster]

Hi there Larry,

If there is either a security issue or a feature issue. i.e, core functionality of a plugin not working for any reason, we will always give higher priorities to those.

For example quite a few versions back now Woo had an issue with payment gateways and checkouts not working. This was a WooCommerce core issue, as soon as they released an update, we checked compatibility and updated that we were compatible with the latest version.

WooCommerce and X is a bit different to most of our other extensions. When you install WooCommerce via X > Addons. It just installs the normal version of WooCommerce from WordPress.org. X has integration files for WooCommerce with custom styling and custom templates. Sometimes when WooCommerce release an update we need to update these files if they say changed the CSS classes used or similar.

However, it is extremely rare for any WooCommerce update to break X in anyway. Even if the version compatibility isn’t officially marked as the latest you shouldn’t encounter any issues when using the latest version of WooCommerce in X.

We monitor the WooCommerce development blog, trac and release notes to make sure we’re aware of and on top of any potential issues that could be caused in X due to a WooCommerce update/release.

I hope this helps clear everything up and if you have any questions or would like any clarification please don’t hesitate to ask.

Thank you!

[Larry KParticipant]

ahhh… thank you for the details 🙂

so just to be clear…
1) if I upgrade to the lastest woo version — because of how the integration is done between X and Woo, I should not have issues with X?
2) in general, X is always watching out for “security issues”

are those 2 correct or do you agree with those?

thanks

[RadModerator]

Hi there,

1. It depends on many conditions. If the update contains different standard and implementation from its previous version then it may break (eg. major updates and core changes). But if it’s only the usual updates, then it should be okay.

Our recommendation is to always test the update on a staging site. In some case, Woocommerce released a major update and it breaks everything, including theme integration, builders integration, and even causes WordPress core incompatibility (for users that are still depending on the older version of WordPress, and upgrading the WordPress core may break other plugins that aren’t yet compatible with the latest one). It’s a chain of effect, testing is always a must.

Check the updates if it only contains minor changes, if it’s, then should be okay to update it directly.

The complexity of the issues are varying in different levels, but we always set priorities depending on its seriousness.

2. Yes, we do. 🙂

Thanks!

[Larry KParticipant]

Thanks again!!!!

I was going to add a new topic, BUT i decided to add it here — 🙂
as I’m confused on where to go for help on this issue?

1) I believe the issue started after I upgraded (currently on Cornerstone 1.3.3 and woo 2.6.7)

— i also upgraded my gateway: Braintree For WooCommerce 2.5.2

2) situation: after the address is updated, the order/payment part of the screen refreshes.
sometimes, the refresh is delayed (which causes problems for the unsuspecting buyer)

maybe an issue when the CC is being typed in and the section refreshes 🙁

3) gateway support said this is how WOO works… (ajax is updating) and not much can be done???
but like I said… i don’t remember that happening before?

thanks

[ChristianModerator]

Hey Larry,

This is more likely an issue with your gateway’s compatibility with WooCommerce. Please try using PayPal or other payment methods that is supported out of the box by WooCommerce and check if the issue persists

Thanks.

[cgWerksParticipant]

Just to be clear… if a newer version than bundled is shown on that version compatibility KB link above, we’re fine to install that updated version? I’m assuming that is what that means, but just wanted to be sure.

From a UX perspective, I wonder if something could be done. It’s typical best-practice to keep everything updated. So, it’s odd to leave certain plugins un-updated. And, if you aren’t following the forums and KBs and such, how would a new X user (or a site admin who isn’t so familiar with X) even realize they shouldn’t update to the latest of everything?

I don’t know the answer to that, but it’s something to think about.

I know a new version of X and Cornerstone are coming along… but it also seems things have slowed a bit in terms of keeping up with the compatible plugins. As Larry indicated, WooCommerce is of crucial importance to many of us… and keeping the templates and compatibility up to date is very important to us.

[RadModerator]

Hi there,

Yes, those will be compatible with X theme. But there is no assurance to be compatible with other plugins and even WordPress version ( if ever WordPress releases new version and user updated their core ).

The update is good if its purpose is for security and compatibility fixes. Updates are what most sites cause of breaking, it should be done in a test environment first. WordPress is not the same as other software where all the features are made by a single group of developers, or a single author. WordPress is a system where theme and plugins are made by different developers not related to each other, different standards and incompatibility has a high chance of occurrence.

Hence, maintain your site with caution and do it in a test environment. Do not engage on any update not yet tested on your existing site. There are many contributing factors that can cause issues during the update.

Thanks.

[Author]

Posts