Sarah Anderson

Thanks for the update and letting me know all is good ??

Hi Patrick,

This plugin was updated last year simply to update the code and I’ve had no problems using it on the latest version of WordPress, I’ve just not had time to update the version tag. However, the idea behind the plugin is outdated due to the introduction of the custom nav menus. Unless you’re using wp_list_pages() in your theme then this plugin is fairly useless to you! And by the looks of things you’re using a lot of other code (I would imagine wp_get_nav_menu_items is pulling menu items from a custom navigation menu).

If you want to have different page titles showing then the WordPress SEO plugin by Yoast does this and much more, and if you want those additional custom fields then the advanced custom fields plugin is great for that job.

Hope that helps.

Great to hear, thanks for the update ??

Just to confirm the new update is now live on the WordPress repository.

Just a further update to this. I’ve finally managed to get the plugin to update in the WordPress repository, so you should be able to just update as normal.

Hi Stevie,

The error is being caused because the site is using an old version of PHP and I updated the markup to bring it more up to date and how I tend to code. I’ve created a backwards compatibility version on GitHub but I’m having trouble getting it updated on the repository. If you want to download and try out v1.3.1 from https://github.com/SarahA21/WP-HideUpdateReminder/releases it would be great to know it’s definitely okay too as I have no access to a server with PHP 5.3 or less on. Although I’m pretty confident it should be fine now.

Thanks

Instead of adding in a PHP version check, I’ve updated the code to allow for backwards compatibility to PHP 5.3 so that you can run the latest changes on older versions.

I’m having issues committing it to the repository right now but if you want to try out the new version you can download it from GitHub – https://github.com/SarahA21/WP-PageMenuEditor/releases

I should get this online tonight when on my own laptop rather than at work.

Hi there, apologies for the time you lost on this. If you use the previous version then it will continue to work on PHP 5.3 and I will update the description to mention this.

I updated all of the code for various reasons and as 5.3 was ended over 2.5 years ago it wasn’t necessarily something I’d considered as I’ve worked on 5.6+ for quite a while now. This is how I code and when rewriting it I wrote it how I code day in day out.

I will add in a PHP version check also to ensure that no one else misses the version comment.

Hi Stevie, sorry for the late reply. I’ve just checked the code and I can’t see an error in that line, however I have a vague memory of fixing an error like it after I’d saved and tested the file. I can’t see my commit logs but possibly the error was committed but then fixed within minutes. I guess you were pretty quick to upgrade!

If possible do you want to try it again and let me know if it’s okay for you now? The new plugin version isn’t a security update as such although it does stop people viewing the file directly, but it’s been upgraded for multisite use and more efficient admin use especially if you potentially have people who can upgrade plugins but not the core files.

I’ll follow this topic so will get a notification if/when you can check on it. I have it running on a few client sites and have no issue on those but it’s always good to check more!

Thanks ??

So, after a lot of echoing out in various parts of the plugin files I’ve discovered that it’s down to my host’s DB not liking the arrow in the post content field (I didn’t change this from the default)

View in Instagram ?

I set the plugin up on my local install of WP and it was fine. I copied the options field over via phpMyAdmin and it was instantly complaining about an encoded character. Once I removed the arrow and altered the string count it worked fine. I can only assume it was this that caused the settings not to save in the first place either.

I’m guessing this is an encoding setting with my DB or server? It’s not major, I can live without an arrow ??

Thanks for your help, I can have a little play with this now ??

Hi Justin, there’s no errors at all showing. I’ve just removed the two option records and tried again, no JS errors showing up. Here’s a screenshot of what I get once I hit save

https://prntscr.com/ez6ym1

I’ll try this on another WP site once the kids are in bed and see if it happens there for me, and I’ll also try reverting my theme back to a standard one plus disable plugins in case something is conflicting with it. Will let you know.

Thanks

Thanks Justin, I did delete them, disabled and re-enabled the plugin and it’s still done it. Everything looks fine until I save the settings and then it just doesn’t show my added user, but it knows its there as the get started changes plus as mentioned, I can see my Instagram user in the option array, but no saved settings (not sure if they would be in either of those options of a third?)

Apologies for the late reply, newborn twins ‘n all that!

The code you want should be something like the below

@$pgmenueditor = get_post_meta($post->ID, 'dsa_pagemenueditor');
if (!empty($pgmenueditor[0]) && count($pgmenueditor[0])) :
  $menu_label = stripslashes($pgmenueditor[0]['menu_label']);
endif;

and then just use $menu_label where ever you want. You may need to vary the $post->ID to the correct code depending on how your loop is written.

Sorry, this is now fixed.

This issue is now fixed.