Admin menu position conflict with HTTPS Mixed Content Detector

  • Resolved Matthew Eppelsheimer

    (@mattheweppelsheimer)


    8 years, 5 months ago

    When I have both Tablepress and the HTTP Mixed Content Detector plugin installed, the “Tablepress” wp-admin menu item overrides the placement of HTTPS Mixed Content Detector’s “Content Security Policy Reports” wp-admin menu item, so that it does not appear.

    When Tablepress is deactivated, HTTPS Mixed Content Detector’s menu item re-appears.

    When both plugins are activated and I add ++$position after line 130 of wp-plugins/tablepress/controllers/controller-admin.php, the conflict is resolved and both items appear in the menu. (I just did this temporarily for debugging purposes.) This switch statement block (lines 121 through 132 of wp-plugins/tablepress/controllers/controller-admin.php) seems intended to prevent conflicts like this from happening.

    This is while running the latest versions of both plugins: Tablepress v1.6.1 and HTTPS Mixed Content Detector v1.2.0.

    https://wordpress.org/plugins/tablepress/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter Matthew Eppelsheimer

    (@mattheweppelsheimer)

    8 years, 5 months ago

    Having looked at the relevant code in both plugins, I suspect (though I am not certain) that this is best resolved on the Tablepress side. But I’ve crossposted this to the HTTPS Mixed Content Detector plugin’s support forum here.

    Plugin Author TobiasBg

    (@tobiasbg)

    8 years, 5 months ago

    Hi,

    thanks for your post, and sorry for the trouble.

    What option have you chosen in the Admin menu position dropdown on the “Plugin Options” screen of TablePress? Simply choosing something else there should be the easiest workaround here.

    Regards,
    Tobias

    Thread Starter Matthew Eppelsheimer

    (@mattheweppelsheimer)

    8 years, 5 months ago

    Well I’ll be. Adjusting that setting resolves this. Thank you, Tobias.

    Plugin Author TobiasBg

    (@tobiasbg)

    8 years, 5 months ago

    Hi,

    no problem, you are very welcome! 🙂 Good to hear that this helped!

    Now, for the actual cause, that’s actually in the HTTPS Mixed Content Detector plugin, in this line. Basically, the plugin is assigning a fixed number for this position, instead of checking which position would be available via the intended mechanism.

    Best wishes,
    Tobias

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Admin menu position conflict with HTTPS Mixed Content Detector’ is closed to new replies.