ram108

@pattihis Thank you very much for fast response. There is no error now.

I have the same issue on my site with absent images on product categories.

This violates the WordPress plugin guidelines, paragraph 11: Plugins should not hijack the admin dashboard.

Source: https://developer.www.ads-software.com/plugins/wordpress-org/detailed-plugin-guidelines/.

Here is the example:

• This reply was modified 2 years, 9 months ago by ram108.
• This reply was modified 2 years, 9 months ago by ram108.

@sterndata Please see here: https://www.ads-software.com/plugins/ram108-typo/ My name is in authors list.

@krasnostas post an issue in wrong forum, but for the plugin, that I am the author.

@sterndata I’m the plugin author. If there is an issue I try to fix it. How can I contact to the issue starter?

The error above is related to another plugin – Web Typography Standards: https://www.ads-software.com/plugins/ram108-typo/

I wrote to the Typograph developer to update his code. Waiting for an answer.

@coreyk

Another interesting graph that shows how important it is to use nginx or apache to directly serve cache files, not a php interpreter.

See graph: https://ibb.co/YDC9F0f

Until August 18th, we have been using Cache Enabler for a very long time. You can see CPU load on the graph.

On August 18, a new version of Cache Enabler 1.4 was released, which changed the names of cache files, as a result, nginx stopped serving files directly and began to use the php interpreter.

The graph shows how the processor load has increased in several times. The load was noticed and analyzed.

Nginx settings have been updated to directly handle cache files with new names. As a result, the server load returned to its previous, almost zero values.

@coreyk @mobiflip

https-index.html.gz

This entry cannot be used, it will cause an error. The server will pick up the compressed files by itself if found.

Correct: https-index.html

@coreyk

was that comparing the difference between

Now I can’t say exactly what the handler was. But I noticed an unusually high load on the server, looked at the process list and found a lot of php-fpm processes creating the CPU load. After examining the problem, I saw that nginx does not serve files directly and uses the php interpreter instead.

Thus, it was found that the names of the cache files have changed.

@mobiflip yes, due to plugin cache filenames change, default apache and nginx snippets doesn’t work anymore.

@keycdn
Correct link is: https://translate.www.ads-software.com/locale/ru/default/wp-plugins/cache-enabler/

But I don’t see any strings here that need to be translated.

I tried uploading my .po translation file, but got the answer: No translations were found!

I did the translation and I have .mo and .po files.
Screenshot: https://ibb.co/DDWnHhx

https://translate.www.ads-software.com/locale/ru/default/wp-plugins/cdn-enabler/

Is it for Cache Enabler?

@coreyk

See this graph: https://ibb.co/swFrcRS

On the left side is the CPU load when nginx stopped processing requests as a result of changing the names of the cache files.

On the right is when I re-enabled nginx processing.

Therefore, using direct file serving with nginx or apache is very important for performance.

• This reply was modified 4 years, 3 months ago by ram108.

The advanced configuration snippet is not required and in many cases not used.

It is used and required, belive me.

With nginx serving pages, I have zero CPU load. But with the return through php (wordpress), the load increases to 30-50%.