• Resolved mikeotgaar

    (@mikeotgaar)


    Latest version (2.0) produce error notice in Dashboard

    1st message:
    Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at ****/wp-content/plugins/easy-modal/includes/admin/sidebar.php:2) in ****/wp-content/plugins/easy-modal/classes/admin/notice.php on line 6

    2nd message:
    “Headers already sent in ****/wp-content/plugins/easy-modal/includes/admin/sidebar.php on line 2.
    This is not a good sign, it may just be a poorly written plugin but Headers should not have been sent at this point.
    Check the code in the above mentioned file to fix this problem.”

    Also Note: The plugin does not uninstall cleanly – leaves this reference in the database – probably as a transient. I haven’t yet checked, but will have to edit the DB to clean this up.

    First time Easy Modal has given a problem on any of our sites

    https://www.ads-software.com/plugins/easy-modal/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Daniel Iser

    (@danieliser)

    Thanks for the report, this has been patched and an update to v2.0.1 is available.

    Plugin Author Daniel Iser

    (@danieliser)

    There was an extra whitespace before the opening <?php tag in the sidebar, should have had no effect on your DB or options etc.

    Im not sure what you mean about leaving reference in the DB. most of the settings are stored in the DB and wont be removed upon uninstall. As they should not be. If you had to uninstall one version to manually install another you wouldn’t want to have to reconfigure everything.

    Plugin Author Daniel Iser

    (@danieliser)

    After further digging we are at a loss as to how the whitespace got there as we have been using this exact same version on our own site for nearly a week with no issues, no error or downtime, it wasnt till i uploaded it to wp.org svn that that space appeared. Its not even in our private git copy.

    I do appologize and we are working very quickly to resolve all upgrade issues. Please let us know what you think about the upgrades to the theme editor.

    Thread Starter mikeotgaar

    (@mikeotgaar)

    Issue resolved now. Excellent response to bug reports too!
    FYI:
    The error message in dashboard (was inserting in the JetPack stats graph field) persisted after updating to 2.0.5. I dropped the database tables (copied created modal data first) before installing 2.0.7
    I guess it was just a transient anyway…

    On retaining settings and data (clean un-install)
    I was meaning that the plugin should clean out it’s settings when being deleted (per recommended practices), not de-activated only.
    Perhaps in time you could add a checkbox at the un-install confirmation step to delete the settings and data like several other plugin do. (Lot of extra work I know, but a good idea for the less tech savvy who may have difficulty editing the database directly through PHPMyadmin)
    Easy Modal still has 5 star rating from me.

    Plugin Author Daniel Iser

    (@danieliser)

    Hey mike, the functionality to clean up is there, but no option exists yet, we are gonna add migration tools to settings page to assist in corrupted migrations like some people experience, will also include uninstall button.

    As far as when plugin is deleted that goes back to what i said before, in order to manually install an update via the dashboard you have to disable and delete the existing plugin, then reinstall the new version.

    So if we hooked the delete and deleted all your settings when you updated, you wouldnt be happy so that wont change, but adding a button isnt a huge undertaking.

    Thanks for the feedback and be sure to rate and review the plugin after you try out the new theme editor and positioning.

    Thread Starter mikeotgaar

    (@mikeotgaar)

    Thanks danieliser

    Yeah – I prefer choices to do things so fully agree with what you say. It’s not a problem for me to edit the database, but there are a lot of WordPress users who can’t – one reason I get paid by clients to manage their WP installations ?? – so it’s always good to make things easy for them…

    I didn’t mention before – the site with the error was a 3.8.3 multi-site install (my own, and I don’t like 3.9.* at all, so will keep it until there’s more options to remove things like the new editor).

    Now I’m sure EM is working I can start updating the customers…

    Plugin Author Daniel Iser

    (@danieliser)

    Glad to hear.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘PHP Error – Headers alreday sent’ is closed to new replies.