You should be able to bypass the forum page through WP super cache, it might fix the issue for you
Thanks – but been doing that for the past 5 years or so.
This problem surfaced only a few weeks ago – may as long ago as 2 months. No idea what changed at that point. Might purge & refresh the CDN as a precaution.
It’s the CDN. Disabling CDN support in WP Super Cache resolved the problem.
I have purged it, so I hope that it remains resolved once the purge and refresh has propagated to all the data centres.
I wasn’t aware that wp-cache included any buttons for the editor. Bit of a surprise.
If this IS the issue then the problem might just be that many plugin authors make the false assumption that the tinyMCE editor can ONLY be used by the WP Admin whereas for quite some time now the WP team have exposed the editor to enable it’s use anywhere – which is what we do with Simple:Press.
If this is the case then they often run support code for their editor additions but do NOT run it on the front end – or run part of it more like. This can often be changed with a small edit to the third party plugin code but that really does depend on how it is constructed..
Resolved.
Advice from the CDN support desk:
Known issue: Firefox not loading cross domain name fonts
You need to add the Access-Control-Allow-Origin header via your .htaccess file:
<FilesMatch “.(ttf|otf|eot|woff)$”>
<IfModule mod_headers.c>
Header set Access-Control-Allow-Origin “*”
</IfModule>
</FilesMatch>
