Open purquhart opened 1 month ago
Hi @purquhart, thanks for report, to successfully resolve issue i need some information:
Hi @tkrch it is version 29.1.0. Are you just wanting to see the View_CMS_Tree_Joined data for the relevant pages similar to #215?
@purquhart i have identified issue, fix is on the way!
Hi @tkrch this is still an issue - the fix did resolve #216 though.
@purquhart there is still opened PR #224 with changes related to this issue. Please wait, i will notify you
@purquhart all changes were published to master branch, can you check if issues still persists? If so, can you send me backup of database where issue can be simulated (preferably anonymized)?
Hi @tkrch issue still exists, sending you a backup of the db via email
Please verify if issue was resolved with recent changes merged into master branch, Thank You @purquhart
Hi @tkrch no that didn't work, but I have found a workaround for this which is after migration to drag the pages into a child section of the tree and then drag them back to the original location.
Good catch that workaround @purquhart, thanks for sharing! I did migrations with DB You supplied and found some additional operation that needed to be done. Fix is include in feature branch #243. You can test with this branch or wait until its merged. Solution included is correct trimming of '/' and some fixes related to inherited page types
For pages that were migrated which were based on non-page builder content types, they do not route and render unless they are manually recreated in the admin ui, and then they work. I did notice that all of the imported pages contain // in their url that is displayed in the content section of the page instead of a culture. e.g. "http://site.com//home" whereas the recreated ones display without the double-slash, and include a culture variant when it is not the primary language e.g. "http://site.com/fr-ca/home".