WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] More problems with updating, or saving a draft (12 posts)

  1. StevenDanielFuller
    Member
    Posted 10 months ago #

    I already posted this, but the problem seems to be getting worse. Now when I try to update, or save a draft, in addition to receiving the following warning message, the formatting of my blog post is also being changed.

    Can this be fixed? Thanks.

    Warning: parse_url(http://) [function.parse-url]: Unable to parse URL in /home4/lbfb/public_html/wp-content/plugins/quick-pagepost-redirect-plugin/page_post_redirect_plugin.php on line 1157

    Warning: Cannot modify header information - headers already sent by (output started at /home4/lbfb/public_html/wp-content/plugins/quick-pagepost-redirect-plugin/page_post_redirect_plugin.php:1157) in /home4/lbfb/public_html/wp-admin/post.php on line 235

    Warning: Cannot modify header information - headers already sent by (output started at /home4/lbfb/public_html/wp-content/plugins/quick-pagepost-redirect-plugin/page_post_redirect_plugin.php:1157) in /home4/lbfb/public_html/wp-includes/pluggable.php on line 1121

  2. LapanWebsite
    Member
    Posted 10 months ago #

    Delete quick-pagepost-redirect-plugin

  3. prophecy2040
    Member
    Posted 10 months ago #

    Steven,
    Did you update to version 5.0.6? That has a fix in it for the plugin Warning messages.

    The warning should not be causing layout changes, unless it is displaying on the front end of the site, or if it is preventing special settings from saving.

    If you update to 5.0.6 and still have issues, clear any cache you may have (if using a caching plugin) and if it still happens, let us know.

    Regards,
    Don

  4. prophecy2040
    Member
    Posted 10 months ago #

    LapanWebsite -
    Telling someone to delete a plugin is not necessarily a solution to a problem, especially if they are using it for some form of functionality that they rely on.

    Offering helpful suggestions or a possible work around would be more helpful. I sure when you are looking for help, a comment like that is of no help to you. Be a little more respectful, please. If you know nothing about it, leave it alone and let someone else reply.

    Regards,
    Don

  5. LapanWebsite
    Member
    Posted 10 months ago #

    Telling someone to delete a plugin is not necessarily a solution to a problem, especially if they are using it for some form of functionality that they rely on.

    He/She has "Plugins and Hacks" support.

    Offering helpful suggestions or a possible work around is on plugin author, in plugins support forum.

    It's his/her decision will he/she ask for plugin support, after he/she knows that this plugin is creating errors.

  6. prophecy2040
    Member
    Posted 10 months ago #

    Then nicely tell them where to post their question so it will be answered for effectively. That is helpful.

    And I am the plugin author.

  7. LapanWebsite
    Member
    Posted 10 months ago #

    Yeah, you're right.
    But, people post so many questions, and all I do is to find shortest way to help.
    Luckily you read this out of plugins support forum, and gave better solution.

  8. prophecy2040
    Member
    Posted 10 months ago #

    LapanWebsite -
    Thanks for understanding.

  9. ideabuzz
    Member
    Posted 10 months ago #

    I fixed the problem in the plugin. Line 1157 is looking to parse_url($url) and the variable $url is empty on submissions not using the redirection. Tracing up through the function there is logic that is looking for check boxes to be populated to trigger the creation of the redirection. The variable $_POST['pprredirect_url'] does exist but is empty for normal submissions. By adding an extra condition that the $_POST['pprredirect_url'] must not be blank the routine will be skipped.

    Change line 1185 from :
    if(isset($_POST['pprredirect_active']) || isset($_POST['pprredirect_url']) || isset($_POST['pprredirect_type']) || isset($_POST['pprredirect_newwindow']) || isset($_POST['pprredirect_relnofollow']) ):

    To:
    if((isset($_POST['pprredirect_active']) || isset($_POST['pprredirect_url']) || isset($_POST['pprredirect_type']) || isset($_POST['pprredirect_newwindow']) || isset($_POST['pprredirect_relnofollow']) ) && $_POST['pprredirect_url'] != ''):

  10. prophecy2040
    Member
    Posted 10 months ago #

    This should already be fixed in version 5.0.6, so there should be no need to edit the plugin code.

    If you are using 5.0.6 and still getting the issue, please let me know.

    Regards,
    Don

  11. StevenDanielFuller
    Member
    Posted 10 months ago #

    I am no longer having the issue. Thanks!

  12. prophecy2040
    Member
    Posted 10 months ago #

    Great - thanks for the update!

    Warm regards,
    Don

Reply

You must log in to post.

About this Topic

Tags

No tags yet.