hrsms

I wrote: “In addition, I had no issues when adding more menu items.”

I found it was inconsistent.
I deleted 9 sub items and now things are working. I guess you may consider it resolved from my end.

Thanks.

As indicated initially, I get the same result with all other plugins deactivated.

This is my menu structure. There are indeed a lot, but I’m shocked this is too many, particularly when the same behavior is seen with no other plugins active. In addition, I had no issues when adding more menu items.

I’ll continue to test.

1
1.1
1.2
1.2.1
1.2.2
1.3
1.4
1.5
1.5.1
1.5.2
1.6
2
2.1
2.2
2.3
3
3.1
3.1.1
3.2
3.2.1
3.3
3.3.1
3.3.1.1
3.3.1.2
3.3.2
3.3.2.1
3.3.2.2
3.4
3.4.1
3.4.2
3.4.3
3.4.4
3.5
3.5.1
3.5.2
3.5.3
3.5.4
3.6
4
4.1
4.2
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.2.6
4.2.7
4.2.8
4.2.9
5
5.1
5.2
5.3
5.3.1
5.3.2
5.3.3
6
7 <--- this is the problem one
8
8.1
8.2
8.3
9

My problem continues, but as juliushg?reported, it is not with every element. I cannot take the time at the moment (at my paying job, which the WP site is not), but I will look closer to identify what might make it different. Could it be that it is a custom link with no URL (serves as inactive top level menu item), rather than a page? Is there anything unique about your menu element, @juliushg?

Thanks, George.

I had indeed done some light reading and understood the template hierarchy. I also understood that page.php was pulling in headers, footers, etc. which is why I mentioned the particular line pulling in the content and why I wasn’t surprised the headers and footers disappeared. I was only experimenting to prove to myself that the page-{slug}.php would be used.

I didn’t state all of this because I was trying to be reasonably brief, which apparently was a good idea because you already thought it was TL;DR; ??

Copy/Paste/Edit of page.php also had occurred to me, but at the same time it occurred to me that this means I would have to manually apply any changes to the theme going foward. I was hoping that, similar to the template hierarchy, there was some hieararchy with get_template_part( ‘content’, ‘page’ ), where I could replace the template “part”. If that exists, I don’t know where it is. If it doesn’t and there is no other way to specify only the content part, I will resort to Copy/Paste/Edit of page.php.

Thanks again for your reply.

I forgot to mention, I was also able to use the Pods blocks yesterday, with Widget Options activated, before it was automatically updated today on my site.

I tried disabling “Gutenberg Page & Post Block Options”, but that had no effect.

• This reply was modified 8 months, 1 week ago by hrsms.

I’ve confirmed the same behavior described by Lock. Today’s update also breaks Pods (Custom Content Types and Fields) blocks. I’ll post that separately, as I know it’s off-topic for this thread.

I wrote:

“I’ve since found a custom post type that was created automatically (‘portfolio‘ from Visual Portfolio plugin). Some of the capabilities are in the Custom group instead of the Portfolio Items group. I’d like to move them.”

Please ignore this also. I saw the note about members_unregister_cap_group.

I also used this for the Pods custom post types, as not all of the related capabilities get added to the automatically created groups.

I wrote:

“(Pods is fairly popular – you might consider working with them to make your two plugins compatible).”

Please ignore. In the Pods admin I can change the type from page or post to Custom Type and the group appears automatically.

I’ve used your snippet to create a new group.

I’ve since found a custom post type that was created automatically (‘portfolio‘ from Visual Portfolio plugin). Some of the capabilities are in the Custom group instead of the Portfolio Items group. I’d like to move them.

Would it work to call members_register_cap_group using an existing group name but passing the new capabilities only? The complete set, new and old?

If not, how can I do this?

Thanks.

• This reply was modified 2 years, 2 months ago by hrsms.

I know only enough about WordPress programming to get myself in trouble, but I managed to avoid trouble this time.

You wrote:
“…if you see capabilities from deleted plugins”

There is no deleted plugin, rather deleted custom post types created with the active plugin (Pods).

With a little searching, I found how to delete the obsolete capabilities and add the missing capabilities using temporary ‘admin_init’ actions added to the end of my theme’s functions.php file (remove_cap / add_cap).

Your snippets page has a note:
“Note that custom post types are automatically registered as groups with Members.”

Groups are not being registered for custom post types created using the Pods plugin. It would be handy to group them, so also managed to use your members_register_cap_group snippet to do so. Thanks for all the information!

(Pods is fairly popular – you might consider working with them to make your two plugins compatible).

It is asking for a purchase code. Is support for Pro only?

Yes. It was just downloaded yesterday for the first time. I checked the version and it is indeed 5.0.6.

• This reply was modified 2 years, 2 months ago by hrsms.

I confirm the issue is fixed on my end. Thank you very much for addressing this issue.

Hello Hannah. I would like to know the answer to Damian’s question, but of course I cannot see the Facebook response. Would you please copy it here?
Thanks
Greg

It works for me now also. Thanks for the fix.