Wordpress Some WordPress issues

To clarify it worked then I updated PHP then it immediately didn't work, I didn't wait any number of hours . Now recreatable on 2 servers. I will remove all plugins but I seriously doubt that's it.

---

 

Hi @eva2000 - I'm having the same problem now. I did run an option 13 yesterday to install Redis. Anyone else reporting this issue?

@Nik did you ever resolve this?

 

Nope I did not. I live with it now.

Are you running XF btw?

 

Yes

 

Nope I did not. I live with it now.

Are you running XF btw?

It was definitely triggered by

Are you running TH XPress?

 

Are you running TH XPress?

@eva2000

There's something super wrong with XF on your site right now. It's caching responses and frequently clocking when hitting Post Reply. Thought I'd mention it.

 

No issues for Wordpress and Invision forum using the latest Redis...

It may help to post all your plugins that you are using...

 

I don't think the other report confirms use of the bridge addon, waiting to hear back.


So I can successfully get rid of this error by disabling the TH bridge addon. I don't know if the other reports are using it or not. Nothing else in my config has actively changes beyond updates to centmin and various recompiles. What I can confirm back when the post was created was that one of those recompiles resulted in these errors going forward. It's php version agnostic as I've proven personally. Unfortunately I cannot live without XPress and albeit issue was reported to TH a while back they are a shell of their former selves so fully expect that this will never get resolved unless many others report it.


Interested to see if anyone else is running the bridge addon.

I'm not running any caching on the WP side of the integration.

 

I am also using TH Xpress. Here is the error:

Code:

[21:51][root@xf.domain.com centminmod]# cd /home/nginx/domains/domain.com/public/
[21:51][root@xf.domain.com public]# wp plugin update --all
Fatal error: Uncaught ErrorException: file_exists(): Unable to find the wrapper "phar" - did you forget to enable it when you configured PHP? in /root/.wp-cli/packages/vendor/composer/ClassLoader.php:394
Stack trace:
#0 [internal function]: XenForo_Application::handlePhpError(2, 'file_exists(): ...', '/root/.wp-cli/p...', 394, Array)
#1 /root/.wp-cli/packages/vendor/composer/ClassLoader.php(394): file_exists('phar:///usr/bin...')
#2 /root/.wp-cli/packages/vendor/composer/ClassLoader.php(351): Composer\Autoload\ClassLoader->findFileWithExtension('XenForo_Error', '.php')
#3 /root/.wp-cli/packages/vendor/composer/ClassLoader.php(321): Composer\Autoload\ClassLoader->findFile('XenForo_Error')
#4 [internal function]: Composer\Autoload\ClassLoader->loadClass('XenForo_Error')
#5 /home/nginx/domains/domain.com/public/community/library/XenForo/Application.php(380): spl_autoload_call('XenForo_Error')
#6 [internal function]: XenForo_Application::handleException(Object(ErrorException))
#7 {main}
  thrown in /root/.wp-cli/packages/vendor/composer/ClassLoader.php on line 394
[21:51][root@xf.domain.com public]# 

 

Interesting. So it is xpress related but why it started breaking after a CM update I do not know.

I logged it already here, you may want to add to it as TH of course incorrectly closed it already so it's taken an effort to relog issues.

WP CLI is Broken by XPress · Issue #597 · Audentio/xlink-issues

 

@Nik Audentio and I have chatted about this. They are confident it's not their code, but a conflict with another item, but they do have a workaround:

It is possible to manually patch the issue by inserting the following line at the start of <wp_root>/wp-content/plugins/wp-xpress-plugins/thxpress.php, but the patch needs to be performed each time the file is updated:

stream_wrapper_restore('phar');​

 

That's great. Yes I'm confident it's not their issue even though disabling every plugin except for theirs still produces the issue but you know what do I know...

Thank you for coming back with a fix.

 

Some time in the recent past, Audentio's fix stopped working. I stumbled across a thread on the XF forums that they're disabling phar in XF now to solve security issues. XF is loaded at all times with XPress, which made me think maybe the problem was in XF and not WP.

I was able to restore phar functionality on my server and WP CLI in kind by adding the below to the xenforo /src/config.php file at the top:

Code:

stream_wrapper_restore('phar');