Hi there,
We upgraded MySource Matrix recently to v3.6.0 and this weird thing happened - there are a number of forms that suddenly became nested content. So, a new standard page was created during the transfer of data, say with an asset id of 4919, and the body of the form can now be found in the content div as nested content. You can search for the form by it's asset no, say 2212, and it is there. You can edit it. But it no longer submits properly.
Is there any way to discover the asset within the tree (it has been replaced in its old position by the standard page of the same name) and elevate it back to its former position?
The other alternative is to build every single form that this has happened to again. Not a pleasant prospect, as there are many.
To clarrify, the upgrade process changed your forms into standard pages? Did I read that right?
Maybe the form is not working because caching is on??
No, what it did was whacked the forms down a level and inserted a standard page in their place, then nested the forms in that page. So, they exist … somewhere in the database … but not, apparently, in the asset tree.
Do forms not work when caching is on?
How odd. Forms that are nest into standard pages do not work when Caching is enabled (which is what I think Greg was trying to say). This is not what's happening on your system, though.
When did you get upgraded? Who performed the upgrade?
Edited to add that there is nothing in the upgrade procedure that would do anything like this, nor have I seen anything like this happening anywhere else. I'm just trying to get a handle on how the upgrade was performed.
It’s okay! A search of the asset tree revealed the forms … in fact, I had myself moved them to a shared area and then nested them several months ago on our development server, which became the upgraded version and which is different to the current live version (hence the perception of a huge change when comparing the original and upgraded versions). In the intervening time, including a long holiday in Europe, I completely forgot I had done this. :rolleyes:’ /> <img src=‘http://forums.matrix.squiz.net/public/style_emoticons/<#EMO_DIR#>/unsure.gif’ class=‘bbc_emoticon’ alt=’:unsure:
And yes, the reason they are not submitting is the nested content thing. Can you turn the caching off at an asset type level or must you do it for the whole site?
You need to turn caching off for all standard page asset types if you want to nest forms in them.