Thanks for your reply Chillu,
I forgot to mention that:
- Before last tuesday I did not even know silverstripe was a CMS
- I was given the task to “Upgrade 3.3 version or port to wordpress” for a site not made by me.
- I have proto-basic knowledge of composer
Given this premise I know I am really under-specialized on the matter so i am not asking or blaming anything.
Mine was just a feedback, if, in my case, could worth anything.
Back to the documentation:
I was referring to
- Leave custom folders like mysite or themes in place.
Leave where? In webroot or in the 4.0 temporary folder?
Identify system folders in your webroot (
framework and any additional modules).
Delete existing system folders (or move them outside of your webroot).
private static $table_name = 'MyDataObject' for any custom DataObjects in your code that are namespaced. This ensures that your database table name will be
MyDataObject instead of
Me_MyPackage_Model_MyDataObject (converts your namespace to the table_name).
Here sample code would help. I tried add namespaces to every class extending DataObject. Was that correct?
Here the doc says “any custom DataObjects in your code that are namespaced”, So should have I re-namespaced only the ones that were namespaced already in the 3.3 installation? I could not find any though.
- Ensure you add namespaces to any custom classes in your
mysite folder. Your namespaces should follow the pattern of
Vendor\Package with anything additional defined at your discretion. Note: The
PageController classes must be defined in the global namespace (or without a namespace).
Here also sample code could help. (and where are they located exactly. mysite/code/ ? And are they all custom classes or in there some are core and some are custom?)
- Install the updated framework, CMS and any other modules you require by updating your
composer.json configuration and running
Does the doc mean I have to go to the old version and run composer update? or to the new temporary directory 4? I suppose I have to run the command inside the old version
Some features have been split into their own modules, such as
errorpage . Please refer to
recipe-cms composer.json and
recipe-core composer.json for a list of recommended modules to include.
Check if you need to adapt your code to changed PHP APIs. For more information please refer to the changelog. There is an upgrader tool available to help you with most of the changes required (see below).
Visit http://yoursite.com/dev/build/?flush=1 to rebuild the website database.
New site or old site?
I could also evalute a quotation for the upgrade process if anybody is interested.
I’ll check the upgrader.