AMIB

They have checked the existence of function “file_get_html” but FVM does NOT check anything and has renamed functions but NOT main class

The previous version was working properly and there was no write permissions related problem.

Today I did open more than 30 sites to disable Merge functionality

Choose a better filename like: managewp-cloner.php.
There was requests to this file in the server log

I taught my site is hacked and was trying to find the problem >:

Thanks, It is OK now.

The plugin has not built-in support for RTL stylesheets
You can find the code to solve the problem here:

https://rokaweb.ir/fvm-rtl/

There is no better way for date localization plugins to do the job they are doing. And also there is no straightforward method for those plugins to check for real usage of function return value.

So I think the only solution for this conflict is not to use wp_date as there is no localization or manipulation necessary.

• This reply was modified 4 years, 2 months ago by AMIB.

Modification of date as local date system is not incorrect. Many many sites are using this method just to display dates, not to insert into MySQL with certain format.

There are some correct usages of the wp_date function in the flamingo. but these two locations are incorrect.

Here is the link

The better question would be:
Why should the plugin use the filtered wp_date function to generate a parameter that supports just ONE format and value?

wp_date() outputs a Gregorian calendar date string in the specified format

This is not true as there are some plugins that change the date system like: parsidate and some other ones…

Setting the menu name with English characters and no spaces solved the problem for me. It was a Unicode name contaiing spaces.

Setting the menu name with English characters and no spaces solved the problem for me. It was a Unicode name contaiing spaces.

Setting the menu name with English characters and no spaces solved the problem for me. It was a Unicode name contaiing spaces.

Setting the menu name with English characters and no spaces solved the problem for me. It was a Unicode name contaiing spaces.

It seems that there is also a new option to force rewrite in permissions( by using buffers ), this was also auto activated and it took me some time to find out what is happening to site title.

This option is also a problem itself. What performance and memory issues happen if every plugin decides to buffer whole the page to “forcibly” modify the html intentionally generated by theme ?

These two main modifications and other changes related to them kept me awake by now( 6:30 AM ) fixing the title of some sites to prevent SEO problems.

Anyway the problem is solved now. but I hope future modifications do not break the compatibility as there are thousands of sites using it.

These type of actions may have no effect on many sites. but some handcrafted sites will face issues

I was facing the same issue in the site title( two titles after each other ) and some other incompatibilities.
The whole title system of new version is breaking compatibility with some themes.

The old and the new title system do not fulfill every SEO requirement for expert users and removing options to bypass this option is not a good decision.