Hi team,
PRO’s color scheme for signaling special attributes in certain areas is indeed useful. I.ex. red for looper providers, orange for dynamic content.
I recently made a mistake driven by others’ rush, for which I found the solution (thanks for your support anyway) and that’s why I deleted the thread. However, it gave me the idea to promote this happening to a request for dev.
My problem were some grids displaying image+headline per cell. I began with a looper powered model, to be used at the rest of cases, but client back&forths made me finally go to good old static “voilà”.
But I left 2 cases that had looper consumer setting on at image and headline elements.
After a rapid publication, this (my) error made 6 categories with working grids and 2 with empty black cells, when everything was fine at backend and all grids looked the same, fine at Cornerstone but wrong in production.
Looper consumer without looper provider equals black cells. Image had source, headline had text, but all was overriden by a non-existing data-source.
Could elements with Looper Consumer set on and no Looper Provider have some kind of indication/prevention?
Perhaps a warning when saving? This “framework” idea could be repurposed for more cases.
Thank you for your time, with or without considering the idea.