Forum Replies Created
-
Posts
-
Hi Nikko,
I now tested disabling the CSS merge and the result is a different CSS behavior (similar to the forcefully enqueueing custom styles at the end of the loading sequence after the merged file). It does not solve the issue with the “!important” statements but some styles seem to change. So it seems like merging does affect the CSS styling which it should not do i guess.
Best regards
MichaelHi Nikko,
yes of course I can always add weight/specificity to my CSS but it would be more convenient if I could just target classes and overwrite as you would expect. I did some research in the forums and found these two things:
new-minify-merging-for-css-and-js-avia-merged-styles-problem
Here is another user experiencing the same problems and you also point him towards higher CSS weight.
But this here seem to lead more in the direction of a solution I am looking for:
add-style-css-from-child-to-merge-files
The code provided to disable the merge however does not seem to work anymore in Enfold 4.4.1. I also tested the de-enqueue and re-enqueues approach (which indeed makes the child theme styles CSS load last in the sequence) but this then creates other CSS problems with some missing styles (which I have not tried fixing yet) – maybe this is what you have been pointing towards in the first linked post (see above). So I do not have the solution yet but I feel this leads in the right direction.
Just wanted to post the research, if you have any thoughts or suggestions, I would be thankful.Best regards
MichaelHi Victoria,
thanks for your reply but this is not the problem. My styles do not get merged in that file but get overwritten by it like it seems. I just think it would be nice if the custom styles in a child theme would always take effect which they would if they would be last in the loading sequence. If you look around in the forums here a lot of the CSS solutions heavily rely on “!important” statements which I (with some necessary exceptions) see as bad practice.
What would be the effect if I disable merging and where can I do that. Would not the same effect (overwrite) take place once I enable the merge again?Thank you and best regards
MichaelHi Rikard,
unfortunately this does not further change the CSS-files loading sequence. The last file that gets loaded is still this:
…../wp-content/uploads/dynamic_avia/avia-merged-styles-501f16d17bc2b13f38ded347de9cb817.css
The name implies its a merged CSS-file but my custom styles are not in it. Might this be the problem?Best regards
MichaelHi Mike,
thanks for the explanation. I guess in more complex tables that is useful. Since you can select if the rows/columns should be standard/description/etc. maybe it would be an idea to fine tune the mobile display. I guess a setup with two columns where the first is description and the second standard for information like contact data, etc might be a quite regular use-case where it would be better to not add via “:before”. But this can be closed unless the solution should stay around for others with a similar problem. Thanks for your quick help!
Best regards,
MichaHi Mike,
perfect that did the job. Thanks for your help!
I think this CSS style should be changed in an Enfold update. (Or made optional if there is a scenario where that behaviour would be desired).Best regards,
MichaHi Victoria,
thank you this fixes the first header section but “Ansprechpartner*innen” (from the first <th>) still gets included in every <td> element. (see link above). It seems to happen via a ::before CSS rule. Not sure why this would be desired.
Best regards,
Micha
