- This topic has 15 replies, 4 voices, and was last updated 1 month, 1 week ago by
.
-
Posts
-
My ISP has obsoleted all versions of PHP7 and is recommending PHP8.1.
Wordpress forum indocates this is a theme error.
[22-Aug-2023 23:06:50 UTC] PHP Fatal error: Uncaught TypeError: preg_split(): Argument #3 ($limit) must be of type int, float given in /homepages/htdocs/wordpress/wp-includes/formatting.php:4056
Stack trace:
#0 /homepages/htdocs/wordpress/wp-includes/formatting.php(4056): preg_split()
#1 /homepages/htdocs/wordpress/wp-includes/formatting.php(4012): wp_trim_words()
#2 /homepages/htdocs/wordpress/wp-includes/class-wp-hook.php(310): wp_trim_excerpt()
#3 /homepages/htdocs/wordpress/wp-includes/plugin.php(205): WP_Hook->apply_filters()
#4 /homepages/htdocs/wordpress/wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php(1875): apply_filters()
#5 /homepages/htdocs/wordpress/wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php(952): WP_REST_Posts_Controller->prepare_item_for_response()
#6 /homepages/htdocs/wordpress/wp-includes/rest-api/class-wp-rest-server.php(1188): WP_REST_Posts_Controller->update_item()
#7 /homepages/htdocs/wordpress/wp-includes/rest-api/class-wp-rest-server.php(1035): WP_REST_Server->respond_to_request()
#8 /homepages/htdocs/wordpress/wp-includes/rest-api/class-wp-rest-server.php(447): WP_REST_Server->dispatch()
#9 /homepages/htdocs/wordpress/wp-includes/rest-api.php(418): WP_REST_Server->serve_request()
#10 /homepages/htdocs/wordpress/wp-includes/class-wp-hook.php(310): rest_api_loaded()
#11 /homepages/htdocs/wordpress/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters()
#12 /homepages/htdocs/wordpress/wp-includes/plugin.php(565): WP_Hook->do_action()
#13 /homepages/htdocs/wordpress/wp-includes/class-wp.php(398): do_action_ref_array()
#14 /homepages/htdocs/wordpress/wp-includes/class-wp.php(779): WP->parse_request()
#15 /homepages/htdocs/wordpress/wp-includes/functions.php(1335): WP->main()
#16 /homepages/htdocs/wordpress/wp-blog-header.php(16): wp()
#17 /homepages/htdocs/wordpress/index.php(17): require(‘/homepages/39/d…’)
#18 {main}
thrown in /homepages/htdocs/wordpress/wp-includes/formatting.php on line 4056I am using Weaver Xtreme and theme support plugin 6.3. While I am relatively new to your theme so far I like it. When I disable Weaver Xtreme and plugin in favor of a WordPress native site builder theme the errors go away.
Post not saving can’t be the norm.
@weaver will have to comment
Two weeks ago I updated my Xtreme site from PHP 7.4 to 8.2.8 and all worked 100%.
However, I had previously tested all my plugins, and had found that one of them worked – but gave lots of error messages on PHP 8.0.x.
I then found a substitute for that plugin and went ahead with the upgrade.
FYI, for my live site testing I used two methods, #1 was the WP Health Check & Troubleshooting plugin, which allowed me to quickly test Xtreme with all the plugins, one by one, and #2, installing XAMPP on my pc and copying the live site setup onto it.
My outdated plugin worked, while still giving unrelated error messages galore! Please do check that you don’t have that same issue. 🙂
Regards and thanks!
The error message you provided does not indicate the error originated with the Weaver Xtreme. There have been no other reports of PHP 8.1 error messages.
It is more likely coming from a plugin. I would suggest testing your site with Weaver Xtreme as your theme, and then disable all plugins, one by one, to see when the error message stops.
I have disabled all plugins even the xtreme support plugin and I still get the error. I change to the WordPress default 2023 theme no error. THe footer only contains the copyright.
When posting credential, always set the post as private so only moderators can see it
I did it for you
So I’m a bit confused.
You sent credentials for https://carterrailroadmuseum.org which seems to be a WP Multisite.
The site you provide above is https://memrr.org
Weaver is not set as Super Admin, so I can’t upload some testing stuff.
If you could download and install the Weaver Xtreme 5 special version, it would allow us to test if the old Weaver 5 works. It should be PHP 8 comptatible,
The download zip is here: https://weavertheme.com/download/9215/?tmstv=1692922224
@whhealy – your question: By the way where is Weaver Xtreme at being block friendly?
Weaver Xtreme supports WP Blocks. However, it will never become what is called a Block Theme. The options organization for traditional themes vs. Block Themes is completely incompatible. Block Themes essentially do not support traditional CSS, and they do not even allow any custom CSS. Really a bizarre design decision as it precludes all the years of effort millions of people have put into learning and understanding CSS.
In spite of WP’s move to “Block Themes”, there are just way too many existing WP sites using classic customizer based themes for WP to drop support for them, at least for many years to come.
But Weaver Xtreme includes a lot of specific CSS rules specific to standard WP Blocks. And there are very few other classic themes the support proper styling in the Block Editor. Almost all of the styling options you specify using Weaver Xtreme Customizer options are applied to the Block Editor display – colors, fonts, etc. Actually, I have not found another classic theme that will apply options to the Block Editor. There must be some, but I have yet to find one.
So, to summarize the answer: Weaver Xtreme has some of the best support for standard WP blocks and the block editor.
@wshealy –
I am not seeing the error message, but when I use your .wxb file, saving a new page fails. So there IS something the the .wxb file. At least there’s a place to start now.
And just to double check on your sites, you could try to test by using one of the built-in Weaver sub-themes.
@wshealy –
I found that problem was in a Weaver Xtreme option for setting post excerpt lengths. The settings you provided had the excerpt length set to over 9000.
It really is a WordPress bug, which I will report. I could fix it in the theme, but I’m not going to since it is an underlying WP issue.
And that error message was coming from the WP internal code that handle excerpt length. So apparently the WP code does not have a check that the excerpt length is a sane value. (The option is in the Customizer Where : Post Specifics : Excerpts / Full Posts : Excerpt Length.)
The theme could double check that, but it really is a WP problem.
But should get you back on track now. I only discovered it by examining every option you’d sent. I’m sure there are plenty of themes that adjust the default excerpt length, but I’d guess it is possible that no one has ever tried to set the excerpt length to over 9000 before.
This is the third or fourth WP bug I’ve uncovered over the years, and they generally are a pain to track down.
- You must be logged in to reply to this topic.