Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
  • #1245503


    Using the Advanced Styling tab, I specified font weight 600 for the body and p styling tags. For some reason, I don’t see this applied. I have verified with WhatFont and it show the default 400 weight. When I manually switch it to 600 with the Chrome developer tool, I do see the difference.

    ccleansed & forced a Ctrl-refresh in Chrome to clean up the client side and next to that also forced a W3 Total Cache all cash cleanse… doesn’t make a difference.

    Any ideas?

    Thank you.

    • This topic was modified 1 year, 4 months ago by  DimitriMTM.

    Hey DimitriMTM,

    Please post us your login credentials (in the “private data” field), so we can take a look at your backend.

    1. Install and activate ” Temporary Login Without Password “.
    2. Go to ” Users > Temporary Logins ” on the left-side menu.
    3. Click ” Create New “.
    4. Add the email address for the account ( you can use (Email address hidden if logged out) ), as well as the ” Role ” making that the highest possible and the expiry about four days
      ( to be sure that we have enough time to debug ).
    5. Click ” Submit “.
    6. You’ll now have a temporary account. Please provide us here in the private section the URL, so we can login and help you out.

    When your issue is fixed, you can always remove the plugin!
    If you prefer to not use the plugin, you can manually create an admin user and post the login credentials in the “private data” field.

    Best regards,

    This reply has been marked as private.

    Hi Dimitri,

    I have tested it and purged the cache as well but it doesn’t seem to work (although it says in the backend it was cleared).
    I tried to disable CSS minification and page caching and purged cache and was expecting it to fetch css files from Enfold and not minified but instead it is still fetching from the plugin’s cache.
    You can test this via web inspector or via viewing the page source.

    Best regards,


    Hi Nikko,

    So do you suspect that this is a caching issue?
    Perhaps the W3 cache plugin isn’t properly purging the cache and I need to manually cleanse Redis & Varnish on the server?



    Hi Dimitri,

    Yes, if you can also temporarily disable the caching as well, it would be better.

    Best regards,


    BTW the W3TCache plugin doesn’t change the rest of your htaccess. The reason why I am saying is that in the htaccess, I have manually specified some minification settings etc. So it makes sense that enabling/disabling this from within Enfold or W3TC won’t make a difference. Anyway, I manually purged Redis & Varnish but this doesn’t seem to make a difference.

    Can’t we specify something in the Quick CSS settings to verify that this pushed through (or not)?
    When I update a page, these changes are visible. I.e. on the homepage, I updated a button and the change is displayed correctly.



    Hi Nikko,

    Adding .avia_textblock { font-weight:600 !important; } to custom.css fixed the issue so this shows that it has nothing todo with caching.

    BTW this works, quiet logical, for my textblock elements… But it doesn’t for the other elements. Where can I find a list of the available txt related CSS elements?

    When will other elements be added to the advanced styling list?
    It mentions that this is still beta functionality but any clue why the advanced styling doesn’t work?

    Thank you,


    Hi Dimitri,

    I have checked it again and I found that these are generated in line 6077-6078:

    #top .all_colors p{font-weight: 600;}

    However if you inspect the styles being applied to the paragraph or the body this doesn’t appear.
    My only guess is with CSS merging, these codes aren’t being read.

    Best regards,

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.