[necxelosParticipant]

Complete error code below:

Fatal error: Uncaught Error: Class ‘X_Update_API’ not found in C:\xampp7\htdocs\GaS_RC_01\wp-content\themes\x\framework\functions\global\admin\addons\updates\class-plugin-updater.php:205 Stack trace: #0 C:\xampp7\htdocs\GaS_RC_01\wp-includes\class-wp-hook.php(300): X_Plugin_Updater->custom_plugin_update_row(‘x-content-dock/…’, Array) #1 C:\xampp7\htdocs\GaS_RC_01\wp-includes\class-wp-hook.php(323): WP_Hook->apply_filters(”, Array) #2 C:\xampp7\htdocs\GaS_RC_01\wp-includes\plugin.php(453): WP_Hook->do_action(Array) #3 C:\xampp7\htdocs\GaS_RC_01\wp-admin\includes\class-wp-plugins-list-table.php(865): do_action(‘after_plugin_ro…’, ‘x-content-dock/…’, Array, ‘all’) #4 C:\xampp7\htdocs\GaS_RC_01\wp-admin\includes\class-wp-plugins-list-table.php(536): WP_Plugins_List_Table->single_row(Array) #5 C:\xampp7\htdocs\GaS_RC_01\wp-admin\includes\class-wp-list-table.php(1213): WP_Plugins_List_Table->display_rows() #6 C:\xampp7\htdocs\GaS_RC_01\wp-admin\includes\class-wp-list-table.php(1141): WP_List_Table->display_rows_or_placeh in C:\xampp7\htdocs\GaS_RC_01\wp-content\themes\x\framework\functions\global\admin\addons\updates\class-plugin-updater.php on line 205

Circumstances:
After a while I came back to making my site (I took a long break from it because I had other work) and I decided to make fresh installation of everything on my XAMPP. This includes newly downloaded WordPress, X Theme, X Child Theme and all X Extensions (from my ThemeForest account).

Everything step of my installation works fine until I actually activate X Theme or X Child Theme. At this point instead of all X-named X Extensions in my plugins tab (which I also installed one by one manually) I get this error at the bottom of the page.

I tried to reinstall everything from scratch several times, even re-downloaded all files but it didn’t help. It happens sooner or later. Error vanishes when I activate any other theme (default WP Twenty Seventeen for example) but is back again after switching to X.

I’ve never had this error before (between few months ago and a year ago – this was the time interval during which I worked on my site).

Side information (in case it matters):
– Several X Extensions inform me that they are outdated, even though I downloaded latest package from my ThemeForest account.
– For some reason error affects only X-Named X Extensions. Other X Extensions don’t seem to be affected.
– I work on localhost.
– I use newest possible stable version of XAMPP (which is a 7.1.1 PHP version currently).

[EDIT]:
I just ran my previous installation from few months ago (old XAMPP from that time, old versions of WP, X and all Plugins also from that time) and error is there too. I mean the site seems to work but X-named plugins are unaccessible because of that error.

[RupokMember]

Hi there,

Can you confirm that you are fully updated? (Theme and Plugins)

You can find the latest version numbers here: (http://theme.co/changelog/) Then you can compare them to what’s installed on your site.

If you find anything to be out of date, you can review our update guide.

[necxelosParticipant]

X Theme – 4.6.6 = FULLY UPDATED!
Cornerstone – 1.3.3 = FULLY UPDATED!

X – Under Construction = Not Updated!
X – White Label = Not Updated!
X – Disqus Comments = Not Updated!
X – Content Dock = Not Updated!
…also several 3rd party plugins (out of those included in X Package) are outdated too. All 13 X-named extensions are unaccessible when X Theme is used though – not just those outdated.
Those are all files I downloaded in newest available package on ThemeForest. Based on Your update guide, X-Package on ThemeForest should have all the recent versions of plugins, which doesn’t seem to be true in this case.

Is this possible that some Extensions (not the Theme or Cornerstone) being outdated (by not much) can cause this error affecting other extensions aswell? How does my localhost setup know that they are outdated in the first place?

It’s just a wild guess but it looks to me like something is wrong with Your DRM (term taken from gaming industry – no idea how You call it guys), which doesn’t seem to accept the fact that I’m not validating (because localhost, because it’s not obligatory and because I don’t want to).

Thanks in advance for help 🙂

[EDIT] I just confirmed that this error doesn’t appear until wordpress does the check for updates. I reinstalled once again and managed to do some stuff, then I clicked “updates” in my WP backend and after it checked for updates error appeared. It seems like it does this check on its own too so my “how does it know” side-question is obsolete.

[JadeModerator]

Hi there,

Is there chance that you could upload a copy of the site you are working on and provide us with the admin and the FTP details so that we could check it?

This would help us check the current setup easier.

Thank you.

[necxelosParticipant]

Sadly I don’t have any way to do it.

But the issue is very easy to replicate (like 5 minutes tops). I already did replicate it over 15 times to check for any conflicting things. Steps:
– Install XAMPP with php 7 or higher,
– Install WordPress, newest version,
– Install X Theme, newest version, downloaded from https://community.theme.co/dashboard/ ,
– Install Cornerstone, from unpacked X file, downloaded from https://community.theme.co/dashboard/ ,
– Install X-named Extensions, unpacked from X Package file, downloaded from https://themeforest.net/ ,
– Click “updates” tab in WordPress,
– Done, the error is at the bottom of Plugins tab in WordPress.

[EDIT] In the meantime: this will be a temporary fix (as the problem will appear again after any plugin gets updated again), but could You please update the X Package on ThemeForest to include latest versions of all extensions?

[JadeModerator]

Hi there,

Thanks for updating.

The plugins are mostly up to there but there may be some instances that we don’t push the latest version of a bundled plugin from a third party vendor because we have to do some extensive compatibility testing with X but whenever we push updates, you should be able to keep track through our changelog here: https://theme.co/changelog/

[necxelosParticipant]

I’m talking about X-named plugins (as in Your own plugins, not 3rd party ones, as they seem to be the reason for error).

And changelog is of no use to me if I can’t download manualy latest versions of those plugins. Your update guide clearly states that I should be able to get latest updates both automatically and manually.

Actually figuring out the real reason error appears would be still prefered though 🙂

[JoaoModerator]

Hi There,

Please try deleting and re-installing the plugins.

Let us know how it goes,

Joao

[necxelosParticipant]

Uninstalled those 4 plugins (not up-to-date ones out of Your own extensions only):
X – Under Construction
X – White Label
X – Disqus Comments
X – Content Dock
and error disappeared, which means I can access and see all other X-named plugins.

After installing even single one of them again – error is back. Error message seems to be “covering” anything that is below it, so if for example X – Content Dock is installed, error covers most of X-named plugins. That’s why I said earlier that it makes other plugins inaccessible.

Sadly even in the case of just those 4 plugins causing the error it still wouldn’t be fine, because I need to use them. I still believe it’s not the case though – to me it seems like non-validated X refuse to tolerate non-updated X-named plugins.

P.S. As it seems figuring this out will take some time on both my side and Yours, could You please update x-package on ThemeForest with latest versions of all extensions? This would allow me to continue working on the site for the time being (as in – before we are able to solve the actual underlying problem).

Thanks in advance and good night 🙂

[JoaoModerator]

Hi There,

You can download the latest version from our dashboard:

Dashboard

Let us know how it goes,

Joao

[necxelosParticipant]

Maybe it’s a stupid question but can You point me to where on Your dashboard is a download for that? Because all I see there is main X Theme and Child X Theme, none of which have extensions package included and that’s what we were talking about here.

Thanks in advance 🙂

P.S. Any news/ideas on the error?

[DarshanaModerator]

Hi there,

Sorry for the confusion. You will need to validate your X theme first in-order to install those extensions.

If you’re using Windows, try installing WAMP server and set up your WordPress site again and see if that works for you. If you’re on Mac, you can use MAMP.

Make sure to download the latest version from your ThemeForest account.

Let us know how it goes.
Thanks!

[necxelosParticipant]

Ok, one thing at a time then:
a) I’m already working using XAMPP, prefer it over WAMP due to the fact that I’m already familiar with it and I like it. It doesn’t matter though as those 3 tools are basically identical to each other, apart from the fact that XAMPP is multi-platform tool while WAMP and MAMP are platform-specific. Unless You suggest XAMPP is the reason for error – please clarify that.

b) I already downloaded all latest files available which I stated in both initial post and several other posts. I have most recent x-package from ThemeForest, I have most recent x and x-child from Your dashboard. Sadly extensions included in x-package aren’t recent by any means with 4 of Your own extensions (I called them x-named extensions throughout this topic) being outdated along with several 3rd party ones (which I did mention only once by now because they don’t seem to take any part in the error).

c) I did install-everything-from-scratch, reinstall-plugins-one-by-one and even tried different versions of PHP – all that dozens of times by now and still only answer I get from any of You guys is “try to reinstall”. I don’t know how am I supposed to respond to that? Error is still there…

d) Validation isn’t mentioned as obligatory in any of Your guides, quite the opposite. Being able to manually install everything was a strong selling point for me (as I have personal grudge and crusade against any form of DRM from my experience with games).

https://community.theme.co/kb/product-validation/
In this article we’ll take some time to discuss product validation in X and the benefits that come along with it. You do not need to validate your product in order to continue using it (will simply need to update the theme manually)

https://community.theme.co/kb/updating-your-theme-and-plugins/
We highly recommend using Automatic Updates (above), please use this method whenever possible. Manual updates are still possible. This requires that you obtain the latest zip file for the product you are updating.

So being forced to validate by an error isn’t solving a problem in any way. I may post my purchase code here though, if You’re suggesting I did not buy it, because that’s exactly how I feel treated now.

Thanks in advance and please, be so nice as to respond to the whole topic, not just the last post this time 🙂

[Rue NelModerator]

Hello There,

Thanks for updating in! It does not matter whether you use WAMP or XAMPP or MAMP if you are using Mac. This is just a tool to run Apache and MySQL in your local machine. Whatever you have, I am sure it is working well and has the minimum requirements to run WordPress as stated here: https://wordpress.org/about/requirements/

The bundled X plugins in the x_package.zip file may not be updated. The best way to get the all the latest X plugins is by installing it from X Addons > Extensions. However, before you can install it, you will need to validate X so that you can connect to out plugin server. Only validated sites can connect to our plugin sever and this is why you must validate X. You can always revoke the validation once you are done install the necessary X plugin so that you can re use X in your other site if you have to. You can always use X in multiple times for you site. It’s just that you can connect connect to our plugin server one at a time so that you can get automatic updates.

Did you happen to take notice which of the X plugin when activated displays the error? Based from the error above, it seems that it is coming from X Content Dock. Please be advised that the latest version is 1.1.0. To save you from trouble, I have attached the latest version in zip file so that you can try and install this manually.

Hope this helps. Please let us know how it goes.

[necxelosParticipant]

Thank You for Your answer Nel 🙂

Let me refer to what You said by quoting You directly (it will be easier for me to answer this way):

Did you happen to take notice which of the X plugin when activated displays the error?

Yes and no.
Yes I did notice which plugins cause the error. Each of those 4:
X – Under Construction
X – White Label
X – Disqus Comments
X – Content Dock
No error isn’t caused by activating the plugin but just by installing it. It still causes error, just by being there.

To save you from trouble, I have attached the latest version in zip file so that you can try and install this manually.

Thank You for that. I tested it and indeed it doesn’t cause the error. Installing any of other 3 non-updated plugins causes the error to appear again though, which proves my initial suspitions: error is caused by DRM detecting the non-updated X-named plugin being installed. There has to be some bug/collision between code responsible for detecting version of X-named plugins and code responsible for validating/non-validating.

The best way to get the all the latest X plugins is by installing it from X Addons > Extensions. However, before you can install it, you will need to validate X so that you can connect to out plugin server. Only validated sites can connect to our plugin sever and this is why you must validate X.

I’m aware of that fact and having some non-updated plugins while still in-development would be completely fine for me if not for this error.

You can always revoke the validation once you are done install the necessary X plugin so that you can re use X in your other site if you have to.

I didn’t know that. It still sound like a lot of hassle though, as for sake of this topic alone I reinstalled entire wordpress site on my localhost like 30 times already. I think I’d go all “Hulk Mode” if I had to validate/re-validate every time.

Final notes:
Could You please try to recreate the error using my guide from post #1361369. It really is a moment and it will prove my point that something is wrong a bit deeper here. IMPORTANT: Do not validate while recreating the error – do everything manualy.

Attachments:
Error 1: Shows Content Dock without error (the one from You Nel) and White Label with the error. Both are just installed, not activated. The other 2 that caused error (reference above in this post) are not installed.
Error 2: Shows the error after installing “Under Construction” plugin on top of what was shown in Error 1 screenshot. Note that error now covers two plugins that should be below “Under Construction” plugin – they are still installed just not visible because of the error in previous plugin on the list.

If it’s possible I’d like to continue talking with Rue Nel, or someone who is already “up-to-speed” with this topic 🙂 It’s nothing personal but it is a bit stressfull and uncomfortable to speak to a different person every post. One might develop a multi-personality disorder on top of that 😉

Thanks and good day to You all!

[Author]

Posts