Hi,
yes, TablePress uses a font for the sorting and pagination icons (see http://tablepress.org/release-announcement-tablepress-0-9-rc/ for some info about this).
Regarding your issue, please see this topic, where the same problem is discussed:
http://ww.wp.xz.cn/support/topic/error-404-435
Regards,
Tobias
OK, many thanks on both counts.
I’ll see if Better WP Minify have any solution …. but I think I’m dumping that plugin anyway because the minified content doesn’t get sent to browser gzipped, not the way I’m doing gzipping (through mod_pagespeed), so its no use anyway.
Thanks for your quick response as always.
I’m Not running better WP Minify any more, but there are still issues with the eot file.
It refuses to gzip cache, or be browser cached, whilst every other resource on the site (graphics, css, js) is being cached by both methods
Does the “?” on the end make any difference? Why is it there?
http://www.thaidomains.com/wp-content/plugins/tablepress/css/tablepress.eot?
Hi,
yes, if you are using mod_pagespeed, you shouldn’t really needed Better WP Minify, as that functionality can be done by mod_pagespeed, from what I know.
That .eot file is the font file that gets used by Internet Explorer (all other browsers use the WOFF format, which is included via the data: URL).
I’m not sure if gzipping it makes sense, or if it is compressed already.
About the browser caching: Are you sure that it is not cached? Is the .eot file format in those for that your server sends the corresponding caching HTTP headers?
The ? could make a difference, but I don’t have experience with that. All I know is it seems to be highly recommended to make the different version of IE handle the file properly (see http://stackoverflow.com/questions/8050640/how-does-iefix-solve-web-fonts-loading-in-ie6-ie8 ). It is taken from the recommended web font inclusion CSS at https://github.com/FortAwesome/Font-Awesome/blob/master/css/font-awesome.css
Regards,
Tobias
