[RadModerator]

Hi there,

Hmm, I can see that by checking the code. Though I’m not getting the same issue, we have same Xampp setup.

I’ll forward this for further checking. Please stay tuned.

Thanks!

[necxelosParticipant]

Any news? It’s already been a week of me “staying tuned” and nothing appeared here 🙂

[RahulModerator]

We’re still working on it.

You’ll be updated with a solution soon.

Thanks!

[necxelosParticipant]

I don’t want to be a pain in someplace dark but…

What exactly is Your definition of soon? It’s been over a month now…

[Rue NelModerator]

Hello There,

Thanks for updating in! Sorry for the inconvenience. We are still busy for the beta testing. X updates and other plugin updates will be release anytime soon.We are just making sure that the update release will go smoothly with PHP 7.

By the way, is the error goes away if you turn of the debug mode in your config file? Sorry I could not test this on my local testing server because I am on a Mac and I do not have XAMPP installed.

Please bear with us. Thank you for your understanding.

[necxelosParticipant]

– Debug Mode is already set to Off.

– Do You plan to fix the cause of the issue or just release updated plugins alongside new X Theme version (which will be only a band-aid and the bug will come back after next plugin update)? Sorry if I didn’t understand You correctly, but that’s the impression I got from Your post.

[DarshanaModerator]

Hi there,

Please locate the following line in your wp-config.php file in the root of your WordPress installation.

define( 'WP_DEBUG', true );

Then add the following lines below.

define( 'WP_DEBUG_DISPLAY', false );
define( 'WP_DEBUG_LOG', true );

Hope that helps.

[necxelosParticipant]

I had:
define( 'WP_DEBUG', false );
…so I changed it to true and added Your code:

define( 'WP_DEBUG_DISPLAY', false );
define( 'WP_DEBUG_LOG', true );

What happened is error message disappeared.
Sadly, ONLY the message disappeared. Error is still there, just not with visible text. Plugins below the one that generates error are still inaccessible as long as one of those plugins is installed. So basically nothing changed.

[RadModerator]

Hi there,

That will redirect the error to log file, it will not fix the error. And I can’t replicate this issue on my own local installation the same with your setup. Since it’s on your local, there is no way I could check it to verify and investigate. Hence, we’ll need to find a way to reproduce this issue. If this issue is due to failed installation by XAMPP system, then it will be harder to implement because that means we’ll have to investigate XAMPP too, which we can’t since it’s not our product. Our test is based on trial and error until we find the similar issue.

If the issue is due to XAMPP itself and isolated to your installation/system, then upcoming new X versions will probably be going to fail too. We’ll keep on checking then we’ll test the new version, and you may test it as well once it’s released.

And validation is not a requirement, you can always update it manually. The error is not about forcing you to validate it. It’s just normal that validation system is loaded since it’s part of the theme, it’s loaded so whenever the user wishes to validate it then it just needs to run. And it happens to be missing, and loading a missing library will trigger an error.

Thanks and stay tuned.

[Author]

Posts