Since update, if I clone a page, all HTML lost at front end

Support
#1

So a few days ago I updated Pro. Since then a weird issue as shown.

  • Create a post and edit in Pro with some elements. Save page all good.
  • Clone a page (I use Yoast but tried another cloning plugin)
  • Edit the cloned page with Pro and at backend exact copy. But if I try and view that cloned page at front end, all the html coding is lost.
  • Workaround. Save all elements as a template, delete the elements, load them back and press save, page displays as intended.

I will place a test page in secure note.

#2

Secure note

#3

Hi Ashley,

Unfortunately, we are not able to find the difference between these two pages and look very identical. If that is not the case and you are trying to point out something else, please provide any screenshot marked with the issue or any video that help us to recognize the problem.

NOTE: Moved the login credentials to the secure note for security purposes.
Thanks

#4

How strange, it looks ok to me too now. I cloned another page and it looks wrong.

So this is what the test page should look like (as you have seen).

Shouldlooklike
Shouldlooklike3290×677 63.2 KB

If I clone that page again, at backend it looks ok, but at front end this is what it looks like (all HTML stripped).

NewClone
NewClone1725×631 43.9 KB

#5

I will update the secure note with the latest test page

#6

Hi Ashley,

In this case cloning the page is not able to copy the Element CSS of that page and that is why the output is different than the main page. It seems that the issue is not related to the theme or bundled plugins, I would suggest you contact the plugin author in this case.

Thanks

#7

It does copy the elements though, as they all show at backend in Cornerstone?

#8

Hi Ashley,

Right after you clone the post, open it in Content Builder (Edit with PRO), in the Content Builder change its status then save, (if its draft, then published it) so it will have a proper cornerstone data, you can then just set it back to draft or private after.

You might already know, but the Content Builder has its own native cloning feature (https://prnt.sc/11sbb5h). You might want to use that instead.

Hope it helps,
Cheers,

#9

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.