Laravel-Backpack / demo

A working demo of Laravel with all Backpack packages installed.
http://backpackforlaravel.com
Other
329 stars 165 forks source link

JS Components not working in online demo #552

Closed EmanueleCoppola closed 1 year ago

EmanueleCoppola commented 1 year ago

Bug report

JS components not working in demo

What I did:

Visited

What I expected to happen:

See all the JS components working.

What happened:

None of the JS components is working. I also see many 404 in the console, my guess is that basset might be broken.

welcome[bot] commented 1 year ago

Hello there! Thanks for opening your first issue on this repo!

Just a heads-up: Here at Backpack we use Github Issues only for tracking bugs. Talk about new features is also acceptable. This helps a lot in keeping our focus on improving Backpack. If you issue is not a bug/feature, please help us out by closing the issue yourself and posting in the appropriate medium (see below). If you're not sure where it fits, it's ok, a community member will probably reply to help you with that.

Backpack communication mediums:

Please keep in mind Backpack offers no official / paid support. Whatever help you receive here, on Gitter, Slack or Stackoverflow is thanks to our awesome awesome community members, who give up some of their time to help their peers. If you want to join our community, just start pitching in. We take pride in being a welcoming bunch.

Thank you!

-- Justin Case The Backpack Robot

tabacitu commented 1 year ago

Thanks for the report @EmanueleCoppola ! We'll investigate and fix ASAP 🙏 Probably today.

tabacitu commented 1 year ago

Possible causes:

1) Cloudflare's Rocket Loader 2) Our "database refresh" script 3) Maybe some hits being made WHILE we are deploying? So while php artisan basset:fresh is being run, people WILL access direct URLs, so Basset will internalize some JS/CSS twice, and maybe that causes some conflicts? We can eliminate this by running php artisan down and php artisan up in our deploy and refresh scripts. But then we need to create a clear Error 500 page so people know what is happening.

tabacitu commented 1 year ago

@EmanueleCoppola I believe we've fixed it. I'm not 100% but I am 99% sure so I'll close this 😀 You can see WHY this has happened in https://github.com/Laravel-Backpack/demo/pull/553#issuecomment-1648337127

Thanks again for opening this up!

tabacitu commented 1 year ago

@karandatwani92 feel free to check our demo once in a while, and tell me if we're still having problems. But we should be good to go now.

karandatwani92 commented 1 year ago

@tabacitu It's working perfectly