Support Forum
w3tc? have you excluded the forum page from ALL cache types active???? you cannot cache the forum page...
you have tons of jquery errors... they just moved to other files now...
on forum - options - global settings, try turning off the combines scripts cache...
Visit Cruise Talk Central and Mr Papa's World
what worked? turning off w3tc or combines js? no, dont see any errors now.. does still look like you are serving cached pages...
so its working now?
Visit Cruise Talk Central and Mr Papa's World
I disabled combined and caching of css and js scripts.
I have not looked into the caching of the forum yet.
I will check that out today and make sure w3 total cache is not caching the forum.
But yes, by disabling those options above the post, edit post and start topic buttons are working and the editor seems to be working just fine now.
I am now having the same problem as Seth - unable to add topics, replies or edit posts. I tried disabling "combining and caching of forum script (JS) files" and resetting the combined script cache, but the problem remains.
I am running WordPress 3.6 and SimplePress 5.3. I recently updated all installed SimplePress plugins as well as several other plugins. I'm not sure when the problem first appeared. I was notified of it by one of our members.
What else should I check?
http://crescentcitycyclists.org/
The only thing that looks worrisome that I can see is that your page is throwing a couple of script errors one of which may be stopping other jQuery calls from working as they should - which would explain the behaviour. I am not 100% on this but it is all I can see. And errors like these can cause so many problems...
The first - a TypeError is being thrown by your theme - Graphene - in their own bundled script so I have no idea what it is doing. Was there an update to your theme as well? The second error is actually in the WP stats code so I doubt that is the real probpem and might be an effect of the first error.
YELLOW
SWORDFISH
|
I searched the Graphene support forum and found that they were aware of a glitch in the latest update (1.9.1) which was causing the JavaScript error. They had a downloadable replacement graphene.js file as temporary patch until they release the next update. I installed that and all is well again!
Thanks again for your quick response and assistance in debugging this issue. I really appreciate it.
1 Guest(s)