Copied pages are not detected by the previous/next module

Permalink
When i go to full sitemap and move a page to it's parent in order to copy it (choose the copy page option), i get a new (copied) page that i can rename and edit as i wish. But now if i don't change the position of that new page in the sitemap, it wouldn't get recognized by the previous/next navigation module. It just acts as there were no new page. Clearing the cache doesn't help.

Only if i manually move that page up and down the sitemap or change it's position permanently, it get's recognized as part of the sitemap order by the previous/next navigation module.

I don't know exactly what's going on in the background, but i think, as soon as a page is copied by drag and drop, there should be some kind of automatic refresh in order to let the new page get recognized as part of the sitemap order by the system, not only if this is manually forced.

Can anybody reproduce that issue?

(5.6.1.2)

okapi
 
enlil replied on at Permalink Reply
enlil
I will definitely try to reproduce this after work tonight and hopefully come up with a simple fix. I'll let you know how it goes...