ReCache - Speed up your forum

Kyrne

wloot can you disable recache and see if the error persists?

wloot

Kyrne I just disabled "enable cache" from recache, the error gone.

Kyrne

wloot can you clear your recache and see if the error persists?

wloot

Kyrne I had tried to do php flarum recache:clear and php flarum cache:clear at same time, sadly no luck..

Kyrne

danielunited pkernstock wloot

I unfortunately, wasn't able to reproduce any of these issues. Luckily I had a pretty good idea what was causing them so I believe all these issues should be fixed. If they still occur, let me know.

2.0.8

Fix CSRF token/Session issues (logout issue and blatant CSRF Token mismatch error)
Add support for Transliterated discussion URLs.

Give Extiverse about an hour to pull the update. Clear the recache after the update completes.

danielunited

For some reason users can't log out of my community after pressing 'Log Out'.

wloot

Kyrne Just amazing! Both of issues are solved. Thank you.

danielunited

Kyrne Awesome! Just leaving a few more bug reports:
Users have started reporting seeing the "Oops! Something went wrong.." message.
Tried restarting the server, I'll see if it solves itself.

Kyrne

danielunited might want to install sentry to see what the error is.

Kyrne

2.0.9

Another fix for discussion URLs
Add support for @askvortsov's PWA Extension

pkernstock

Kyrne Add support for @askvortsov's PWA Extension

As I've reported a few months ago, there's still an incompatibility or slight issue together with the PWA extension, causing thousands of PHP NOTICEs in days being reported to Sentry and logged on disk.

PWA is using and recache triggering notices on following paths:

/sw
/webmanifest
/offline

Edit: Apologies, (for some reasons( I completely forgot to add the actual PHP NOTICE for your convenience:

ErrorException: Undefined offset: 0
#43 /vendor/reflar/recache/src/Replacers/Data.php(66): FoF\Sentry\SentryServiceProvider::handleError
#42 /vendor/reflar/recache/src/Replacers/Data.php(66): Reflar\ReCache\Replacers\Data::replaceInCachedResponse
#41 /vendor/reflar/recache/src/Middlewares/CacheResponse.php(65): Reflar\ReCache\Middlewares\CacheResponse::process

danielunited

The extension has been giving me some errors, so I tried to disable it and encountered a fatal error. What do I do now?

Kyrne

danielunited hey man, contact me on discord. Discord is going to be the only way I provide support for my premium extensions.

wloot

just out of curiosity: I have never seen the "recache:1" header on my website("recache:0" header just gone after the first refresh), which is normal?

Kyrne

wloot please contact me on discord for help!

Kyrne

Just a quick heads up, I accidentally removed the "ReCached: 1" header from the current version (since 2.0.8)

The "ReCached: 0" header is still in place. So if you see no ReCached header it's working, if you see the 0 header, it's not working.

I'll fix this soon.

[deleted]

@Kyrne does recache support the most recent version of fof/nightmode ? Periodically, my session flips between night and day mode but the problem isn't evident with recache disabled.

Kyrne

[deleted] it doesn't. I'll add a cache catch for it.

[deleted]

Kyrne thanks

Kyrne

While I won't be able to update this extension for just a bit because of school. It should still work on beta 14 with one caveat. Before updating to beta 14 turn off Lazy image Loading. It should then work just fine.

MikeJones

Kyrne thanks for the heads up. I will probably be waiting a bit to update than.

Hopefully it won't be too long!

cmwetherell

Kyrne

If I am installing this extension fresh onto Beta 14, will it break, or will I be able to disable lazy image loading somehow?

« Previous Page Next Page »