[KilmanaghParticipant]

Suddenly I am getting 404 errors for all the font-awesome fonts when editing/creating posts (http://site.org/wp-admin/admin.php?post=1178&action=edit, etc)
The URLs it is looking for is /wp-content/themes/x/framework/fonts/font_awesome/font-awesome.woff (TTF, etc)

However, the fonts are now named fontawesome-webfont.woff in that directory.

How do we get that corrected?

I am using WordPress 4.6.1/X-Version: 4.6.2 with CloudFlare
Thank you,

[RupokMember]

Hi there,

Please try resetting your WordPress files and folders permissions. The correct settings can be found at http://www.smashingmagazine.com/2014/05/08/proper-wordpress-filesystem-permissions-ownerships/

Thanks!

[KilmanaghParticipant]

My permissions are fine 🙂

Ill make you a deal. Take a look at /x/framework/css/dist/admin/visual-composer.css

See all the “format(“woff”),url(“../../../fonts/font_awesome/font-awesome.ttf?v=4.5.0”)” etc?

The files in /x/framework/fonts/font_awesome/ are named fontawesome-webfont.ttf and so forth. See the spelling difference between the CSS and the actual file name? There is no font-awesome ‘*’ in the directory it is fontawesome-webfont ‘*’. That is straight from your Zipped File.

That’s a 404 with any permissions on a server 🙂

[RadModerator]

Hi there,

In that case, would you mind providing us with login credentials so we can take a closer look? To do this, you can make a post with the following info:

– Link to your site
– WordPress Admin username / password
– FTP credentials

Don’t forget to select Set as private reply. This ensures your information is only visible to our staff.

And it’s very important to provide the site’s URL that has the issue. We could at least directly access the file’s URL directly. It could be permission, a security, a firewall, and more. Checking it directly is more recommended.

Thanks!

[KilmanaghParticipant]

Have you even looked at your code? I gave you the lines of code in from your ZIP file that I downloaded from here.
Your /x/framework/css/dist/admin/visual-composer.css looks for ../../../fonts/font_awesome/font-awesome

However, its /x/framework/fonts/font_awesome/ are named fontawesome-webfont in your code.

Please take a look at your repository or your Look in your distributed zip file before I give anyone access to anything. I have to go to the customer and get a consent for anyone that is not on the contract for liability issues and PII waivers.

You have it correct in Icon.css in the stacks directory (“../../../../fonts/font_awesome/fontawesome-webfont.woff2?v=4.5.0”) format(“woff2”),url CORRECT!

but in the dist/admin visual-composer.css it is (“../../../fonts/font_awesome/font-awesome.woff?v=4.5.0”) format(“woff”),url INCORRECT!

Again, kindly have a closer look at your code to verify what I have found. I have given you exactly what you need to verify your code in about 2 minutes. This is an excellent theme and I have had excellent service. However, check your code please or forward the information to a developer on your team that knows the code well.

My guess is that when you decided to stop updating Visual Composer, you also deprecated support for people that continue to update and use Visual Composer.

Thank you for your time, please verify your code first, I am actually helping you out.

[FriechModerator]

Hi There,

Thank you for the heads up. Yes, I can confirm visual-composer.css has the wrong path. Let me forward this to our Dev Team for now.

Rest assured that we will continue supporting extensions that is bundled to our x|theme.

Cheers!

[Author]

Posts