My website was running fine for months, but all the sudden receiving 500 error on the dynamic pages. I tried to create a new collection and new dynamic page without any custom code, able to preview the page, but hitting 500 error when published.
I also testing with a new collection and a default dynamic page generated automated.
Database collection name âtest-dataâ and dynamic page âTest-dataâ, oakary.com/test-data/jerry@oakary.com
Roll back and restoration from the backups does not work
I discovered the error 500 issue on 11/27/18, but the pages have been running fine for the past few months. So I tried to roll back to the backup all the way to 11/26⌠11/14, but still getting the error.
I also duplicated the site and publish a test website, and that also does not work.
Getting odd dataset error
I experienced the error, "DatasetError: Operation (onReady) not allowed on an unconfigured datasetâ after the page went down for the 500 error. All the default auto-generated dataset no longer work and not working in preview neither, so I have to replace them manual with new dataset, which it works fine afterward the replacement. see page oakary.com/candidate/{email}. The page is loading the data and UI correctly in Preview, but still having 500 error when published.
New collection without custom code also not working
A brand new data collection and created a new dynamic page with dynamic dataset linked to that new collection, it still shows the following error with the auto generated and default dataset. "DatasetError: Operation (onReady) not allowed on an unconfigured datasetâ
So I tried to add a dataset manually, then the error went away, but the page still having 500 error.
This is done without any custom coding.
You can check the new collection âtest-dataâ and new page âTest-data (Email)â ( https://oakary.com/test-data/jerry@oakary.com in live site).
Existing ones only work in Preview
I examined the code and thereâs no error and itâs able to run in Preview, only problem is the it hit error 500 when view as a live site. and the code is not new, it has been working fine for months, only few days ago (11/27) it went down by itself without any code modification. And not just this page, pages that tied to database (any database, thereâre few) all have the same error. No code was modified and the same situation, pages have been running for months fine then went down all the sudden.
Please see screenshots attached (page oakary.com/candidate/jerry@oakary.c om)
Hi Jerry,
I recommend trying to change the field to ID instead of an email. In order to use the dynamic page feature correctly, the field should be unique otherwise it wonât work properly. The ID field is unique, therefore I think that it should help.
The field email actually works fine, since I have been using it to get the profile page in the past few months until 11/27. I used email to retrieve the page, because ID is random I wonât able to know the ID for particular candidate. Plus, I think Wix handles the none-unique field by requesting the most recent data, so no trouble there.
I think the main issue is that even new collection and dynamic page without custom code also doesnât work. Rolling back also doesnât help. So Iâm suspecting itâs the backend logic of handling dataset somehow corrupted for this particular case. Restore doesnât restore the database, as a result, restoring wonât fix the 500 error, which also means that the code itself is not the issue, since I already rolled it all the way back to the data that was working fine, like 11/14 before 11/27, when it first broke.
You can see the test-data collection and dynamic page also have trouble working on live site (but works fine in Preview).
Please let me know what you think if you have a chance to test out the test-data collection, because that one is a simple version of the example of the issue.
hereâs another thing I tried today. You can find a new website âbasecampâ, I copy the same database to that project to test things out and works fine. So seems like itâs really the oakary website has backend server issue. Perhaps database get corrupted, so itâs able to write, but have trouble reading it.
Could you investigate for as a database bug for me? thanks!
It looks like an issue with the code in the routers.js backend file.
If you comment out the code in this file, I believe that you will be able to use dynamic pages in published sites.
Try to start solve it from this file.
I have the same issue. The site worked fine for months. Now throwing up error 500, especially if swtiching rapidly through dynamic pages. Only front end code is running. What can I try?