Any idea what is causing this 404 from Visual Composer?
http://mysitename.com/wp-content/plugins/js_composer/assets/css/vc_lte_ie9.css
It is hitting my 404 log regularly, always with the exact same name, most recently from the msnbot, but also from the googlebot. Also seeing this 404 from website visitors who are not bots.
Is it related to the Visual Composer upgrade I recently did from 4.6.2 to 4.7.1.1?
Thanks
VC might have discontinued support for IE9 or changed that and some caching or other element is still pinging that.
You could likely
a) check the plugin folder to see if that file is there or got renamed
b) do a 301 redirect via htaccess to the renamed file, or to a different CSS file.
Also possible it’s an old file which had a vulnerability and a bot is looking to hack you or check to see if vulnerable.
That could be totally wrong — so tagdiv may have better answer; just food for thought. Looking at the changelog for VC might also provide a clue if the file was retired.
Hi,
I have also checked this on my side and found the same issue, the vc_lte_ie9.css file doesn’t exist but it is requested in the page source – http://screencast.com/t/Qyuv0uAAYUv
We will open a ticket to the plugin support and we hope it will be fixed as soon as possible.
Thanks and sorry for inconvenience!
Hi Alin / Chris,
I just noticed that after the update to 6.6, the 404s for http://website.com/wp-content/plugins/js_composer/assets/css/vc_lte_ie9.min.css are back in a big way. My 404 log is full of 404s for this ie9 css file since the 6.6 update. Any recommendation on how to eliminate this?
Thanks
Hello,
Unfortunately the problem is still present in the current version as it does not come from our theme. It comes from visual composer. It is requesting an non existent file. We opened a support ticked for this error and got no response but they tend to fix errors from reports even if they do not answer them. We will open another ticked on the subject and hopefully it will get fixed in a future version of the plugin.
Thank you!
P.S. As a temporary solution you can add an empty file with that name in the path specified so the 404 error will not show up anymore.
Hi @mtman,
We have opened a ticket to the VC support also when you first reported this.
Bellow you can read the official response:
Hi Ra,
We had already responded in your previous ticket that this will be fixed in the next big release. We are working on 4.9 update which will be out soon.
Thank you,
Thanks!
