Rincewind

No worries glad its working for you.

I see ok I have tried to google this, and wasn’t able to find anything at all on this, still learning how to code wordpress plugins correctly as intended, the wordpress site itself doesn’t mention anything at all about this, but have made the suggest change hope this is what you was wanting and that I did it correctly.

Sorry but am unable to make this requested change for one reason, using this method of add_action(‘init’, …) would mean that my localization language files would be included on every single page in the admin area, and on the public site also, this would be inefficient imo.

The file should only be included as and when its needed imo.

Sorry what I meant was are they currently showing in the navigation on your site as it stands at the moment, ? disregarding what is showing in the sitemap created by my plugin.

If they are showing and you dont wish this, why dont you change the visibility of the pages to private ? this will remove them from the sitemap created by my plugin, and it will also remove them from the navigation on your site, you will still be able to view these pages if you know there path, they just wont be in the navigation.

Hope this helps, if not please say.

Thank you very much have submitted back to the plugin page, and creditted you also for it, thanks once again.

There isn’t no, how do you hide them at the moment ? by category ? or by individual id’s ?

Do you know why when I generate the .pot file from within the admin area for the plugin, that it everything after “#. Plugin URI of the plugin/theme” at the bottom of the file?

When I use poedit it doesn’t add this at the bottom, which was how this problem has arisen.

But have made the necessary changes to the files, and has been submitted should be live shortly.

I’ve updated the plugin now so all entries are now in the pot file.

I have used poedit for this, so there is a .po file in there also, am not 100% sure I have done it correctly tho.

This should now be rectified with the new plugin structure.

This should now be rectified with the new plugin structure.

Thank you for the response, however wp_footer doesn’t give me the results I was looking for.

If I follow the code here : https://codex.www.ads-software.com/Plugin_API/Action_Reference/wp_footer

This is what I get in my html : <p>This is inserted at the bottom</p></body></html>

This is too late I need the code to be after the opening body tag, and not before the closing one, do you have any more ideas as to how I can do this ?

This should be in the file on line 109

109: #: wp-realtime-sitemap.php:174
110: msgid “Post limit”
111: msgstr “”

This has been reported already, you just need to click the submit button on the options page and this error will go away and the page will then show your content.

But I will look into whats causing this.

Thats to get the settings out of the database for the first time the form loads after first installation, but I guess its trying to get the settings out of the database before they have been inserted, it wont affect your use of the plugin but I will look into whats causing that.

I have since fixed this now, didn’t realise that admin_init on every page aswell as when the plugin first gets activated.