Conflicts with NextGen Gallery and TinyMCE

  • model13

    (@model13)


    11 years, 6 months ago

    We have several multisites currently running WP 4.01, and all our plugins are up to date. A snapshot of our setup:

    1. We have multisite configured with subdirectories, not subdomains.
    2. SSL is forced on the login and admin pages. We’re required by to use SSL on login pages integrated with the university ID system.
    3. We have wildcard SSL for one of the series of mapped domains we commonly use (*.campus.university.edu) but cannot obtain one for the other series (*.university.edu).
    4. We do not apply the mapped domains to admin pages because numbers 2 and 3 cannot be reconciled.
    5. Remote login ability is enabled in the MU Domain Mapping settings.

    In a nutshell, the plugin’s function get_original_url() is called repeatedly and at random times depending on the individual sites’ and pages’ setup, and each time it is it adds the pre_option_siteurl filter back in. It’s the same issue identified in https://wordpress.org/support/topic/remote-login-is-not-working-with-recent-update.

    With NextGen Gallery this filter is causing gallery image uploads to fail.

    With TinyMCE, if the site’s primary domain is in the *.university.edu series, the editor disappears from posts and pages. We’re running the TinyMCE Advanced plugin, but this problem has to do with TinyMCE itself, and deactivating or uninstalling the plugin makes no difference.

    When the add_filter() line is commented out in get_original_url(), both broken features begin working again.

    The problems were first noticed this past spring, but we did not realize until working on MU Domain Mapping issues this past week that they were tied to this plugin.

    I’ve been able to restore a semblance of sanity to our admin pages by creating a must-use plugin that attaches a remove_filter() to almost every possible action hook, but it’s a clumsy solution to the problem. It would be better if the plugin could do an is_admin() check and not apply filters changing the siteurl and home values unless sites are explicitly using the mapped domain in the back end.

    https://wordpress.org/plugins/wordpress-mu-domain-mapping/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter model13

    (@model13)

    11 years, 6 months ago

    For clarity’s sake, just a mention that this is with Version 0.5.5 of MU Domain Mapping. However, these two particular issues predate that release.

    We’re going to 0.5.5.1 this afternoon, but I had already begun patching things before it became available. We decided to hold off on the update a little longer in order to document the issues. We’re still checking on several other reports of plugin conflicts and disabled features.

    Thread Starter model13

    (@model13)

    11 years, 6 months ago

    We updated to 0.5.5.1, and I tried, without luck, to reproduce the problems we’ve been having with NextGen and TinyMCE. We updated several plugins at one time this past week, including NextGen Gallery, so our original belief that these problems were indeed caused by something else last spring is probably correct. It looks like the last round of updates fixed those bugs but 0.5.5 introduced a new one so the net change was nil.

    Both NextGen and TinyMCE appear to be fully functional with 0.5.5.1, even when I disable the code I wrote to remove the filters added by 0.5.5.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Conflicts with NextGen Gallery and TinyMCE’ is closed to new replies.