Call to a member function stdWrapValue() on null about staticfilecache HOT 3 CLOSED

Hello @lochmueller
This seems to do the trick, thank you! Should I only uncheck this for pages that load INT scripts or with all pages altogether? What would be the use case for (un)checking this option? (You can close this issue afterwards)

Best regards

from staticfilecache.

You should always uncheck this option! If there are *_INT objects, the page is not cachable. The checkbox is only for testing. If you want a fully cachable page, do not use *_INT object and fix the plugins/typoscript that use *_INT scripts.

Regards,
Tim

from staticfilecache.

Hey @nwm-dev
Do you saw the notice on the "force static file cache" field in the backend ;-) => "Force the static cache generation (NOTE: This result in undefined states. Do not enable this field for editors, do not use in production and do not report bugs related to this feature!)"

Please do not use the "force static file cache" function.
Does this information help? StaticFileCache cannot control the states of INT script loading... and there is no direct API to handle this.

Regards, Tim

from staticfilecache.