Wappler Version :last stable
Operating System :Mac
Server Model: NodeJS
Database Type: PostgreSQL
Hosting Type: custom
A very strange problem - the Calendar is not displayed on the production server, but is perfectly visible on the local one.
All requests with data received are the same and complete in both cases.
I'm at a loss - how can this be and what does it depend on?
Did you do a full publish? Any errors in dev tools?
On local, sometimes the calendar collapses and shows such a strange appearance, but after reloading the data it returns to normal
On the production server it never shows at all and in the console there is this error
Please provide a li k to your production server where we can check this.
Login: Wappler
Psw: wappler
after login refresh page if not view Events->Kalendars
I see LOTS of errors in the console, quite a mess.
I also see you are using quite old app connect version - 1.x something.
Are you sure you haven't mixed some old App Connect files with new ones from version 2?
I always just update the project with the release of updates, so even if something got mixed up, I don’t know how. How can this be cleaned up and brought to the latest version of App Connect?
It doesn't seem to me you updated this project with each update. It's currently on app connect 1 and we released app connect 2 some time ago.
Do a project files update using the resource manager and make sure to upload your files to the server:
I have the Stable channel now and before - I will also check all the updates there and I have no changes in the project files after this
Then you have old files on your server.
I tried switching to Beta and back, published again - but nothing changed. What specific files can be checked for version compliance?
dmxAppConnect.js -
App Connect
Version: 1.14.12
(c) 2023 Wappler.io
@build 2023-03-14 12:22:18
It looks like it's really old - but why isn't it updated by Wappler?
I have a guess - there is a Web Root Folder 'public' - it contains a new version of the files, but in the root folder of the project there are old ones and are not updated. In general, this folder and the root one should be identical - it seems that wappler creates it itself when creating a project
Maybe some folders with components can be deleted from the root directory - and then change the Web root to the root - so that everything new is transferred there? Unless of course this ruins the whole project?
Or should Wappler update all components in the project root directory as well?
I am not sure i understand you.
Stable and beta channels are currently the same, we don't have any extensions in the beta channel.
What do you mean? Where is this public folder and what is the "root folder of the project" you are referring to?
What is the server model you are using?
Is this locally or on the remote server?
How do you publish your project?
This sounds to me like you have something really broken in the project settings.
Well the files in the public folder are the ones used for your app. Not sure how did you end up having the dmxAppConnect folder outside the public folder?
No,I don't know how it happened, there is some kind of correct structure - how can I move/remove unnecessary things? I started another project, but there such a structure was created and dmxAppConnect is inside public
You only need the dmxAppConnect folder that is located in the public folder. This should be the one uploaded to your server.
