Nice to see all the changes to the Wix/Corvid UI and system.
However, I have two deal breakers:
(1) Today, my main site is about 4x as slow as it used to be until last night.
(2) In addition, I cannot clear this database message:
Publishing the site does * NOT * clear the message and the new collection fails with my existing code.
@yisrael-wix
Stuck - Need a fix, please.
This workaround may help some … if you are not using DATE type entries in your collection.
If you painstakingly create each field in the collection, then you can publish the site, as instructed, and the new fields are accepted - except for DATE fields.
DATE fields keep their exclamation mark and remain undefined field types.
Hey storrrm, how are you doing?
The “publish your site” problem sounds weird. You say that you’ve fixed it (work around). Is this something reproducible? I’d like to report this to QA, but they’re gonna need a problem to investigate.
Thanks
Yisrael, hanging in there while I get pranked daily … rolling with the punches.
It’s hardly a “fix” nor much of a workaround - few collections and groups of collections (referenced) can do without a DATE field.
They can look at the last two collections added:
“… 2020-03-01” Imported csv, published, but none of the fields take.
“… 2020-03-02” Manually created the fields, published, and they all took except the DATE field (dob).
Sorry, I don’t keep bookmarks of user’s websites (too many to keep track of). Post the link again, with relevant pages and collections, and let me know where the problem is. I’ll see what I can do.
Definitely a bizarre issue. I sent this on to QA for evaluation. We’ll keep you informed.
This is [recent] currently existing issue. Stay tuned and Don’t touch that dial.
Still holding on to that dial.
Any updates?
I can’t believe nobody else is encountering this bug.
I understand that this issue has recently been resolved. Please try again and let me know if it works for you. Thanks.
Thanks for the attention to this problem.
I observe progress, but it’s still buggy.
Did not fix the current collections with that error (I’ll delete those).
Created a new collection by importing a CSV:
The LIVE part works! (Which is what matters to me)
The SANDBOX part still has the same error.
OK, that’s what the devs told me - that a current problematic collection will still be a problem. It’s strange that the Sandbox still has an error. What happens after you publish? Does the Sandbox still have the problem?
Created a new collection by importing a CSV and published the site
(ALL new fields have the error message until you publish):
Q1: Do you not have the same issue yourself?
Q2: The speed is still unacceptably slow (maybe 3x slower than it was before this update). Anything that can be done on that front?
Sorry, I had only 5 minutes to look at it when I wrote the above reply.
After looking at it further:
Created a new collection by importing a CSV and published the site (ALL new fields have the error message until you publish):
I tried this and saw some changes:
I painstakingly created each field in a new collection, then published the site, as instructed, and the new fields are all accepted, including DATE fields . Then I synced the collection to LIVE (no data, just the fields). Published.
Now I had both SANDBOX and LIVE with error free fields (all of them, including DATE fields) - but no data yet.
After importing a CSV database to the LIVE section … the DATE field error returned.
This happens on import to LIVE or SANDBOX.
This corruption means I have been unable to import a database from a CSV and get it working with my existing code, or any code, for 5 days now.
I need to load a new database for April in a few days or my Corvid site becomes unusable.
I’m passing this on to the devs for clarification. Thanks
I was looking at your site again… Instead of creating a new database each month, why not just use one database with an additional field (or fields) that indicates the criteria of current data (month, year, whatever). Old data would be ignored based on the appropriate query/filter using these criteria.
Creating a new collection each month(?) just seems to be sort of high maintenance. No need to adjust collection names, change queries to access different collection, and so on.
Umm - I realize that I probably don’t know enough about your project, it’s just an observation based on my own experience with designing database schemas.
One of the devs got back to me and said that the flow works fine for him:
created a new collection in sandbox
added some fields of type number, datetime, reference
added some date
exported it
created new collection in sandbox
imported same CSV I got previously
everything works as expected
I can’t spot the difference between what you are doing and what he’s doing.
Well, I got the devs involved…
This is the sample flow they suggest:
Created collection via auto cms opened from editor
Publish the site (to create the collection in live)
Import csv file in sandbox, the fields defined via import panel
Publish the site (to push created fields from sandbox to live)
Sync Sandbox to Live for getting data in Live
And they’ve got a request …
For reproducing the issue they need detailed info and if possible the csv file or an example of the data. Without these details, the investigation will take too much time.
Yisrael - thanks again for your assistance.
I followed the second checklist:
This is the sample flow they suggest:
Created collection via auto cms opened from editor
Publish the site (to create the collection in live)
Import csv file in sandbox, the fields defined via import panel
Publish the site (to push created fields from sandbox to live)
Sync Sandbox to Live for getting data in Live
Results:
(Exclamation mark tells you to publish)
2. Publish the site (to create the collection in live)
3. Import csv file in sandbox, the fields defined via import panel
So - the DATE field is now being created and initialized correctly for the collection - but the imported date data is not accepted if it is in a daylight saving period.
SANDBOX and LIVE look the same when done with the above checklist.
Note: the csv file I use has very simple fields with only TEXT and NUMBER fields, and one DATE field (DOB). The date field is in the format of “MM/DD/YYYY” and I always carefully ensure to select that in the import panel.
Which reminds me - before this debacle I was using a before insert hook to ensure Zulu time when importing the dates into the collection.
For testing reasons I went without it this time, and I get the above error.
I’ll do some testing on the DATE field import and report back.
