[Hiyou]

Hi Ally,

Will this be in for the next release? Thanks!

[Hiyou]

Hi Ally,

Yes, that will be great, please add the hooks for the outer wrapper classes, thanks!!

[Hiyou]

Hi Ally,

Sorry I didn’t explicitly state my needs correctly. I need to programmatically add CSS Classes to groups / pages (and other non-input elements). In order words, I want to decide at run-time which classes to add, in order to style the elements differently depending on different logic. I know this can be done for input elements by using the quform_field_classes_elementID filter, but this is not implemented for non-input elements. Can this be implemented?

[Hiyou]

Please allow to add Custom CSS Classes to all elements, not just input elements (e.g. Groups, Pages, etc)!

[Hiyou]

Hi Ally,

This is now resolved, it in fact is a permission issue. Although the Settings checks stated that the folder is writable, the previous files itself generated wasn’t writable anymore, hence causing the issue. This is now resolved, thanks.

[Hiyou]

Hi Ally,

I checked the quform/cache in Tweaks & Troubleshooting and its okay (green tick). The css file generated in the quform/cache directory is also working ok (if I change the background color for the ‘group’ element as part of the pre-available admin choice, it shows up in the css correctly).

However, any other css I do in the ‘Add Style’ feature will not work. E.g. if I add the “color: red;” in the group wrapper and also change the background color in the group element, only the background color will show up. Any custom css style I change to any elements doesn’t show up in the form (but it reflects okay in the Admin Ajax preview).

What is wrong?

[Author]

Posts