Wappler is not picking the correct db when switching between development and production

[JoakimAsk]

Wappler Version : 7.7.6
Operating System : Mac OS Tahoe 26.3.1
Server Model: NodeJS
Database Type: Docker DB MariaDB
Hosting Type: Docker

Expected behavior

What do you think should happen?

Wappler should make the correct DB choice when switching between development and production.

Actual behavior

What actually happens?

When publishing to production the development DB is still active and published.

How to reproduce

• Detail a step by step guide to reproduce the issue
• A screenshot or short video indicating the problem
• A copy of your code would help. Include: JS, HTML.
• Test your steps on a clean page to see if you still have an issue

I have only created one DB connection called db.

I then have 2 servers specified, development and production. When I'm developing I'm using the development server. And when I press the publish button and select the production server it seems to still publish with the development servers DB connection.

Probably the same error as this:

Env Variables and DB Connection Details are not retained for each target correctly

Hello, NodeJS, MacOS, Docker, MySQL, v7.7.3 (Project), v7.7.6 (Wappler Core) This is the first time I have come across this issue with Environment Variables (config.json) and DB Connection details (db.json). When I update values for a target in the Environment variables and DB Connection details under Global > DB Connetions, the values are correctly saved for that target. But, these changes seem to overwrite the values in config.json and/or db.json for other targets. I’m updating the values …

[JoakimAsk]

@George

So this didn’t get fixed in todays update.

Wappler is not usable right now.

[daves88]

Agreed .. not sure why we had to wait a full week for another update where this hasn’t been fixed.. very disappointing and also worrying that other parts of the system may be effected by this

[George]

We haven’t had any changes for months in this area, so this is not a recent problem.

And we have to clear what exactly is the problem during editing or switch as we can’t reproduce it.

[JoakimAsk]

Is there any way we can assist you in finding what’s wrong?

[mimuk]

I have the issue too.
/opt/node_app/app/modules/connections/db.json

• external access should use XX.XX.X.XX:9910
• internal Docker app access should use wappler-compose-xxxxx:3306

But my Production target is still publishing the external values.

[guptast]

This bug has really put a stop to my work on the projects, especially those that need to be re-deployed with any code updates.

[Hyperbytes]

I have had this happen to me but i have always thought the cause was different.

I have always suspected that if you open connectipn settings and then change target while they are open then saving saves the settings on screen to the selected target, hence overwriting incorrectly.

I aways close all settings screens before switching target and also refresh the connections panel.

May not be the cause but thought it worth a mention.

[Teodor]

Hello, we found the problem.
If you are in a hurry to get the fix, use the following file:
file.zip (3.7 KB)

First fully quit Wappler.

For Windows:
Extract and replace the existing file in

C:\Users\YOUR_USER_NAME\AppData\Local\Wappler\resources\app\Shared\DMXzone\dmxAppCreator\UI\lib

For Mac:
Go to the Applications in finder, right click on Wappler and then Show Contents

There you can navigate to Contents/Resources/app/Shared/DMXzone/dmxAppCreator/UI/lib
extract and replace the existing file.

Otherwise it will be included in the next update.

[JoakimAsk]

@Teodor On next thursday release?

[Teodor]

Yes

[scott]

Thanks @Teodor , that fixed the issue for me!

[Teodor]

Fixed in Wappler 7.7.8