Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Frank Goossens

    (@futtta)

    Very weird der-bank-blog, could you copy/paste the exact error-message here?

    Thread Starter Der-Bank-Blog

    (@der-bank-blog)

    It just said (in German) The plugin could not be activated, because it produces a fatal error

    Thread Starter Der-Bank-Blog

    (@der-bank-blog)

    Is it “normal” that there are more than 58,000 files stored under /cache/autoptimize/js ?

    Plugin Author Frank Goossens

    (@futtta)

    re.: the fatal error; absolutely no idea I’m afraid, this is the first report of this occurring, even though the last release is 3 months out and has been downloaded approximately 40.000 times since then. no idea how to debug (yet) that I’m afraid … ??

    re.: cache size, there’s info in the FAQ describing why this happens and how to configure AO to not do that (hint: exclude page- or request-specific inline JS).

    frank

    Thread Starter Der-Bank-Blog

    (@der-bank-blog)

    I will delete all files and try to install it again. Let you know about the result

    Thread Starter Der-Bank-Blog

    (@der-bank-blog)

    After deleting all files and Setting up everything new, it seems to work fine again.

    Not sure, if I get it right with the Caching files. Do I have to mark the box for static?

    Plugin Author Frank Goossens

    (@futtta)

    Great (a relief, really)!

    Regarding static vs dynamic; static is default & better, except it you’re not on apache in which case dynamic optimized files will make sure expiry & compression are handled by PHP instead of by your webserver.

    frank

    Thread Starter Der-Bank-Blog

    (@der-bank-blog)

    Ist my relief as well. I really like your plugin.

    I still am not sure how to prevent from saving many Caching files. I looked through the Q&A but did not get the answer. Maybe you could help me with another hint please

    Plugin Author Frank Goossens

    (@futtta)

    well, if you have 2 similar pages (2 blogposts) compare the HTML, it will very probably have some inline JavaScript which is slightly different. Try to spot those differences and then try to identify a common string in them and add that common string to the comma-seperated “exclude from JS optimization”-field.

    frank

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Fatal error’ is closed to new replies.