Since 7 out of 10 times an X Theme update breaks a site to some degree can we do one of two things?
- Not push out releases through Wordpress Updates that are not considered near stable. These very beta update releases should live on Apex as a download for people who want to test.
- Add a note to the validation page that states what the current release is and what the stable release is like on the download page in Apex?
I am a long time X Theme user with many sites running X and Pro. I hold 22 licenses of this theme and have 15 more licenses that clients have purchased directly. This has been a long time issue with Theme.co that is not often present in other developer themes.
If this information is elsewhere, I suggest making some changes to make it more apparent to the user.
For example, I just updated a site to the latest version through a standard Wordpress update and it broke all images that were in a Cornerstone element. How does that happen? I don’t understand how an update gets pushed with such an oversight. If this was the first time it happened to me I would not be complaining. It’s been an issue for years with updates.
At the very least, test more and if a crazy bug exists, take it down and send an email to everybody.
I know that this was not simply an issue with one site as I reproduced the error with 3 other sites with the same results. It’s not a plugin conflict as I also tested with all plugins disabled except for Jetpack.
Still love X Theme and will continue using it. Just have to keep on learning what to watch out for with this theme.
I rolled back to 6.2.5 easily since I use a child theme. Lost about 30 minutes chasing down the problem assuming it was due to a plugin issue.