• Resolved Ed G

    (@ed-g)


    Notice: Undefined variable: k in /home/ifjiywnj/public_html/wp-content/plugins/sewn-in-xml-sitemap/includes/sewn-meta/includes/sewn-meta-boxes.php on line 222

    Warning: Cannot modify header information – headers already sent by (output started at /home/ifjiywnj/public_html/wp-content/plugins/sewn-in-xml-sitemap/includes/sewn-meta/includes/sewn-meta-boxes.php:222) in /home/ifjiywnj/public_html/wp-admin/post.php on line 242

    Warning: Cannot modify header information – headers already sent by (output started at /home/ifjiywnj/public_html/wp-content/plugins/sewn-in-xml-sitemap/includes/sewn-meta/includes/sewn-meta-boxes.php:222) in /home/ifjiywnj/public_html/wp-includes/pluggable.php on line 1207

    https://www.ads-software.com/plugins/sewn-in-xml-sitemap/

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter Ed G

    (@ed-g)

    Additional info: This error message appeared after I had installed Google XML Sitemap Generator and experienced errors. I uninstalled that one and installed Sewn In XML Sitemap and started getting the error messages above. I have previously used Sewn In with no problems. Here are the error messages caused by Google XML Sitemap Generator:

    The plugin generated 493 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.

    and

    Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method xmlSitemapGenerator\core::addRssLink() should not be called statically in /home/ifjiywnj/public_html/wp-includes/plugin.php on line 503

    Unfortunately, deactivating and removing that plugin seems to have left traces that conflict with the Sewn In plugin.

    Thread Starter Ed G

    (@ed-g)

    Here is the line of code in Sewn In Simple XML sewn-meta-boxes.php file that generates the error. The k variable is not defined or initialized anywhere in that file.

    $is_valid_nonce = ( wp_verify_nonce($nonce_value, $this->settings[‘nonce’][‘action’] . “_{$k}”) ) ? ‘true’ : ‘false’;

    Thread Starter Ed G

    (@ed-g)

    No response yet. This error happens when the plugin is active and a post or page is published. I’m thinking about just modifying the code myself to comment out the line with the $k variable since there has been no response from the plugin provider.

    I just installed the plugin after a fresh WordPress 4.3.1 installation and the same errors are being logged, even though the plugin seems to otherwise work fine.

    Plugin Author Jupitercow

    (@jcow)

    I don’t get notifications from WordPress forums on new topics which annoys me, so I have to check in to find out there are issues… I am looking at this now. Sorry you had problems. I will see what I can find out and issue a new version if needed.

    Plugin Author Jupitercow

    (@jcow)

    It is weird that it doesn’t output an error for me, but there is a bug. I am uploading a new version to fix this for now. The metabox system is getting converted over cmb2 in the near future.

    Thanks. I will give it a try and let you know whether that change fixed the error message.

    The new Version 2.0.4 works fine at multiple websites with no error messages.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Error Messages’ is closed to new replies.