Black Screen Issue: Please update your theme to ensure WordPress 5.6 compatibility. Dentalia 2.1 and Recycle 2.1 are now available on ThemeForest. 

Okay
  Public Ticket #2916453
Dentalia - Semrush CSS issue SOW Widgets
Closed

Comments

  • nymphbyte started the conversation

    Hello!


    I am getting issues in SEMRush and in the inspector related to CSS created by siteorigin widget plugin. Seems the CSS is dynamically appearing in wp-content/uploads/siteorigin-widgets folder and it is also removed. Css filex have sufixes

    SEMRush errors: issues with broken internal JavaScript and CSS files

    /wp-content/uploads/siteorigin-widgets/sow-image-default-d6014b76747a-15554.css?ver=5.7.2


    Inspector errors:

    Refused to apply style from '/wp-content/uploads/siteorigin-widgets/sow-button-flat-7ed72b907790-22024.css?ver=5.7.2' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.

  •  531
    OrionThemes replied

    Hi,

    Do you use any caching/minification/optimisation plugins? If you deactivate them, does the issue dissapear?
    It seems strange to me, that the css would load from the uploads folder...

    Can you share a link to the site, where this appears? 

    Kind regards,

    Andrej

  •   nymphbyte replied privately
  •  531
    OrionThemes replied

    Hi,

    I can see the uploads css files in the sources. There isn't nothing suspicious about them. They can be opened manually in the browser: https://www.dr-mostarac.hr/wp-content/uploads/siteorigin-widgets/sow-image-default-d6014b76747a-1000.css?ver=5.8.2 I guess this is normal (sorry, I didn't know about how SO widget generates their CSS.). I don't see any errors connected with this CSS files in the web console. 
    Buttons also seem to work. The CSS is not blocked in my browser (Chrome). 

    Here are couple of more ideas how to resolve the issue:
    1. I noticed you have WordFence installed. It also could be a potential source of the issues. WordFence should always run in the learning mode first, so it learns what to block and what not to block. 

    2. You can also check if some plugin added anything into the .htaccess file, which would prevent to load urls like the css file above. For example, if you find something like this, remove it:

    <IfModule mod_headers.c>
    	Header set X-Content-Type-Options nosniff
    </IfModule>

    In such case the server will only serve file.css, but will not allow file.css?ver=5.8.2

    Kind regards,

    Andrej