setevoy

Cool, thanks, @ronaldvw – this worked.

Also, I’d discovered a new area for me – hooks in WP ?? (not a developer at all, just a common WP user with a “DevOps” on the job title)

So, I tried to use the wp_footer hook, but – it adds a text to a very bottom, while I need to put it in a specific location to add counters in the right position.

Now I guess the only solution is to keep whole files in the child theme’s directory.

And some files have strings with the theme’s version like :

> * File Last updated: Iconic One 1.7.2

It’s the content.php file in this case, and “Iconic One” is the name of the theme used (btw – really good theme, I even bought its Pro version just to support its authors, check it here).

So I’ll have info if it was changed on the last update, and if so – will have to update correspondent file in the child theme.

Although this doesn’t seems to be a really good solution ??

• This reply was modified 5 years ago by setevoy.

@arnaudbroes Great, thank you.
I just now noticed the “Description” filed length, although I’m pretty sure you already aware of this behavior (I won’t’ use the “bug” word here yet ?? ).
The screenshot is here – check the “Description” at the bottom – it also has the full text included.

@arnaudbroes Here is why I suggested that the issue is because of the Preview snippet – pay attention, that in this case, it generates a preview with the WHOLE content of the post’s text: screenshot.

@arnaudbroes Here is why I suggested that the issue is because of the Preview snippet – pay attention, that in this case, it generates a preview with the WHOLE content of the post’s text: screenshot.

Oh – wrong topic ??

Hi, @arnaudbroes

Thanks for your reply.
For me, it happens for example even with the post with 2500 words.
Please, check the screenshot below.

Freeze && 100% CPU on editing

(didn’t try to disable other plugins – just had no time yet for more deeper debugging yet, sorry)

I had php_admin_value[display_errors] = 'stderr' im my /etc/php/7.0/fpm/pool.d/rtfm.co.ua.conf.
Changed to the php_admin_value[display_errors] = off and all good now.
I thought stderr means write to the php_admin_value[error_log] ??
Anyway – the warning gone now.

> just set WP_DEBUG to false in production and that’s ok)

@chouby +1 – doesn’t work for me too (PHP 7.0.33-0+deb9u6)

@mstuyts @ini_set( 'display_errors', 0 ); – where did you added this? Tried add to the wp-content/plugins/polylang/polylang.php – no result.

Great!
The fix worked for me too, thanks a lot.

The version already installed – Version 2.4.0 | By James Bradford.
Disabled and enabled it again.
Nothing in the Dev Console – after closing the bar with “x” it’s appeared again after the “Update” post button was pressed.
Screenshot available here: https://ibb.co/hfYQbZN

• This reply was modified 6 years ago by setevoy.

Just created new Menu in the Appearance => Menus, and made it “Primary Menu”.

OK, it was the expires max; option in the nginx.conf – added it into the server {} block during “performance tuning” attempt.
Removed it, cleaned cache again – and looks like all works now.
Instead – need to set it to the images location block:

    location ~* \.(jpg|swf|jpeg|gif|png|css|js|ico)$ {
        root {{ web_data_root_prefix }}/{{ item.0.name }}/{{ item.1 }};
        expires 24h;
    }

(this is part of my Ansible template)

• This reply was modified 6 years, 7 months ago by setevoy.
• This reply was modified 6 years, 7 months ago by setevoy.
• This reply was modified 6 years, 7 months ago by setevoy.
• This reply was modified 6 years, 7 months ago by setevoy.

Well, I’m still interested in the root cause… Did it happen because of changing NGINX’s settings? Or just a “bug” in browsers?
Looks like it was something in NGINX as it affected two different browsers – Chromium and Opera (on Linux).

But anyway – will mark this topic as Resolved.
Thank you for confirming my guess about cache ??

Yeah, that looks like caching issue, @emmtoor.
Found this after opened WP in another browser: after adding a new post from it, let’s say “test3” – I saw previously added “test2” + “test3”. After adding “test4” – I saw “test2” and “test4”.
And yes – after cleaning browser’s cache – it works now.
I’m trying to find why that happens… I did some changes with NGINX’s configuration and trying to roll-back them one by one to find where the root cause was.
Although – after cleaning browser’s cache looks like it works anyway.

P.S. Even more: after I cleaned cache in my _first_ browser – I got all my test posts added before ??

• This reply was modified 6 years, 7 months ago by setevoy.

Proxy came here just now, after migration, so previously – it was something about IIS/Azure directly.

Hi, @tott.

Suddenly – we got update with that ??

So – customer went away from Azure to own server, with some Linux and Apache 2.4. And – faced with the same issue – “HTTP error”.

We also got another one issue with 413 error on this new host – “Entity body too large“. As traffic goes via our NGINX as Proxy to their host with Apache – I updated our NGINX and added:

client_max_body_size 64M;

And – that fixed not only 413 – but the “HTTP error” as well.

Thanks for your assist ??