DMXzone App Connect Support Product Page
Answered
Will config.js break my App?
Asked 30 Apr 2018 11:00:51
1
has this question
30 Apr 2018 11:00:51 Hans Haverlach posted:
Hi I found out that when build an App connect web app for a certain website, certain settings are written to config.js in the dmxAppConnect folder.I upload my application and all the dmx folders and it works fine.
But I sometime develop other App connect apps for a different website and afterwards I like to use this some of these Apps for the first website.
I copy the App pages and the subfolders from dmxConnect folder to the first website and upload.
But now my question: the first website has a config.js in the dmxAppConnect folder with different content than the config.js file present in the other website(which has many more Apps)
What to do? Is the config.js file an obligated file, or can I jus leave it and not upload it?
Replies
Replied 01 May 2018 06:08:39
01 May 2018 06:08:39 Teodor Kuduschiev replied:
Hello Hans,
The config.js won't break your site. It stores things like query parameters defined on your pages, so they will get lost, when overwritten.
The config.js won't break your site. It stores things like query parameters defined on your pages, so they will get lost, when overwritten.
Replied 01 May 2018 07:43:19
01 May 2018 07:43:19 Hans Haverlach replied:
Thank you for your reply Teodor.
But if I understand correctly, uploading a different config.js file (from my development site) to a production site (which has also other app connect apps, not present in my development site),
will overwrite the existing config.js and thereby the stored query parameters will be lost.
The existing apps on the production site will not find the stored query parameters.
That will cause problems, maybe not break my site, but it will break some functionality.
Isn't it more logical that the query parameters are stored in an App specific config.js, so each App has its own config.js.
If above conclusion is right, than the current setup does not contribute to portability in my App development workflow.
But if I understand correctly, uploading a different config.js file (from my development site) to a production site (which has also other app connect apps, not present in my development site),
will overwrite the existing config.js and thereby the stored query parameters will be lost.
The existing apps on the production site will not find the stored query parameters.
That will cause problems, maybe not break my site, but it will break some functionality.
Isn't it more logical that the query parameters are stored in an App specific config.js, so each App has its own config.js.
If above conclusion is right, than the current setup does not contribute to portability in my App development workflow.
Replied 01 May 2018 08:00:34
01 May 2018 08:00:34 Teodor Kuduschiev replied:
Hans,
the config.js file is only used by DW, not by the sites you create. It won't break the functionality of the sites.
the config.js file is only used by DW, not by the sites you create. It won't break the functionality of the sites.
Replied 01 May 2018 09:15:50
01 May 2018 09:15:50 Hans Haverlach replied:
Alright, now I get it. Thank you!