PHP 8.4

[User]

@Weaver @Roadside

Before entering into all that work for you both, may I humbly suggest a further check for WP plugin conflicts?

@Roadside, if you are willing, may I suggest you install and activate the WP “Select Health Check & Troubleshooting Health Check & Troubleshooting” plugin and initialize the “Troubleshooting” mode?

That will allow you to have a test sandbox with only Weaver Xtreme and Jetpack running.  In PHP 7.4 all ought to display and work correctly.

If you were then to reset to PHP 8.4, you will be able to confirm instantly that this is a “Weaver Xtreme and Jetpack” only issue, or if one of the other plugins is causing (or contributing to) the issue.

Assuming this test is okay, a conflicting plugin may be confirmed activating plugins in the Troubleshooting mode, one by one.

Just a thought to perhaps rule out all other plugins as contributing factors and should not take long to do.

Regards.

[roadside]

@weaver I couldn’t see your last response.  Marked private.  (Maybe because I wasn’t the originator of the thread?)

@user Thanks for that.  I didn’t know about that plugin.  Tried it out and ran the site at 8.4 with only Weaver and JetPack running and did get the same error result.  Just the header image and nothing else.

 

[Weaver]

@roadside – I took off the private setting. I had thought you were the originator of this thread…

 

[roadside]

Got it, thanks.  There is a way to set different versions for different sites, but I’ll have to figure out how to use it.  My host is pretty helpful with that stuff.

 

Might take me a few days to get it, but I’ll get it happening.

[User]

@Roadside

FYI, I currently use 8.3.25 and that is a huge improvement over 7.4 in every way.

8.3 also seems to have no known compatibility issues with the latest WP core, Xtreme or plugins.

Given Weaver’s previous comments, it may take a while to resolve what’s going on with Jetpack & Extreme…. so in the meantime, I think 8.3 will get you where you want to be.

Regards!

[roadside]

Thanks, but I’m running into that on 8.3 as well.  It’s weird.  I’m trying to find the time to clone the site for playing around.

[User]

Very odd.

Have you confirmed that it the Jetpack plugin which is causing the issue with 8.3 too?

 

[TheSpiralMom]

This reply has been marked as private.

[vladgavr]

Dear all, I would like to report a bug with accessing the WordPress admin pages that happened since I updated to PHP to 8.4 from 7.4 and concurrently upgraded weaver-extreme to version 6.7 from 6.4.1 . I am running two websites on x10hosting on their free hosting offer (https://x10hosting.com/) with domains https://vladimirgavryusev.ru/ and https://italiagidflorenzia.ru/

On both websites I’m getting this error when I try to login in the admin backend:
“Parse error: Unmatched ‘}’ in /home/public_html/wp-content/themes/weaver-xtreme/admin/admin-core/admin-page-posts-meta-boxes.php on line 1”

If I use another theme or change the theme name to anything else, I get to access the admin panel.

The current server config is
Wordpress 6.8.3 with PHP 8.4 with these libraries (https://ibb.co/WWLmvNjT) and options (https://ibb.co/zHXQSxRn)

Fearing a cache issue, I replaced W3 Total Cache with WP Super Cache, but it made no difference.

Before upgrading the PHP version and the Theme weaver-extreme to version 6.7 from 6.4.1 , these were the plugins that I had installed on both sites (the updated versions run fine):

————————————————————
Blog vladimirgavryusev Activated plugins:
Akismet Anti-spam: Spam Protection v.5.5
BackWPup v.4.1.7
Broken Link Checker v.2.4.2
Simple Google reCAPTCHA v.4.0
Transposh Translation Filter v.1.0.9.3
TablePress v.3.1.3
WP Super Cache v3.0.2
Weaver Xtreme Theme Support v.6.5.1
Yoast SEO v.25.5

————————————————————
Blog italiagidflorenzia Activated plugins:

AddToAny Share Buttons v.1.8.13
Akismet Anti-spam: Spam Protection v.5.5
BackWPup v.4.1.7
Broken Link Checker v.2.4.2
Contact Form 7 v.6.0.3
Honeypot for Contact Form 7 v.2.1.7
Simple Google reCAPTCHA v.4.0
Transposh Translation Filter v.1.0.9.3
WP Super Cache v3.0.2
Weaver Xtreme Theme Support v.6.5.1
Yoast SEO v.25.5

 

Can you kindly help?

[User]

@Weaver will meed to comment.

[Weaver]

Having the error output message is helpful.

This is a somewhat difficult thing to figure out since you are unable to admin those sites to fiddle with things.

Note, the error message. It is quite revealing in some ways.

“Parse error: Unmatched ‘}’ in /home/public_html/wp-content/themes/weaver-xtreme/admin/admin-core/admin-page-posts-meta-boxes.php on line 1”

What that says is that there is a } on the first line of the listed file. That clearly is NOT the case with the original source file. So either that php file that is part of the installed weaver theme has been corrupted, or there is some malware injection going on. But if you have an opening } in a php file, it will throw the error message you got.

So, using your hosting site’s admin account, you need to try deleting the weaver-theme directory. That should then let you access your WP admin account. Try adding a different theme – just to see if that works. Then try to reinstall Weaver Xtreme if another theme works. If Weaver Xtreme then works, it means the version you installed before was somehow corrupted. If not, then I’m not sure what could be going on.

ChatGPT suggests:

Weaver Xtreme’s clean source is almost certainly fine; the copy on the server is likely:

• Corrupted / partially uploaded during the theme update, or

• Injected (malware edits often stick a stray } plus obfuscated code at the top), or

• Stale OPcache serving a corrupted compiled file (less common, but it happens).

Because the user updated both PHP and your theme at the same time, a bad upload + OPcache is a very plausible combo.

—

I’m not sure what OPcache is, or how to reset it.

The AI suggests using cPanel or whatever tool your site host provides to replace the theme. If there’s another theme loaded, then you can simply delete the WeaverXtreme directory, but it might be interesting to create a zip file of the corrupted directory first for possible analysis of a hack.

Another general hint when upgrading things: Upgrade only one thing at a time! It is most likely a corrupted version of the theme and not PHP 8.

Good luck, and let us know if that fixes things.

[vladgavr]

I’ve found out the solution, with the help of Gemini. I’ve reuploaded a fresh copy of the theme in version 6.7 and changed in the file “admin/admin-core/admin-page-posts-meta-boxes.php” the line endings from MAC (CR) to Unix (LF), according to this guidance:

The “Single Line” Delusion (Line Ending Mismatch)
If the file was saved or extracted on x10hosting using non-standard line breaks (like legacy Mac \r instead of standard Unix \n), the PHP parser on your server won’t recognize where lines end.

To PHP, the entire file exists on Line 1. So when PHP encounters a syntax error anywhere deeper in the file, it gets blamed on line. If you are using an editor like Notepad++ or VS Code, open admin-page-posts-meta-boxes.php, set the line endings format to Unix (LF), and save. When you upload it back, PHP will give you the exact line number where the issue lives.

[Weaver]

All Weaver themes and plugins have been edited with an editor that has \n end of lines. I don’t think they ever were in \r format.

But that is an interesting and obscure issue. I’ve never heard of any \r vs \n issues before. Thanks for the report.

 

[vladgavr]

You are welcome. It appears that admin-page-posts-meta-boxes.php was the only file with this encoding issue, at least on my computer. Thanks for the support.

[Author]

Posts