unable to add new pages after upgrading to cmsmadesimple 1.8.1 [SOLVED]

[davids355]

I have just upgraded my cmsmadesimple installation.

I was running cmsms 1.7.1
done a base upgrade to 1.8 run the upgrade script etc.

then I done a diff to 1.8.1

Everything seemed to work fine untill I tried to add new content - when I go to make a new page, there is no content block so I cannot add any content, also when I try copying an existing page, it will not let me.

I am running tinymce 2.7.2 which I beleive came with the new cmscore.

I have tryed completely removing tinymce and reinstalling it, no help.

Can someone give me some pointers?

Thanks in advance

[RonnyK]

Do you have the {content} tag in your template? As it is required to have the default {content} call

Ronny

[davids355]

I have {$capturedcontent} but I did try putting {content} back in the template, and it didn't help...

[Ziggywigged]

Maybe one of these posts will help you...
http://forum.cmsmadesimple.org/index.php/topic,45644.msg217391.html#msg217391
http://forum.cmsmadesimple.org/index.php/topic,45433.msg216270.html#msg216270

[davids355]

Ok I found the problem - I created a new template, made it default, then everything worked fine.

After that I found that a UDT name {contentads} was causing the problem - after reading the links by ziggywigged, it seems that anything with "content" in is being interpreted as the content?

So anyway, I renamed my UDT to contenads and it works fine!

Thanks for the help!

[odo]

Just thought I’ll write here my latest findings on subject (could be helpful for someone who finds him/herself in same situation where I was). I too had issues after upgrading to 8.1 and as I had similar situation before (upgrade 1.3 to 1.6 for example etc) I started to investigate what went wrong this time. Basically after upgrade everything seemed fine except the fact that I couldn’t add new content. I had content area to write to but after submit despite CMS’s somewhat misleading statement “ The content was successfully added to the database ” nothing was in fact added. And what turned out in my case was, that upgrade script was unable to upgrade database schema from 32 to 33 (found out this in debug mode). No errors were displayed during process  - message about converting from 32 to 33 claimed success. In reality it wasn’t and when I checked upgrade script I noticed that one field (secure) was added during this upgrade to content table. Of course when inserting new data CMS tried to save to that field but as it was missing error was generated (but not displayed of course) and nothing was saved. In my case upgrade script was unable to add field because in live environment database user had no ALTER rights.
So in conclusion I suggest two things that could save some time for future upgraders
1. some verification method for schema upgrade script to see if it has rights to alter something
2. CMS itself to somehow verify content after save and display message based on actual events (if not saved then error message)