Jose Mortellaro

You’re welcome, Adrian!

If the rewrite rules are flushed only when you edit a map, that’s totally fine. In this case, it was a false alarm.
I’ll try to improve this check to avoid this kind of false alarm in the future.

Thank you again for reporting this issue.

I would not ask them to reduce the requirement to flush the rewrite rules if you confirm that they flush it only when you edit the map.

Best regards

Jose

@binarywc Lies are born when the truth is difficult and we are not strong enough. With this, I will close the discussion. I suggest you be more honest in your life. Good luck.

For those reading this review, the user is referring to this thread:
https://ww.wp.xz.cn/support/topic/hosting-provider-claims-freesoul-plugin-is-causing-502-503-errors/

I suggest reading the thread and forming your own opinion about our support.

We didn’t received any other support requests from them.

Please, read also the support requests from other users if you want to have an idea about the support.

Of course, we are not perfect, like all humans, but when someone is not polite, I cannot pretend otherwise. I am always honest. Reading between the lines, it was clear that this user was rude and not willing to listen.

He requested a MySQL command line. I did not provide it because I did not have time to prepare a safe version. I will add the MySQL command line to the documentation for others who may need it.

I responded to him after 10 hours, on a holiday, for a free plugin. And this is the “bad support” he complains about.

• This reply was modified 5 months ago by Jose Mortellaro.

You say it’s not the first time you had a bad support. I don’t see any other support requests from you on this forum https://ww.wp.xz.cn/support/users/binarywc/topics/

Anyway, if you were a real developer, you would have appreciated my support.

This is a free plugin. I”ve answered after around 10 hours and it’s holiday here in Spain.
I’ve tried to understand your issue. I believe I’ve understood your issue, and suggested what to do, but you don’t hear.
Have you enabled the debug in wp-config.php?

In any case, I have nothing more to say. I will not give you the MySQL command. This would be very dangerous because you are not a developer, sorry. You think you are, but you would not ask this kind of questions if you were a real developer.

If you are developer, the first thing you do is open the file uninstall.php and check what you need to remove.

Sorry, but this forum isn’t for this kind of help. We are not here to give you a MySQL command line.

For doing that, go to ChatGPT and paste the uninstall.php content.

If it doesn’t help, install another plugin.

I will close this thread.

Best regards

Jose

Hi Davood,

you deactivated Freesoul Deactivate Plugins (FDP) using FTP, right?

If you want to clean the settings of FDP, you can simply deactivate it from the plugins page, and delete it from the plugins page. It will automatically clean up the database.

Another way is resetting the FDP settings from FDP main navigation => Tools icon => Reset FDP Settings.

However, I suggest you don’t do that. If the errors are caused by FDP, the cause it’s more likely the presence of the mu-plugin wp-content/mu-plugins/eos-deactivate-plugins.php.

That file wasn’t deleted if you deactivated FDP via FTP. That file is deleted only if you deactivate FDP in a standard way from the plugins page.

Instead of cleaning the database and lose all the FDP settings, I suggest you delete that file.

Even better, before deleting anything, enable the debug in wp-config.php and check the file wp-content/debug.log. It will give you information needed to understand what is going on.

Probably, you have disabled a plugin with FDP that is needed for a third plugin.

A fatal error typically occurs when an active plugin attempts to call a function defined in another plugin that you have disabled. If the active plugin does not first verify that the function exists, the site will crash.

I hope it helps.

Best regards

Jose

Hi @joebarrettaccess

Nothing in the PlugVersions code can cause this kind of issue.
The list of active plugins is based on the WordPress core option active_plugins. PlugVersions never updates this option and never filters it.

Switching between plugin versions is done by renaming the plugin folders, without touching the database.

When you roll back to a previous version, it’s not possible for other plugins to be affected. If you experience an issue with the plugin you are rolling back, it could be a bug in PlugVersions. However, if the issue affects other plugins, then the cause must be something else.

You likely have a plugin that filters the active_plugins option. Do you have any plugin manager installed, such as Freesoul Deactivate Plugins, Plugin Organizer, or Plugin Load Filter? If so, I suggest checking whether there is a conflict with your plugin manager.

I will review the PlugVersions code again to make sure I’m not missing anything, but at this point I don’t see anything that could even trigger this kind of issue in PlugVersions.

Best regards

Jose

Hi @jerichomontes

Thank you for your kind words.

I suggest updating the plugin to version 1.0.2, where the misspelling has been fixed.

After updating, you can remove the line you mentioned by adding the following code to your child theme’s functions.php file or to a custom functionality plugin:

add_filter( 'essential_form_include_source_in_email', '__return_false' );

You probably won’t need it, but you can now even customize the text before the message using the filter hook essential_form_before_message.
Here’s an example:

add_filter( 'essential_form_before_message', 'my_custom_before_message', 10, 4 );

function my_custom_before_message( $before_message, $name, $email, $post_id ) {
    $before_message = "Sender: " . esc_html( $name ) . "\n\n";
    if ( $post_id ) {
        $post_title = get_the_title( $post_id );
        $before_message .= "Message submitted from the page: " . esc_html( $post_title ) . "\n\n";
    }
    return $before_message;
}

I hope it helps

Have a great day!
Jose