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 6 years, 2 months ago by setevoy.

@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.

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)

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 7 years, 2 months ago by setevoy.

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 7 years, 8 months ago by setevoy.
• This reply was modified 7 years, 8 months ago by setevoy.
• This reply was modified 7 years, 8 months ago by setevoy.
• This reply was modified 7 years, 8 months ago by setevoy.

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 7 years, 8 months ago by setevoy.

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 🙂