Tagged: 404
-
AuthorPosts
-
March 27, 2014 at 9:58 am #243741
Tried this solution https://kriesi.at/support/topic/removing-entypo-font-version-string/
In both the parent and the child theme, but nothing seems to help, still 404 error.
Any fix ror thisMarch 28, 2014 at 9:01 am #244249Anybody?????
March 28, 2014 at 9:52 am #244268Hi!
Did you check if the file exists on your server? Maybe try to install the theme with ftp: https://vimeo.com/channels/aviathemes/67209750
Cheers!
PeterMarch 28, 2014 at 10:31 am #244271The file exists
like entypo-fontello.woff without the ?=v2′ like it suppose to.
Double checked this.
The fonts are working, I se the icons at the website, just the WOFF is 404.
Any suggestions?March 30, 2014 at 9:05 am #244996Not solved yet…
March 30, 2014 at 9:17 am #245004Hi!
Can you post a link to your website?
Regards,
JosueMarch 30, 2014 at 9:45 am #245023This reply has been marked as private.March 30, 2014 at 9:52 am #245026Hi!
As a quick FYI our queue goes by oldest posts to newest. When you self bump or ask about a topic it actually pushes the topic to the end of our queue and its more likely we will miss it rather than see it.
As for the issue if the file is in fact located in wp-content/themes/vsd/config-templatebuilder/avia-template-builder/assets/fonts/entypo-fontello.woff make sure that its set to be readable by the server. Eg, chmod 776.
Regards,
DevinMarch 30, 2014 at 1:30 pm #245098HI,
Gave it 776 and even 777, still 404March 30, 2014 at 9:33 pm #245201Hey!
Try re-installing a fresh version of the theme.
Regards,
JosueMarch 31, 2014 at 7:30 am #245300Tried this too.
Before rote to the supportMarch 31, 2014 at 8:05 am #245315The only other option would be to talk to your hosting provider and explain the issue. If the file is there on the server and the theme is pointing to it but the server returns a 404 there must be something else going on server side.
March 31, 2014 at 8:08 am #245319I don’t know what to tell them.
The rest 99.99% of the website is ok, this is the only issue, the icons are show up at the frontend.
How they suppose to know what to fix?
Only the .woff?=v2 the rest of extensions for the font are ok’ too.- This reply was modified 10 years, 7 months ago by vadi4ek.
March 31, 2014 at 4:57 pm #245515Hi!
Thank you for the info.
I’m not sure why the filter is not working. I also tested it on my end but the appended version doesn’t seem to be removed. If you don’t mind, you can remove the actual code on config-templatebuilder > avia-template-builder > php > template-builder.class.php. Find this code on line 45:
'append' => '?v=2',
Regards,
IsmaelJune 25, 2014 at 1:26 am #283356Solution, if what I think is happening, is actually happening.
If so, then the issue is with “Mime Type”. Woff is not a recognised just yet, so you have to add it to the .htaccess file or web.config file for Windows.
http://stackoverflow.com/questions/3594823/mime-type-for-woff-fonts
June 25, 2014 at 1:29 am #283360Thanks for sharing your solution Paul!
Best regards,
Josue -
AuthorPosts
- You must be logged in to reply to this topic.