-
-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
“Copy Files” toggle is ignored when duplicating a page #6885
Comments
Hello @linusrogge I've tried on starterkit 4.5.0 and it's working great. Do you have plugins? Also I just wonder that copy and don't copy actions works for you with |
This behavior will be changed with Kirby 5 (already present in the beta): #6567 With Kirby 4, duplicating a page would keep all UUID references as they are. So no matter if duplicating files or not, the old UUID references would always point to the files of the old page. With Kirby 5, we will differentiate between UUID references to files within the page and outside of the page. Those to files outside of the page will always stay the same when duplicating a page. But those to files form within the page (or subpages) will be treated differently: when duplicating files as well, we will replace the UUID references to the files within the old page with those new duplicated files within the new page. When not copying over the files, we will delete any UUID referencing one of those files that didn't get copied. I think this will solve your expected outcome. |
Description
When duplicating a page with images, I have to option to set a toggle whether to copy these files or not. But no matter what option it is set to, the files are always copied.
Expected behavior
When the toggle is set to
false
, no files should appear in the duplicated page.This looks like the problem. Shouldn’t it be
if ($files !== false) { …
?kirby/src/Cms/PageActions.php
Lines 470 to 479 in 94cc37e
To reproduce
Your setup
Kirby Version
4.5.0 (but has been around before)
Your system (please complete the following information)
The text was updated successfully, but these errors were encountered: