Erikvona

I’ve done a thorough review, and identified and fixed the underlying error. Some old code for the storing settings in a file functionality was partly removed, and because of that, the remainder of unused code was generating errors.

If you encountered these errors, they were of no consequence (since the code didn’t run and wasn’t supposed to).

Resolved in the 1.4 version

Thanks. New version just got released, so I’ve done a full compatibility test (about the same you did, plus install/uninstall, with WP-debug on). Added the compatibility tag, marking this as resolved.

Check the changelog if you want to know more.

Thanks for your support and interest.

Erik

There will be an update coming soon fixing some bugs and possibly adding some functionality, which will be tested on WordPress 4.7.

I always review the WordPress changelog for any possible incompatibilities, and use it on my own updated WordPress site. I don’t always do a full test, however.

(I am a sixth-year medical student, so free time for programming is sparse)

Finding all the pages you added content to can be done by querying the underlying MySQL database. The content is stored in the wp_posts_meta table. By joining the wp_posts table, you can identify the posts. You will have to look up the specifics yourself.

Unfortunately, not beginner stuff.

I will look into this. I’m planning to release an update this to next week with some bug fixes, and will look if I can include this.

I think your code will work, except that the do_shortcode should be outside, and not inside the stripslashes:

if(!empty($addtoheadcontent)){
	echo do_shortcode(stripslashes_deep($addtoheadcontent));
}

Else, you will run into errors with slashes being removed in the code your shortcode places, and your shortcode not working if there are any characters in it that should be escaped.

• This reply was modified 7 years, 11 months ago by Erikvona. Reason: mistype

Sorry for replying so late. I don’t believe I can be of aid, since as far as I know, this is not possible. The headers already sent issue can only occur if a PHP error occurs, and a PHP error should show up when WP_DEBUG is on.

I am at a loss. Perhaps you could send me the HTML source of one of the “headers already sent” page?

This is probably either a theming, or a HTML issue. Are you using the appropriate HTML tags? This is not primarily a SEO plugin, so you will need to wrap your SEO description in HTML tags.

Without a link to your website, I can’t help you, but I don’t believe this is a plugin issue.

Fixed this issue. Will be included in the next release.

The plugin was not correctly checking if the current page was an archive page or a normal post/page. Due to this bug if you had a page/post with the same id as one of your tags/categories, it would show the content for the page on the archive page for the category

As far as I know, the plugin is perfectly safe to use with WP 4.6. Haven’t added the compatibility tag yet because I haven’t done the proper tests to guarantee it, but I have checked the WordPress change logs, and there is no reason to assume that any problems will occur with this new WordPress version.

I’m a little lazy with updates lately, still have to get to it but really busy with other things.

With regards,

Erik

I need a more specific error description to try and replicate this issue. Obviously, this is a bug, but I can’t be sure of the cause unless I have a detailed error message or a way to replicate it.

It would be helpful if you could turn on WP_DEBUG, and give me the error message (see this codex page for more information on WP_DEBUG)

You can’t. Category pages and tag pages are not supported. Support might be added in the future, but I have no working version with support for these things yet.

Fixed it for this specific occurrence.

If anyone else has this issue, please make a new support thread. As far as I know, there is no underlying fault in the plugin, and this should not happen for anyone else.

I see. You can use the contact form at evona.nl to send me login information, so I can look at the problem myself. There are several things left to try, but this is a very odd issue.

Could you add comment tags for me on one specific post in the head area, and then send me a link to the post?
Like
<!– per page start –>
your code
<!– per page end –>

But have you also added it to the field for every page, in the WordPress settings menu? Because that would exactly explain this behaviour.

If you add the code twice (once in the settings for every page, and once in the custom field for the page itself), it will get displayed twice. This is intended behaviour and not a support issue.