Erikvona

You just probably forgot to check it under screen options. Check it under screen options when editing a page.

Also, check if your user role is allowed under Settings -> Per Page Add To Head (or just allow all roles)

I will try to fix this problem next version, though I can’t explain why the conversion on display was not working.

I originally introduced the %BREAK% after version 0.3, which preserved line breaks with \n as you suggested, but due to weird handling of MySQL escaping and storage line breaks weren’t preserved in most configurations.

If you want, you can still download version 0.3 from SVN (here). The error won’t occur then, but white space will probably not be preserved.

My solution wasn’t a good option, but it worked for everyone until now. I will try to properly fix it next version, which I will try to release soon.

Of course, but you will need to use PHPMyAdmin or another MySQL interface.

You can use the following query:

SELECT *
FROM wp_postmeta
WHERE meta_key = 'per-page-ath-content'

Where wp_ is your database prefix.

You can also automatically delete empty meta fields using a query like this.

There is no way to do this from the plugin.

Note that the options and the content added to every page isn’t shown in this list

Hey,

I guess this is a general notice, because in all my PHP files, everything is either a call to a built-in WordPress function, or the creation of a new function. So if you directly access one of the PHP files, the only thing that is going to happen is it’s going to throw an error because of an undefined WordPress function, or it’s going to do nothing because it’s just setting functions and not executing them.

Still, this can’t really hurt (except it increases the plugin’s size and running time by a tiny bit), so I guess I’ll include it in the next update. But I won’t push an update just for this, because it’s not a security issue in this plugin.

Hey,

With so little detail, I can’t really help you. Did you try adding something for every page, or for a specific page? You could check if one works, but the other doesn’t.

One problem might be the sitename/index.php/postname notation. That’s not commonly used, and I haven’t tried my plugin with that notation.

Sorry, but I can’t just magically solve something, without knowing exactly what is going on. You could try turning on WP_DEBUG and see if there are any error messages.

Sorry, I have tried a couple of things, but still can’t replicate the error. Modifying existing fields and adding new ones is done by the same functions, so it’s really weird you can do one, but not the other.

I would love to have a look at your exact configuration so I can see what is going on, but for now, the editing custom fields is the best I can do, I guess…

Dear Cyberhomes,

Thanks for using the plugin.

Unfortunately, I can’t replicate the error. I can only speculate to most likely causes
This error is most likely caused by the new rights system, since it’s the only real change in the new version. A fresh installation causes administrators to have the correct rights, but when you update, you need to manually set the rights, as mentioned in the changelog. Most likely something has gone wrong there.

– Go to settings -> per page add to head, and check the roles and post types you want to use after the update. Administrator should be auto-checked. Change something in the roles. Press update. Change it back. Press update again.
– Reinstall the plugin. A fresh installation will grant administrators the correct rights. You will need to set the “Add to every page” field again, but all per page content will not be lost.
– If both these don’t work, you can always change the “add to head” content when editing a page by clicking screen options, checking “Custom fields”, and changing the “per-page-ath-content” field.

Sorry for the bug you’ve encountered. Let me know if this works, and which one worked.

I will mark this as resolved. This theme is tested and compatible with WordPress 4.2.2, and without any specifics on what doesn’t work, I can’t help you.

Sorry, but you can’t. These pages are auto-generated by your theme, and my plugin can’t influence them. You can add things to every page, though, and you could use JavaScript to effect specific pages. But this might not be the best option.

Some themes support custom tag and category sections, if this is so, you can create a page for each tag and category and add the content there.

Simply put, no, this isn’t possible with this plugin.

If you have experience with PHP, though, you could modify your theme to include this. And if you would want to insert code on a per-page basis, you could add a hook to your theme, and modify this plugin to insert on that hook, and not wp_head(). But by default, there is no hook to insert attributes to the <html> tag.

Note that you should read up on modifying themes before doing it, and perhaps use a child theme.

That is curious, it should say https://localhost/wp-admin/etc&#8230;
I cannot replicate the error, I have a testing version under localhost which works fine. It might be server-related, since the plugin uses the server to reconstruct the request URL.

You can probably fix this by editing the plugin and changing the following code in settings.php
Line 110: ?><form method="post" action="<?php echo $currenturl; ?>"><?php
To:
?><form method="post"><?php
If I release an update, I will probably include this change, but since the error is probably server-related and doesn’t occur on my testing server nor my shared hosting server, the impact of this bug is probably small, so I won’t make an update only for this error.

Let me know if you’ve made the change and it still isn’t fixed.

Hi David,

Thanks for reporting this error. I have updated the plugin, it is fixed now. Sorry for the sloppy testing, made a stupid mistake in the 1.2 update and didn’t test the installation function.

Anyway, you can update or download it again, and it will be fixed.
Hope the support is fast enough for you ??

Custom post support is added in version 1.2, which will probably launch today. You can now set the custom post types you want to add stuff to under Settings -> Per Page Add To Head.

Custom post support is added in version 1.2, which will probably launch today. You can now set the custom post types you want to add stuff to under Settings -> Per Page Add To Head.

Capability and role support is added in the 1.2 update, which will probably launch today (a new capability, add-to-head, is added, and because some admins will want editors or even users to be able to do this, and a management page is added to assign this capability to the available roles. Administrators have this capability by default, and this cannot be removed).

Thanks for the tip!