Curious if anyone else gets this message? And what is the cause? Is it IF Admin and Site Forms don't match? ... that would seem unlikely as Site Form often contains a Submit Button.
It'd be great to have more info from Seblod about this. It seems when I create a long form, inevitably, I get this message. And must move all fields out of the form and then back in to correct. Arrgh. Well this appear not true either. I moved every field out of the Site and Admin form and still got the Oops ... msg.
I am using a shared server on HostGator. While their servers do include php5.2, MySQL 5.5+, Apache 2.x+, they've given me a line in HTACCESS to load PHP5.3 per below, so I doubt that's the cause of my problem.
# Use PHP 5.3
AddType application/x-httpd-php53 .php
in php.ini, I also set
max_user_vars=3000
Any one else getting this "Oops! Fields not found" message?
Very frustrating and I am wondering if Seblod is stable enough for the everyday web lackey ... that'd be me.
Any one have a clue as to what causes this error? It's been frustrating me for days... I can't seem to nail down how a field could not be found. So far, this has only happened with long content types. I am not changing any field names in the dB table. Hmmm....
Hi cubist,
Do you get this error in admin when you try to create a new article with your fields or is the error on the frontend?
If it is in admin - create article - it might be because you are losing the admin form template. I had a similar issue where in Forms & Content Types something would go wrong with template settings for that form and I would get "oops! fields not found" message in create article. (not sure why this happens)
If I understand this correctly, Seblod creates autosaves of versions of your forms each time you save them and you can revover them by going to Form & Content Types and click on the box between the status green tick and id number of your form. That takes you to the Version Manager - Forms & Content Types. There you click on the orange tick to "go back to this version" of your form.
Hope this solves your problem otherwise we need one of the Devs to try to figure out this issue.
Anjo
Thanks. I must have done an inadvertent search and replace in MySQL. I thought I had not affected any CCK tables, but I must have. Thanks for the version reminder!