Level 75
I always backup data (the mysql database) daily or more often.
1 like
Apr 7, 2024
4
Level 11
All data gone after upgrading to Livewire 3 (from v2)
I do not know if anybody had this, I guess not. I did craft a project using livewire 2 once and over time, I had to upgrade livewire from v2 to v3. I did make all the steps in the upgrade guide and I used (locally) the upgrade command. After that, there was much fiddling around with the smaller errors but I got it running. I did wonder a bit, why my local db was wiped but it was a lot of work and I did not care much about it (though I had done somehing causeing this) and after some hours, the project run with livewire v3.
Then, I made some polishing and it was ready for deployment to the server (forge with deployment steps). I clicked on "deploy", it run through and my project was there asking for a login. Logging in with my credentials did not work and I went to my db tool looking into the (prod) database I my heart stops: all data was gone. The tables are there, the data is gone.
Why? And: I guess noone had this problem, no?
Level 11
@jlrdw This was on my todo list but not done yet. I evolve o do this as basic setup and not after testing phase. Still: The problem is existing and it undermines my trust in laravel things not only a bit.
Level 14
I know it wont' be helpful to your current issue, but I've updated a half-dozen applications to use Livewire 3 in local + production, and never run into anything like this.
One thing to consider (and I might be way off base here), but to me, the issue you're talking about sounds like you might have inadvertently run your tests as part of the upgrade, and not had a separate test database.
1 like
Level 122
@shawnyv Sounds plausible to me. Why would any upgrade mess with the database, let alone Livewire?
1 like
Please or to participate in this conversation.