[resolved] Headers already sent error with Mylinks 4.6 (6 posts)

  1. lecyril
    Posted 2 years ago #


    Unfortunately the last upgrade to Mylinks 4.6 broke my site for all URLs contianing a ? (probably similar problem as reported by mlauten in another topic).

    All URLs containing "?" (e.g. logout) generate a dozen of errors like :

    Warning: Cannot modify header information - headers already sent by (output started at /(...)/wp-content/plugins/mylinks2/mylinks.php:1) in /(...)/wp-login.php on line 368

    I tried to open mylinks.php and options.php and save it with UTF-8 without BOM encoding (I remembered it helped with another similar error with another plugin), without success.

    Any idea?

    Test URL if you want to reproduce the error: -www.around-annapurna.com/wp-login.php?action=logout


  2. lecyril
    Posted 2 years ago #

    I think I solved it, simply by removing the two blank lines at the end of mylinks.php :-)

    I do not get the error anymore. If the plugin author reads this, could you please confirm that these two blank lines should be removed?



  3. Eric J T
    Posted 2 years ago #

    That fix worked for me also. It was scary initially as when I saved the edited file I got just a white page with three error reports instead of two, but I clicked back, then refreshed the editor page and all was well. Thanks so much. Good eye.

  4. lauritasita
    Posted 2 years ago #

    @lecyril - Thank you for that suggestion, that worked for me, too, but the author should still fix this. I was not able to log into my admin at first. I removed the plugin folder using FTP, and then reinstalled the plugin, but I got the same error.

    This should still be fixed and put into a new version. I have two other sites that use this plugin, and I think I will wait until it's fixed.

    I have had a few bad experiences with plugin "upgrades" to give me a stomach ache for one day!


  5. lecyril
    Posted 2 years ago #

    lauratasita, you are right when you say in your other thread that maybe this one should not be tagged as "resolved", since what I found is merely a workaround waiting for the author to be definitely fixed!

    Just to be clear, I decided it to tag it as "resolved" so that other users could know there is a temporary solution out there ...

    Anyway, glad this helped!


  6. 2020media
    Plugin Author

    Posted 2 years ago #

    We have fixed this problem.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic


No tags yet.