Juergen Posted April 1, 2016 Posted April 1, 2016 Hello @ all, I want to copy a childpage in the page tree and I always get this error message: Can't save field from a new page - please save the entire page first Saving the entire page doesnt solve the problem. Has anyone an idea why this message appear on the screen. Copying the parent page works quite well. The problem is only at the children. Best regards Jürgen
BitPoet Posted April 1, 2016 Posted April 1, 2016 Are you copying through the UI or API? If the latter, can you show the relevant snippet of code?
BitPoet Posted April 1, 2016 Posted April 1, 2016 Never seen that. Maybe you could use Tracy Debugger to get a full stack trace that points you to where the call to $pages->saveField originates (perhaps some module?).
Juergen Posted April 1, 2016 Author Posted April 1, 2016 Quite good idea! Unfortunately always the loading spinner is beside the title and I get no errors from Tracy. I have tried it with the parent page and I get an error form the Page rename module. But the parent page copy function works. Maybe it has something to do with this module. I use the latest devs (3.0.12)
Juergen Posted April 1, 2016 Author Posted April 1, 2016 Strange behaviour. The copy function works if the page the should be copied is unpublished. If the page is published the duplication fails. Maybe it has something to do with the publish from date field. My setting is that the current date will be filled in if nothing is entered in the publish from field. If I copy this page maybe the publish date will also be copied and then it will be in the past. Could this be a reason?
BitPoet Posted April 1, 2016 Posted April 1, 2016 You mean the Schedule Pages module? That's actually possible. From a quick glimpse, it hooks before Pages::save and, if a publish_from date is set, tries to clear that and calls "$page->save('publish_from');". This line should probably only be executed if $page->isNew() returns false. 1
thlinna Posted August 29, 2016 Posted August 29, 2016 I ran into exact same problem. Only (working) solution I've come around is to uninstall the Content Scheduler module. Is there any bug fix or way around this issue for a PW novice?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now