jmarkweaver

@henner123 You may be correct that this is a different problem. Or maybe it is the same problem. Either way, it would be nice to see someone address one of our questions. :-).

I am having the same issue. My events are showing up 4 hours later than posted listed in the WordPress source. System time is set correctly.

Maybe I fixed this but I am not sure how or why. I had two plugins that were pending updates that I upgraded. I also disabled one unused plugin. I wish I checked after each action, but when I check the “Parent Page” dialog was present and apparently working. Any idea what happened and why? Any idea how to keep this from coming back?

The primary mechanism for setting menu visibility is exactly in its proper location (i.e. Appearance –> Menus –> Menu Structure –> Who Can See This Link). As an improvement, it would be nice to have in a common location (reachable by either (or both) as Appearance –> Menus –> [new tab] -OR- Plugins –> Installed Plugins –> User Menus –> Settings) that shows a “Where Used”. This “Where Used” function would be used help the developer double check that all menus groupings are set the proper level.

In other words, itemize menus that are available with “Administrator” access, “Editor” access, etc.

This might be an opportunity for some level of error or vulnerability checking.

Thanks again for a great plugin.

I am not sure if I am having the same issue, but it appears that this plugin does not work for my pages either. How do I verify if I am using WPML as @benkhalil3 might be using?

My scenario is pretty simple: Add menu and/or sub-menu items based on privilege level (such as Administrator, Editor, Shop Manager). I have tried numerous configurations with setting the condition for the selected page(s) and setting the condition for the selecting privilege level(s).

This was resolved by upgrading the uncode theme to the latest level (2.2.3), then upgrading to wordpress 5.3. I have now lost some .css overrides, but that is a separate and less serious issue. The fix was just made to the version 2.2.3 uncode theme November 13th.