Webrocker Posted December 19, 2018 Share Posted December 19, 2018 Hi, there are some things that need to come together to reproduce this, so not sure if this is a bug, but since this fell on our feed in a production site just now, I wanted to document it here. Happened in production with a 3.0.33, tested additionally with a fresh empty local ProcessWire 3.0.98 Master in "blank" profile. Modules needed to be active: ProFields:PageTable v0.1.3, Page Clone (Core) v1.0.3. Settings (see settings.png attached): Have a dedicated page where the PageTable elements are to be stored (so not save them as a child of the page that has the PageTable field) Have the "Page behaviors" set to unpublish an element when its parent is unpublished Steps to reproduce: Create a page with the PageTable field. Create some content items with the page table field. Publish the elements and changes to the page. Look in page tree at the page that stores the PageTable elements. As is to be expected, you see the elements, published. Now, click on the name of the page with the PageTable field, and choose "copy" from the actions (this only appears when you have installed the PageClone core module). Now you have a (unpublished) copy of the first page. Look again in the page tree for the stored PageTable elements: Now you have twice as many elements, and ALL are unpublished. So by duplicating a page, the contents of the original page are altered/unpublished. Since this is unexpected and happens without any indication to the editor, this creates a bad situation esp. for pages where already a mix of published and unpublished PageTable elements has been before. Expected behavior: Leave the original page and Pagetable elements alone ? aka wouldn't expect that making a copy of a page will alter the published state of the origal page's contents. Also (not directly related to this effect) expected to see the copied PageTable Elements suffixed with "(Copy)" in the page tree, as it happened with the copied page. See screenshots for illustration. Link to comment Share on other sites More sharing options...
dotnetic Posted December 19, 2018 Share Posted December 19, 2018 @kongondo I think this should be moved to https://processwire.com/talk/forum/42-table/ Link to comment Share on other sites More sharing options...
Webrocker Posted December 19, 2018 Author Share Posted December 19, 2018 @jmartsch that link seems broken? (btw I'm fine with moving to a more fitting place, posted here b/c I wasn't sure which module or the combination of modules and non-standard settings causes this) ? Link to comment Share on other sites More sharing options...
dotnetic Posted December 19, 2018 Share Posted December 19, 2018 As a ProFields buyer you should have acces to the ProFields support forum. This would be the correct place to get support for the table module. Link to comment Share on other sites More sharing options...
Webrocker Posted December 19, 2018 Author Share Posted December 19, 2018 Ah. But this is the interesting thing; I downloaded a plain new processwire w/o any additional modules. installed it locally with a new db. The module was already there, needed only to be activated. I think this used to be a ProField, but now is core, but kept the name (?) Link to comment Share on other sites More sharing options...
Webrocker Posted December 19, 2018 Author Share Posted December 19, 2018 Ok, I think you are referring to the "Table" field; but my issue is with the "PageTable" field. ? Link to comment Share on other sites More sharing options...
kongondo Posted December 19, 2018 Share Posted December 19, 2018 Yes. PageTable is a free ProFields module ?. I'll still move this topic though to general support. Link to comment Share on other sites More sharing options...
Robin S Posted December 19, 2018 Share Posted December 19, 2018 Both FieldtypePageTable and ProcessPageClone belong to the core, so if the issue is consistently reproducible you could add it to the ProcessWire issues repo: https://github.com/processwire/processwire-issues/issues Link to comment Share on other sites More sharing options...
Webrocker Posted December 20, 2018 Author Share Posted December 20, 2018 Thanks @Robin S @kongondo , will make an submitted an issue on github: https://github.com/processwire/processwire-issues/issues/772 Link to comment Share on other sites More sharing options...
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