Page defaults: Great feature/functionality but lacks realiability
Permalink
It's just recently that I have introduced myself with page types and page defaults. I really like the idea but hate (very much) how most of the changes I make to page defaults don't reflect on existing pages, be it for page attributes block(s) I add or composer controls.
I tried with just changing vertical positions of two different composer controls. Changes weren't reflected on an existing page of that type. It's frustrating not knowing what causes this - is it a bug or me not doing it right?
I also tried with adding a page attribute block. These have this option to apply or remove from child pages. On only one occasion did I manage to reflect it on an existing page, by several add to / remove from existing page. After that, all attempts failed.
The idea behind page types and page defaults is really really nice and I was looking forward developing a bunch of pages of a type but now I'm not sure if I want to dive into it because I know I will be adjusting the defaults pretty much.
P.S. I just noticed the following as well:
Using Setup on child pages is messy as well. If you go around and enable/disable page attribute blocks for certain pages, after they are re-enabled, they end up at the bottom of a column, for example, notwithstanding the fact such block was at the very top prior to removing it from that page.
I tried with just changing vertical positions of two different composer controls. Changes weren't reflected on an existing page of that type. It's frustrating not knowing what causes this - is it a bug or me not doing it right?
I also tried with adding a page attribute block. These have this option to apply or remove from child pages. On only one occasion did I manage to reflect it on an existing page, by several add to / remove from existing page. After that, all attempts failed.
The idea behind page types and page defaults is really really nice and I was looking forward developing a bunch of pages of a type but now I'm not sure if I want to dive into it because I know I will be adjusting the defaults pretty much.
P.S. I just noticed the following as well:
Using Setup on child pages is messy as well. If you go around and enable/disable page attribute blocks for certain pages, after they are re-enabled, they end up at the bottom of a column, for example, notwithstanding the fact such block was at the very top prior to removing it from that page.
All cache settings have been turned off. But I just deleted cache anyway, just to make sure. Then I went to my page defaults, and since there was a column with 4 blocks in it (all page attributes), I removed the second one from top from all three existing pages of that type.
Then I went to one of the pages, hit F12 (and no, no errors in console, btw) and then hard reloaded with cache clearing (in Chrome, long press on reload button in the toolbar). That block/attribute was gone, as expected.
Then I went back to page defaults and re-enabled the block back to all pages. Went back to the actual page, again hard-reloaded and - the block was sitting in the bottom, instead second from the top.
Sounds like a bug to me.
Then I went to one of the pages, hit F12 (and no, no errors in console, btw) and then hard reloaded with cache clearing (in Chrome, long press on reload button in the toolbar). That block/attribute was gone, as expected.
Then I went back to page defaults and re-enabled the block back to all pages. Went back to the actual page, again hard-reloaded and - the block was sitting in the bottom, instead second from the top.
Sounds like a bug to me.
Try clearing the cache of your browser and concrete5's cache.