group permalink is bugged

I’m not sure whether this plugin is supported anymore, but just in case…

Hyphened permalinks/slugs break faq group display:

1. When a page is created with a hyphened permalink, faq group does not show on page.
2. When a page is created with a non-hyphened permalink, faq group shows on page.
3. When permalink of working page is changed from non-hyphened to hyphened then again to a DIFFERENT non-hyphened, faq group does not show.
4. When a new page is created with non-hyphened permalink and an existing group is slugged to this new page, faq group does not show on this new page.
5. Creating a new page with non-hyphened permalink then creating a new group and then adding existing faqs to that new group does not work. The new group will not show the existing faqs.

Apparently, group settings are being saved the first time, but changes are not being [correctly] saved, since the permalink and slug MUST be the ORIGINAL non-hyphened one that the page was created with and that the group was initially associated with. Changing the permalink and slug back to the original causes the faq group to show again.

Moral of story, until this bug is fixed: Do not use hyphens in new faq page permalinks at time of first publication and never need to change the name of these faq page permalinks or you’re screwed.

The workarounds are:

1. Create a new page (with non-hyphened permalink), create a new group, create new faqs, then copy and paste content from each individual faq into the corresponding newly created faq and assign them to the newly created group.
2. Put the individual faq shortcodes in the new page and forget about using groups for the affected page.

I have made certain the group slug matches the page permalink. This is not user error.
I get the same result regardless of theme tested. This is apparently not a plugin conflict, as I’m not using any redirect or database plugins and deactivation of other plugins does not fix the issue.
I have also cleared caches and waited hours to ensure any server caching is not at fault.