WordPress.org

Ready to get started?Download WordPress

Forums

Plugin Organizer
[resolved] Per-page/post enabled plug-ins do not load for SSL URI (7 posts)

  1. belg4mit
    Member
    Posted 1 year ago #

    I am using the latest version of the plug-in (2.5.6),
    but a per-page plug-in (amr events calendar or lists with ical files)
    will not load when accessed as HTTPS.

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

  2. belg4mit
    Member
    Posted 1 year ago #

    I overlooked the "Ignore protocol" setting, though it should probably default to on; cannot imagine why you'd want it disabled.

  3. Jeff Sterup
    Member
    Plugin Author

    Posted 1 year ago #

    It was built without the ignore protocol setting. That was added later. To default it to on now would cause issues with people who are already using the plugin.

  4. belg4mit
    Member
    Posted 1 year ago #

    It was built without the ignore protocol setting. That was added later. To default it to on now would cause issues with people who are already using the plugin.

    It's not clear it would. Do you know of many users whom want to change the plug-ins that are loaded based on whether or not SSL is used? It seems a very specialized thing.

    It is also possible to have the default for new installs not affect the existing settings...

  5. Jeff Sterup
    Member
    Plugin Author

    Posted 1 year ago #

    The setting didnt exist so it didnt ignore the protocol before that option was added. If I switched to on then it would have different functionality and would cause problems. For it to behave the same way it has to default to off. I added that option because I needed it on one site but I have others that need it to load different plugins on ssl pages.

  6. belg4mit
    Member
    Posted 1 year ago #

    It still makes no sense to me that one would ever want it off.
    However, if it is really worth having such an odd behavior,
    it would still be best to default to on per the "principle of
    least surprise" for new users.

    It is not necessary to default to off just to support legacy
    users whom may or may not want such an awkard setting. The
    sense of the test can simply be inverted and the setting given
    a new name, with old settings carried over and inverted on
    upgrade ;-)

    .                      Current                 Future
                          (ProtocolSensitive)    (ProtocolInsensitive)
    pre-setting existence  on                     off
    1st setting default    on                     off
    1st setting changed    off                    on
    new setting default    off                    on
    new setting changed    on                     off
  7. Jeff Sterup
    Member
    Plugin Author

    Posted 1 year ago #

    Its not a surprise if you take the time to look over the settings before using the plugin.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic