Anybody else temporarily losing Action capability after deploying?
Hi all, hoping somebody can help me out with this one, as it's a weird one for me.
I'm finding on my production site that after I deploy, I (and my users) aren't able to trigger actions until we reload the page.
Even if I push, then login, the first action I try doesn't do anything. Once I reload, it loads perfectly.
I'm wondering if it's a view caching issue somehow? I've got "@php artisan filament:upgrade", in my post-autoload-dump, and I'm running $FORGE_PHP artisan optimize in my deploy script at the end (just before horizon terminate).
I know I'm probably being stupid and have missed something obvious - hoping somebody here can point me in the right direction!
Thanks!!
I'm finding on my production site that after I deploy, I (and my users) aren't able to trigger actions until we reload the page.
Even if I push, then login, the first action I try doesn't do anything. Once I reload, it loads perfectly.
I'm wondering if it's a view caching issue somehow? I've got "@php artisan filament:upgrade", in my post-autoload-dump, and I'm running $FORGE_PHP artisan optimize in my deploy script at the end (just before horizon terminate).
I know I'm probably being stupid and have missed something obvious - hoping somebody here can point me in the right direction!
Thanks!!
Solution
Upon further investigation, it seems it happens the alpine session variables are re-set. Once they've been deleted, no action modals will show up until a page is loaded twice (then any/all of the action modals work again). Turns out the issue was because I used wire:navigate, and that seemed to interfere with the first loading of actions.
