Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

Upgrading SilverStripe /

Ask questions about upgrading SilverStripe to the latest version.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

Upgrade 2.4.7 to 3.0.1 Content field missing


Go to End


3 Posts   1934 Views

Avatar
Jimmo

Community Member, 2 Posts

25 August 2012 at 5:20pm

Hello,

I have just upgraded from 2.4.7 (I think its .7, the version does not show in the admin so its either .6 or .7), and now i get no content field in the admin. I thought maybe i should add the admin account into 'Content Authors' but i still don't get the editor. I only get a 'Metadata' drop down group after the 'Navigation Label' field (see attached image) - (I also checked the other TABs incase it was hiding).

So I then did a clean install of 3.0.1 and after complaining about a missing rewrite module (im running iis7 with URL Rewrite module) it seems to work ok, it shows the content field. there are no script errors or missing files (fro mthe console etc).

It is a VERY simple site, and the only change i have made is to create a new theme from the tutorial with 2 content pages, and added a few pages.

The upgrade i did => remove folders: cms, mssql, sapphire and copy in new cms and framework. Then change 'sapphire' to 'framework' in web.config (and .htaaccess for the sake of completeness).

What else should I need to do to get the tineMCE content editor working??

cheers

Attached Files
Avatar
Jimmo

Community Member, 2 Posts

21 September 2012 at 12:20pm

Has no one else had this issue?

Avatar
(deleted)

Community Member, 473 Posts

21 September 2012 at 1:23pm

Edited: 21/09/2012 1:23pm

Try using 3.0.2, specifically the 3.0.2 index.php. I'm fairly sure this bug got fixed in it.