WordPress.org

Ready to get started?Download WordPress

Forums

All in One SEO Pack
Bug (4 posts)

  1. nigeldeethiopia
    Member
    Posted 1 year ago #

    Line 1157 is throwing notices. Need to update the next update package. I changed it from this

    function post_meta_tags($id) {
     $awmp_edit = $_POST['aiosp_edit'];
    	$nonce = $_POST['nonce-aioseop-edit'];

    to this

    function post_meta_tags($id) {
    	    $awmp_edit = isset($_POST["aiosp_edit"]) ? $_POST['aiosp_edit'] : null;
    		$nonce = isset($_POST["nonce-aioseop-edit"]) ? $_POST['nonce-aioseop-edit'] : null;

    Hope that helps!
    http://wordpress.org/extend/plugins/all-in-one-seo-pack/

  2. Darren Slatten
    Member
    Posted 1 year ago #

    I found a similar bug.

    Version: 1.6.15.2
    File: aioseop.class.php
    Error:

    Notice: Undefined index: aiosp_front_meta_tags in /wp-content/plugins/all-in-one-seo-pack/aioseop.class.php on line 2382

    The fix could be to change line 346 from this:

    $front_meta = stripcslashes($aioseop_options['aiosp_front_meta_tags']);

    to this:

    $front_meta = isset($aioseop_options['aiosp_front_meta_tags']) ? '' : stripcslashes($aioseop_options['aiosp_front_meta_tags']);

    The frustrating part about this particular bug is that the error notice HTML code got printed into the "Additional Front Page Headers:" textarea on the options page. Normally, this HTML would render as a big, ugly, orange-headed table, but since it was wrapped in the textarea tags, it rendered as an inconspicuous block of editable plain text. So when I updated the options, I didn't notice that this textarea field had been populated with the error notice's raw HTML, and I essentially saved the error notice HTML as an "Additional Front Page Header". Then when I viewed the home page, I saw the big orange error notice--despite the fact that PHP loaded the page without any errors. The error notice code was simply being retrieved from $aioseop_options['aiosp_front_meta_tags'] and inserted into the head section.

    Good times.

  3. Peter Baylies
    Member
    Plugin Author

    Posted 1 year ago #

    Thanks to both of you; this is fixed in the 2.0 branch.

  4. jrf
    Member
    Posted 1 year ago #

    The fix contains a typo and the plugin is still throwing error notices....

    To fix, change the line to:
    $front_meta = !isset($aioseop_options['aiosp_front_meta_tags']) ? '' : stripcslashes($aioseop_options['aiosp_front_meta_tags']);

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags

No tags yet.