Query Manager loses variables

Wappler General Bugs
1

Wappler Version : last stable
Operating System : MacOS
Server Model: NodeJS
Database Type: PostgreSQL DO
Hosting Type: custom

Previously, the project used Query Manager on many pages and configured many different variables. But now all the variables on all pages have disappeared - but in the code where they are used they remain.

And so far they seem to work on assignment and reading - but it looks a little scary. Perhaps this is a problem with the display in the interface, but it is not clear how to add new query variables now, since the old ones are not visible.

lost
lost2966×1888 1.07 MB
working
working2954×812 197 KB

2

They also disappeared from the options in the App

app
app2098×1710 1.03 MB

1 Like
3

Variables All the query definitions are stored in dmxAppConnect/config.js under the key that you have specified as app ID.

Do you see anything in this file or is it empty?

When exactly does this happen?

4

@George sorry for joining here but I already had that problem 2 times and I have in mind to pay attention every little bit to my config.js for changes in order to report it so we can solve it…
But it is not easy and it may take time until it happens again, so I’m making copies (backups) of my config.js when I make changes (queries, variables, datastores etc…) just to make sure that I will not loose to many data.

image
image912×107 7.86 KB

5

Well it will be very helpful to find after which action does it happen. Like were you defining new variables or repeat regions that when tried to save the new data, somehow got an error and empty the file.

1 Like
6

dmxAppConnect/config is in the root folder - there doesn’t seem to be anything similar in it, there is another one in the public/dmxAppConnect/config folder - it has several pages - but the rest are missing

7

no, all this has disappeared in many places - even in those that have not been edited for a long time. I noticed this about a week ago

8

So your config.js is empty?

10

not completely empty - there is something in it - but not all pages here exist

dmx.config({
  "ev_ankete": {
    "query": [
      {
        "type": "number",
        "name": "event_id"
      },
      {
        "type": "number",
        "name": "rider_id"
      },
      {
        "type": "number",
        "name": "client_id"
      },
      {
        "type": "boolean",
        "name": "edit"
      }
    ]
  },
  "ev_rider": {
    "query": [
      {
        "type": "number",
        "name": "event_id"
      },
      {
        "type": "number",
        "name": "rider_id"
      },
      {
        "type": "number",
        "name": "client_id"
      },
      {
        "type": "boolean",
        "name": "edit"
      }
    ]
  },
  "ev_ligums": {
    "query": [
      {
        "type": "number",
        "name": "event_id"
      },
      {
        "type": "number",
        "name": "rider_id"
      },
      {
        "type": "number",
        "name": "client_id"
      },
      {
        "type": "boolean",
        "name": "edit"
      }
    ]
  },
  "ev_invoice": {
    "query": [
      {
        "type": "number",
        "name": "invoice_id"
      },
      {
        "type": "boolean",
        "name": "edit"
      }
    ]
  },
  "invoices": {
    "data_view_riders": {
      "meta": [],
      "outputType": "array"
    },
    "tableRepeat1": {
      "meta": null,
      "outputType": "array"
    },
    "query": [
      {
        "type": "number",
        "name": "invoice_index"
      },
      {
        "type": "text",
        "name": "sort"
      },
      {
        "type": "text",
        "name": "order"
      },
      {
        "type": "number",
        "name": "invoice+page"
      },
      {
        "type": "number",
        "name": "client_id"
      },
      {
        "type": "text",
        "name": "type"
      }
    ]
  }
});
11

Well we made some improvements in the last two Wappler updates, so this shouldn’t happen any longer. The problem was probably occurred before that.

Still keep an eye on it, if it happens again now with the latest update let us know.

12

the file above is inside the public/dmxAppConnect folder, but the file from the root /dmxAppConnect contains these parameters - this is probably why they are executed in the code as before. But it’s unclear why the contents of the /public folder are not synchronized with the main project code - I really don’t quite understand its role in the structure

  ],
    "query": [
      {
        "type": "text",
        "name": "sel_fl"
      },
      {
        "type": "text",
        "name": "image"
      },
      {
        "type": "number",
        "name": "room_id"
      }
    ],

this is a piece of this file where they are

13

Hmm there shouldn’t be any other file in your root but just one in the public.

Could you paste the full code of the one in the root? To see what is stored in it and determine where it comes from.

14

the amount of code there exceeds the limit for uploading here - what’s the best way for you to convey it?

15

You can zip the file and attach it here.

16

config.zip (7.4 KB)

@Teodor Is this what you meant?

17

Ran into this problem again on a very simple page

query_man
query_man2842×1802 401 KB

18

So this happens after a Wappler crash?
Can you restart Wappler with logging and recreate the issue, so that we can see what’s the crash reason?

19

I’m not sure that this happened exactly at the moment of the fall, I tried to repeat my actions, but this time nothing happened.

20

Today Wappler crashed again and all parameters in Query Manager loses.

1 Like