• Resolved misstomboy

    (@misstomboy)


    After the update this plugin now makes Elementor another plugin not work no more.
    I know it is this plugin causing the problem because when I deactivate it Elementor works fine. This just happen after I updated.

Viewing 15 replies - 1 through 15 (of 16 total)
  • Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    Hi @misstomboy,

    I just tried Elementor in combination with this update, and couldn’t reproduce the problem. What exactly is the issue you are experiencing?

    Do you have errors in the developer console? You can check this by right clicking on the screen, then “inspect element”, “console”.

    Thread Starter misstomboy

    (@misstomboy)

    500 (Internal Server Error) that’s the error I get when I activate your plugin and try to use Elementor. I also get the error the page could not be loaded. Here is an example of what I get from their site and how to fix it. It was working fine before I updated so I know it your plugin. I also deactivate your plugin and it works. So I am not sure why after the update it will just stop working.

    https://docs.elementor.com/article/245-preview-could-not-be-loaded?utm_source=editor-panel&utm_medium=wp-dash&utm_campaign=learn

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    If you can enable debugging, by adding the following lines to the wp-config.php:
    define(‘WP_DEBUG’, true);
    define(‘WP_DEBUG_DISPLAY’, true);
    define(‘WP_DEBUG_LOG’, true);

    You will see in the screen and/or in wp-contents/debug.log the error.

    This can tell us what the issue is.

    As the changes in the plugin should only apply to new installs, I suspect you might be low on memory on your site. If that is the case, any plugin deactivation will get your site below the memory limit, an update can cause a memory spike.

    If your debug log shows something like:
    Fatal error: Allowed memory size of 33554432 bytes exhausted, then you are having a memory issue.

    If you post (a part of) the debug log here, or email it to me, I can tell you what the issue is.

    Thread Starter misstomboy

    (@misstomboy)

    Give me a min I will try that but just so you know I tried to deactivate another plugin and have yours activated and still same problem.

    Thread Starter misstomboy

    (@misstomboy)

    I not getting anything at all

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    The issue is most likely a PHP error, to be able to do something about it I need to know what this error is. If you can send me FTP and wp credentials, I can debug the issue. Please contact me directly at support(at)really-simple-ssl.com.

    I just checked, the plugin was updated about 124000 times since the update this morning, this is the only support request regarding the update sofar. This makes me think the issue is specific to your setup.

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    You can also try what using the “deactivate but keep https” option does. Does the issue go away when you use this button? (in settings/ssl/settings)

    Thread Starter misstomboy

    (@misstomboy)

    Well I know it is not my issue and I won’t give anyone ftp because I trust no one. No offence I just have to not trust anyone. I also have not tried that option I will figure it out on my own I guess.

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    ok, I understand. If you have a php errorlog for me I can dive into that (you might need to refresh the file list in FTP), if there’s anything else I can do, let me know.

    Thread Starter misstomboy

    (@misstomboy)

    Thanks not sure where is my php log to be honest.

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    It should appear in the wp-content folder, debug.log, often there is also a file error_log in the root of the site.

    I forgot to add that in the wp-config.php there’s by default a define(‘WP_DEBUG’, false); statement, if you add the other three lines you should comment that one out, or change it to true. Maybe that is preventing the logs from appearing.

    Thread Starter misstomboy

    (@misstomboy)

    I got no logs but I did comment that out

    Thread Starter misstomboy

    (@misstomboy)

    I know you do not think it is your plugin but I just wanted to tell you I tried a different SSL plugin and had no problems. I sorry but I do think it is your plugin but I understand that you do not.

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    I’m not sure of anything at the moment, the problem is mainly that I can’t reproduce it, and I can’t check the actual error, which means I can’t fix it.

    So if it’s Really Simple SSL or not doesn’t really matter until I get an errorlog, or until I can reproduce the issue locally. With an errorlog, I can verify what the problem is and solve it.

    But I’m glad you found a solution!

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    Just checking something: is your home_url in settings/general currently https:// or https://?

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘Plugin caused a problem’ is closed to new replies.