Deploy - DATABASE LOCAL X REMOTE

The file was empty. I tried filling it with the same information as the development version, but the problem persists. I installed Wappler on a Linux Mint distribution and it worked fine, indicating that the problem may be related to Windows 10.

Yup, if there's no <database_connection_name>.json fiel or data, goes without saying that its corrupted. You could follow Apple's advice meanwhile and reinstall wappler, there's a guide within forum of how to completely reinstall wappler, or if you're using Mysql or MariaDB, you can wait for the next update! Also, try creating new connection under globals, that should create new connection file!

1 Like

Thanks for the suggestions, but I've already performed a clean install of Wappler on Windows, removing the AppData\Roaming\wappler folders. I've also tried creating global connections, but to no avail. Interestingly, it worked fine on Linux Mint. I think I'll try reinstalling Windows to see if that resolves the issue.

Don't forget AppData\Local\Wappler
That's where Wappler is installed..

1 Like

Yes I deleted it in that folder too! :wink:

Linux and Wappler are an awesome combination!

2 Likes

@Teodor

Hahahahaha, proper OS! Not none of this sit in an expensive coffee shop, 'can I have Soy milk please', with a beard business!

:stuck_out_tongue:

1 Like

Is coconut milk ok?

2 Likes

How about you install an older version of Wappler?

1 Like

Absolutely the right way to go!

George has already said this will be resolved in the next Beta update. It is NOT Windows, read what George said...

Just be patient and as Apple says just use a non Beta version for now (your 'students' really should not be using the Beta at all, in my honest opinion).

1 Like

The problem here, is that he's using stable 6.8.0, so maybe something is corrupted from that version :thinking:

1 Like

Or he could've clicked the update extension nag in the top right corner without realizing :thinking:

Yep my bad I missed that... Onward to my next mistaken observation!

1 Like

True, but isn't that only for assets? Maybe trying the assets updater to stable worth the try? :thinking:

Or maybe try beta? The world is very confusing

1 Like

It might include internal Wappler files (what they call "inline updates"), that's why it breaks sometimes

2 Likes

I've done so much testing, no updating the wappler, updating, beta version, etc.... I did a lot of tests, what made it work again for now was to have installed the wappler on a Linux distro. But as Geroge said, let's wait for the next beta version and see if it solves it!

1 Like

Stick with Linux! I've not used Mint but am an avid Ubuntu/Debian User. The whole experience on Linux is second to none. Windows is just terrible and even more so in its most recent iterations.

Still am happy you have a resolution for now so at least you can continue.

2 Likes

I'll stick with Linux! I need to have experiences with Windows to help students solve problems like this! The vast majority still use Windows and convincing them to migrate is another story! Thank you all very much!

1 Like

This should be fixed in Wappler 7 beta 14

1 Like