WordPress.org

Ready to get started?Download WordPress

Forums

Plugin Organizer
[resolved] Does not work with ssl-enabled pages (4 posts)

  1. hsz_36
    Member
    Posted 2 years ago #

    Dear Jeff,
    on pages served via https only the global settings work. The settings from the page or post do not work, regardless whether i want to enable or disable a specific plugin.

    There is one php notice, too:
    PHP Notice: Undefined index: HTTPS in /wp-content/mu-plugins/PluginOrganizerMU.class.php on line 24
    To get rid of this change the line 24 to something like this
    $protocol = (isset($_SERVER['HTTPS']) && $_SERVER['HTTPS'] == 'on') ? 'https' : 'http';

    And there is another php notice:
    PHP Notice: Undefined index: plugin_status in /wp-content/plugins/plugin-organizer/plugin-organizer.php on line 21
    To get rid of this change the line 21 to something like this:
    if (!array_key_exists('plugin_status', $_REQUEST) || $_REQUEST['plugin_status'] == 'all' || $_REQUEST['plugin_status'] == 'active') {

    Thanks for your work and thanks for this fine plugin!
    hsz_36

    http://wordpress.org/extend/plugins/plugin-organizer/

  2. Jeff Sterup
    Member
    Plugin Author

    Posted 1 year ago #

    I have a version that can be set to ignore the protocol. Ive had it ready to release for a while but haven't gotten around to it yet. I will release it in the next few days. It should fix your problem.

    Undefined index notices should not be showing up in your production environment. If they are you have your warning level set to high and you should change it or you are opening yourself up to other problems.

  3. Jeff Sterup
    Member
    Plugin Author

    Posted 1 year ago #

    Sorry it took so long. Been really busy. I got the new version submitted that allows you to ignore the protocol. Let me know if this fixes your issue.

  4. hsz_36
    Member
    Posted 1 year ago #

    The new version fixes the protocol issue and the php notice in line 24. (Which shows up in my development environment, btw.)
    The php notice in line 21 is still there and i would be pleased if you could fix this. I like to have my debug.log as clean as possible, so that the real errors better show up.
    Nevertheless i mark this topic as resolved, since the main issue is fixed.
    Thanks for your work!

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags