Symphony.

Wasn't too sure how to name this error but it is really strange.

We have dumped a db from live to our staging environment and following the switch something really strange is happening when I try to create a new subsection manager field. The field takes a different form then expected. Just dumped the contents, one seemed like a Date field and another one looked like a normal text field. Cannot really understand why this is happening.

The strangest part is when I went into the subsection manager field php file and removed the create table return and put a die just after the table looked perfectly fine (just I couldn't go into the back-end to view/create entries anyway, I am assuming this is because symphony didn't register the field and got messed up.

Anyone would have any clue why this would happen? And if the problem is with the dump or with some files? (as we do not want to overload our live environment for testing stuff)

Issue seems to have been resolved after causing the above error, and re-saving. The previously created subsection manager items were still buggy but all new ones seem to be created fine.

Any idea why this would happen? maybe query caching or some other stupid issue?

I have to admit that I haven't understood your problem so far. Could you provide us with a few screenshots, please? Thanks a lot!

Sorry no screenshots I can send will try to re-explain.

1. Copied Live DB onto our Staging Env (due to posts being done on live we wanted to re-sync)
2. After a day or two we wanted to try creating a new section to extend the website which included Subsection Manager
3. When trying to Save a new Entry the subsection manager fails. due to no field relation_id found in field.
4. I decide to hack a bit and dump the entries of the new table through symphony datasource fields looked to belong to a different field such as a date... (very strange)
5. I decide to hack subsection manager and dump table structure when creating another Subsection Manager field. This looks fine, I remove the dump and since the system has been working fine.

I cannot really understand what caused the problem to be honest and seems to have been resolved in a very strange way. I assume it has something to do with the DB dump though this was done before and never caused us problems. I had created around 10 buggy subsection manager fields though they had to be cleared up so cannot provide a screenshot unfortunately.