W3TC and Ajaxize getting the dreaded "-1" again.
-
This is for a different site than I originally posted about regarding Ajaxize returning “-1” instead of the Ajaxized content. That problem was fixed by increasing the garbage collection frequency.
Unfortunately I am running into this again on another site but it is only happening with W3 Total Cache and only on Windows machines. The problem occurs even after W3TC is first instantiated or just after the page cache has been cleared so this can’t have anything to do with the garbage collection frequency.Depending on the Windows version, a page refresh fixed it but not always.
I know nothing about crsf tokens so I have no idea if this is related to that or something else. At least on this particular site, W3TC is quite a bit faster than WPSC so I would prefer to use W3TC. The problem does not occur at all with WPSC.
Any ideas?
- The topic ‘W3TC and Ajaxize getting the dreaded "-1" again.’ is closed to new replies.