Hello, I need some help! I was not the one who installed SilverStripe on my server. I am having trouble upgrading for 2.4.7 to 3.1 I read that all i need to do it update the cms folder and maybe the framework folder. I first just tried the cms and got all sorts of errors. I then noticed that my site is missing the framework folder. Any one out there have any ideas of what i can do or where to start? Thanks so much!
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.
- Page 11(current)
- 2
- Next 10 entries
if you are on 2.4.7 the framework folder is now different.
make sure you delete the old sapphire folder etc too.
also check your server requirements as well.
in many cases I only had to use the mysite folder, and the theme only when i upgraded. and from what you have said it is a hard to give you an accurate answer, if you get any errors / warnings please add them to the thread.
http://doc.silverstripe.org/framework/en/topics/debugging
this will be a help to debug as well.
Ahh I see now, thanks for the tip!
When I Update the old sappbhire dir to the new framework I now get a siteTree class does not exist in Page.php. Any Ideas?
Make sure you've got the cms module as well. See http://doc.silverstripe.org/framework/en/changelogs/3.0.0 and http://doc.silverstripe.org/framework/en/changelogs/3.1.0 for more things you'll need to be aware of.
I have the CMS module installed, all I did was swap out the shapphire dir with a new framework dir
Im also getting this warning.
Warning: Unknown class passed as parameter in framework/core/Object.php on line 472
Willr, My site is very customized. I have lots of code files. A update feels like a must. My site has be compromised by hackers a couple of times. I think its because Im on old version. In this case how would you suggest getting my cms up to date? try just an update or basically start from scratch and build on the new version? The latter is obviously not Ideal. Thanks!
Yes, and we're not supporting 2.4 after March 2015 so you will need to upgrade at some point.
Building on what you have got should be straight forward. After getting the framework and cms folders updated make sure you have new versions of all the modules as well and reference the changelog for any other information on upgrading.
- Page 11(current)
- 2
- Next 10 entries