Title: Bug
Last modified: August 20, 2016

---

# Bug

 *  [nigeldeethiopia](https://wordpress.org/support/users/nigeldeethiopia/)
 * (@nigeldeethiopia)
 * [13 years, 10 months ago](https://wordpress.org/support/topic/bug-13/)
 * 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/](http://wordpress.org/extend/plugins/all-in-one-seo-pack/)

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

 *  [Darren Slatten](https://wordpress.org/support/users/darren-slatten/)
 * (@darren-slatten)
 * [13 years, 10 months ago](https://wordpress.org/support/topic/bug-13/#post-3233076)
 * 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.
 *  [Peter Baylies](https://wordpress.org/support/users/pbaylies/)
 * (@pbaylies)
 * [13 years, 10 months ago](https://wordpress.org/support/topic/bug-13/#post-3233091)
 * Thanks to both of you; this is fixed in the 2.0 branch.
 *  [Juliette Reinders Folmer](https://wordpress.org/support/users/jrf/)
 * (@jrf)
 * [13 years, 10 months ago](https://wordpress.org/support/topic/bug-13/#post-3233102)
 * 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']);`

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

 The topic ‘Bug’ is closed to new replies.

 * ![](https://ps.w.org/all-in-one-seo-pack/assets/icon.svg?rev=2443290)
 * [All in One SEO – AI SEO Plugin to Boost SEO Rankings & Traffic (Schema, Local SEO, Sitemap & SEO Insights)](https://wordpress.org/plugins/all-in-one-seo-pack/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/all-in-one-seo-pack/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/all-in-one-seo-pack/)
 * [Active Topics](https://wordpress.org/support/plugin/all-in-one-seo-pack/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/all-in-one-seo-pack/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/all-in-one-seo-pack/reviews/)

 * 3 replies
 * 4 participants
 * Last reply from: [Juliette Reinders Folmer](https://wordpress.org/support/users/jrf/)
 * Last activity: [13 years, 10 months ago](https://wordpress.org/support/topic/bug-13/#post-3233102)
 * Status: not resolved