Jose

Отлично, спасибо за подтверждение.

Hi @po64

thank you for reporting this issue. Please, update to v. 0.0.4, it fixes the issue

Have a great day!

Jose

привет @po64

спасибо, что сообщили об этой проблеме. Пожалуйста, обновитесь до версии 0.0.4, это решит проблему.

Хорошего дня!

Thank you very much Klodi.

Unfortunately, renaming the wp-content is not possible with this plugin. At least not at the moment.
Maybe this feature will be added in a future version, but I can’t say now when.

Have a great day!
Jose

Hi @cutu234

thank you very much for sharing your experience. I’m happy that the anti-spam system works well.

Have a great day!

Jose

Perfect. You are welcome Dave!

Have a great day!

Jose

Hi Osaopaulo,

you can remove it with this PHP code:

add_action( 'plugins_loaded', function() {
    remove_action( 'add_meta_boxes', 'eos_scfm_add_meta_box' );
} );

Have a great day!

Jose

Hi Dave,

thank you very much for asking your question. Honestly, I realise only after your question that this was really not clear ??
In the next version the example in the backend will be clearer.

Anyway, the right syntax is:

asset-url media=”(min-width: 601px)”

for example:

https://yoursite.com/wp-content/uploads/2024/04/your-image.jpg media=”(min-width: 601px)”

Have a great day!

Jose

@agencewebmeyer

Hi Stephen,

thank you so much for your feedback! I really appreciate it.

Have a great day!
Jose

Hi @pixelmm,

Thank you for reporting this issue.

v. 2.2.2 was still not public but was already on the repository. Before publication, we changed something in the code. All those differences reported by WordFence are related to the changes done before the publication.

Probably, WordFence doesn’t read the most updated files, but the old files of v. 2.2.2.

In any case, there is no reasons to worry about those warnings. I don’t see anything strange in the code.

I hope it helps.

Have a great day!
Jose

You are welcome @khobs!
Many thanks to you! Your thread was a big help for improving the plugin.

Hi @khobs,

thank you for reporting this issue.

Please, update the plugin to v. 2.2.2 and let me know if it works also for you.
I was able to reproduce the same issue with v. 2.2.1, and v. 2.2.2 fixed it.

Have a great day!

Jose

Hi @leroy-b,

as answered to your email, you have the settings in Specific Content For Mobile => Tablets.
If you don’t see that settings page or still have any issues with the PRO version, please, let’s continue via email. The rules of this forum don’t allow us to help with the PRO features.

Have a great day!
Jose

Hi @harryfear,

when the file wp-content/mu-plugins/eos-deactivate-plugins.php doesn’t exist and you have Freesoul Deactivate Plugins active, you should see an error in the FDP backend pages that is very visible, with big fonts.
Maybe you have some CSS in the backend that hides that error.

However, without that file, FDP can’t disable any plugin. Hadn’t you noticed FDP was not working? All the plugins should be always and everywhere active without that file. This is why I suspected your mu-plugins folder is elsewhere.
What do you see if you go to Plugins => Installed Plugins?
Can you see the link “Must-Use”?
If you see it and click on that link, can you see freesoul deactivate plugins [fdp]?

When you activate or update Freesoul Deactivate Plugins, it writes the file eos-deactivate-plugins.php into the folder wp-content/mu-plugins.
So, if you confirm that the mu-plugin doesn’t exist, try to deactivate, and then activate again Fresoul Deactivate Plugins.
Be careful, you have only to deactivate it, not delete it. If you delete it you will lose all the settings.

After doing so, can you see the file wp-content/mu-plugins/eos-deactivate-plugins.php? Or in Plugins => Installed Plugins => Must-Use, can you see freesoul deactivate plugins [fdp]?

If you still don’t see it, via FTP, create the folder wp-content/mu-plugins, and manually copy that file from wp-content/plugins/freesoul-deactivate-plugins/mu-plugins/eos-deactivate-plugins.php to wp-content/mu-plugins/eos-deactivate-plugins.php.

Have a great day!
Jose

Thank you @harryfear.

That function fires only after a plugin is activated or updated.
Probably when you invoke the WP CRON one or more plugins are updated.
In any case, the function eos_dp_get_option() is defined in the file wp-content/mu-plugins/eos-deactivate-plugins.php which is called by WordPress before the file /wp-content/plugins/freesoul-deactivate-plugins/fdp-load.php where the error was triggered.
This means the file eos-deactivate-plugins.php is not called when you invoke the WP CRON which is very strange.

Can you please check the file wp-content/mu-plugins/eos-deactivate-plugins.php exists?

I suppose it exists, in another case, FDP would not be able to disable any plugin. So I suspect the files in wp-content/mu-plugins are not called during the WP CRON in your case. If confirmed, this would not be a normal behavior.
Do you have any code that defines a different path for WPMU_PLUGIN_DIR during the WP CRON?
How do you invoke the WP CRON? Using WP CLI?

For me, it would be easy to modify the code in fdp-load.php to avoid the error about the undefined function, but it would be better if we first understood what is going on, in another case, you could have other issues.

Have a great day!
Jose

Hi @agod,

When you add or remove something to/from the cart, WooCommerce calls via Ajax a URL that looks like https:///yoursite.com/wp-admin/admin-ajax.php?action=add_to_cart&……..

You can’t manage Ajax actions with Custom URLs…
In your case, you can use the settings Actions => WooCommerce => add to cart. I suggest you have a look here: https://freesoul-deactivate-plugins.com/how-deactivate-plugiins-on-specific-pages/actions/

I hope it helps.

Have a great day!
Jose