@illinoisharley This morning I followed all of the steps in http://rkt.gs/testing I received the error while using the Twenty Ten theme, so it's not a theme level conflict. I then de-activated ALL plugins (including gravity forms). I re-activated gravity forms so that it was the ONLY active plugin. I did this while the Twenty Ten theme was enabled. I still received the javascript exception on tw-sack.js in that environment. Therefore this is not a theme level or plugin level conflict.
I have asked the hosting environment for the RAM available to both PHP and WordPress, I'll post that back here when I hear back from them. I can't see why an out-of-RAM error would occur on a vanilla WordPress site, with no plugins, and the stock Twenty Ten theme. Furthermore, as a javascript developer I have never seen a javascript exception caused by the server running out of RAM. The Javascript files are served to the client properly with no 404 exceptions occurring, and the javascript exception occurs on the client's machine, so I'm not sure how RAM could play a role in this. I'm open to it being the cause, I just don't understand how it could be.
What other ideas do you have that I should look into because I don't believe RAM is the root cause of this javascript exception.
Thanks in advance for your thoughts on this.
Posted 11 years ago on Friday January 4, 2013 |
Permalink