philoweb

Solved !

I follow your method and I found a custom function launch by the pre_get_posts filter who launch the bug.

The function “search_posts_per_page” set a configurable number of posts per pages in search result pages.

I correct this by insert this line at the top of my function :

if ( is_admin() || ! $query->is_main_query() ) return;

And that’s all ok ! I don’t understand all the reason why, but it work !

Thank you for your responses and time passed to help !

Hello Konrad,

Thank you for your response, I haven’t been notified.

The problem is persistent, and I will soon follow the method you have mentioned to me.

The thing I do not understand is that I have no problem with sites in hosted on shared servers. This bug occurs only on a dedicated server.

And once again :

• No impact on the front
• No impact on the use of my ACF blocks in Gutenberg, nor my fields in the Options pages
• It’s just the detailed view of the groups of fields that does not work and generates this error (for example: WP -Admin/Post.php?post=158984&action=edit – Post 158984 being a ACF group of fields). The page returns all the information to the ACF group, but not the ACF fields themselves, and the mentioned error is lifted. How could the themes and my blocks impact this “admin” view ACF only on this server?
• This bug appeared after version 0.8.8.9 of ACF Extended. I am solving for the moment by staying on this version, but my site devus source turning with the latest version of ACF Extended (without problems), when I export the blocks in JSON, I have a 500 error at the time of ‘Import and this operation is not quite properly done.

The PHP version does not seem to come into play. And the system has been stable for more than two years, I have built around twenty sites with it. And the problem occurs including with almost empty sites, just one or two pages.

For info, the spect of the server

WP version: 6.1.1 – Supported
WP Multisite Activated: No
Web server info: Apache
PHP version: 8.1.14
MySQL version: 10.10.2
SQL version variable: 10.10.2-Mariadb-1: 10.10.2+Maria ~ Deb11
Local php: negative_sign:
WP memory limit: 1g
WP debugging mode: no
WP language: default
MAX MAX MAX TOWN: 50 MB
Maximum PHP sending: 100m
Maximum number of nested entries: 64
PHP execution limit: 30
PHP Max Input Vars: 1000
SUHOSIN installed: no

I would come back to you later when I would have had time to duplicate the system on this same server following your instructions. But if in the meantime you had another track …

Many thanks in advance, have a nice day

Hello Konrad,
Thank you for your feedback, I did not have time to set up your tests, having many projects in progress.
I’ll do it as soon as I have some time, I’m as curious as you to see where it could come from.

Meanwhile, another problem has occurred with the latest update of the free version of ACF extended. I was only able to get out of it by reverting to version 0.8.8.9.

1 – the bug is only on the wp-admin side, there is a fatal error triggered when I want to see the detail of a group of ACF fields. No other impact, neither front side nor Gutenberg side for example
2 – this only does it on a dedicated server running on php 8.2, no worries on my shared 8.1
3 – the error concerned the memory allocation when launching the core wp-query class. The increase in server memory, already substantial, had not solved the problem.
The logged error :
Allowed memory size of 1073741824 bytes exhausted (tried to allocate 262144 bytes) in /home/####/wp-includes/class-wp-query.php on line 3749

4 – The error occurs with large sites as well as very small sites under construction (this morning, error with a site with 6 articles and 3 pages)
5 – My groups of fields are “clean” and assigned mainly to types of blocks, or to categories of articles. The error occurs even when keeping only groups associated with blocks.

FYI, I mainly use ACFpro (up to date), ACF extended free and ACF component fields (https://acf-component-field.gummi.io/) to build my blocks. The system had been very stable for years.

In advance, thank you.

Re,
Thank you for your response !
It occur in a classic page, construct only with acfpro blocks.
Strangely, it occur in only one page. But I can’t retrieve in the stack error log the source in my files.
Regards.

Hello, no it’s not resolved. Same thing happen to another site.

When I create a custom pattern, the home of the site is broken and call this empty custom pattern in place of regular homepage. The generals setings of wp are goods.

Thanks,