Config does not work if cssId field is hidden

[oveleon]

Config does not work if cssId field is hidden

[aschempp]

It's not that much of a deal, but it was unclear to me. I'm using stylemanager in one project because I don't want my client to "need to remember" CSS classes. Because he's not supposed to enter anything into that field, I removed it from permissions.

I would prefer the style manager to work independently for that reason, but I understand the technical challenge. Regardless if the solution, the current situation is just confusing because one might not notice it does not work. I just enabled the field permission for my client now which isn't a problem.

[doishub]

Fixed in 2.5.0

[doishub]

Hi Andreas,

unless the cssId field is allowed to be edited, the callback methods (load_callback, save_callback) are not executed.

Is there a case where the user is allowed to operate the StyleManager, but CSS classes are not allowed to be entered independently?

From my point of view, we would have two options:

1. we disallow the StyleManager to be managed detached from the cssId. For example with an onsave callback for user groups and a corresponding hint.

2. the storage and preparation of the CSS classes no longer takes place via the class fields themselves, but via the onsubmit_callback of the Config (DCA).

That properties are written directly in the cssId field itself, should only occur if a category / CSS group would be removed from the StyleManager set. The reason for this is so that all properties would still be retained for the time being.

[doishub]

Okay, I will have another look at this issue in detail. It is indeed a bit confusing and a solution should definitely be found here.