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.

Upgrading SilverStripe /

Ask questions about upgrading SilverStripe to the latest version.

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

Upgrade from 2.3.3 -> 2.3.6


Reply


6 Posts   1158 Views

Avatar
dompie

Community Member, 88 Posts

11 February 2010 at 9:10am

Edited: 11/02/2010 9:15am

1) i replaced folders cms, sapphire and jsparty uploaded and run /dev/build?flush=1
Version Number 2.3.3 was still shown in Backend
2) replaced folder themes and root files and run again /dev/build?flush=1
Version Number 2.3.3 was still shown in Backend
3) edited in LeftAndMain.php the static link output and changed it back to original
4) Went for a cup of tea, thinking and then i relogging...suddenly i reveive a website error for the backend, frontend works fine.

5) Done a /admin/?isDev=1
Output:

[User Error] Uncaught Exception: Object->__call(): the method 'gethtmleditorconfigforcms' does not exist on 'Member'
GET /admin/?isDev=1

Line 551 in htdocs/sapphire/core/Object.php
Source

542             case isset($config['function']) :
543                return $config['function']($this, $arguments);
544             
545             default :
546                throw new Exception (
547                   "Object->__call(): extra method $method is invalid on $this->class:" . var_export($config, true)
548                );
549          }
550       } else {
551          throw new Exception("Object->__call(): the method '$method' does not exist on '$this->class'");
552       }
553    }
554    
555    // -----------------------------------------------------------------------------------------------------------------
556    
557    /**

Trace

* Object->__call(getHtmlEditorConfigForCMS,Array)
* Member->getHtmlEditorConfigForCMS()
Line 158 of LeftAndMain.php
* LeftAndMain->init()
Line 84 of CMSMain.php
* CMSMain->init()
Line 113 of Controller.php
* Controller->handleRequest(HTTPRequest)
Line 277 of Director.php
* Director::handleRequest(HTTPRequest,Session)
Line 121 of Director.php
* Director::direct(/admin/)
Line 118 of main.php


Any ideas how i can fix this?

Avatar
Double-A-Ron

Community Member, 604 Posts

11 February 2010 at 10:27am

The fact that you still see 2.3.3 in the CMS footer really indicates to me that you over-wrote the core directories on top of 2.3.3. That number is pulled from the "version" file inside each directory. So that file hasn't updated, who knows what else.

I've had trouble with this in the past. These days if the update is a manual one like this, I will upload the core directories as a different name (e.g. "sapphire2"). Then delete the originals and rename the new directories. Followed by a Dev build.

Avatar
dompie

Community Member, 88 Posts

11 February 2010 at 10:54am

Ay damn...i tricked myself ^.^

I deleted the old files inside my workspace, put the new inside that directory and uploaded them to the server. But i did not delete them on the server -.-'

Avatar
Sunnybex

Community Member, 39 Posts

12 February 2010 at 12:14am

Edited: 12/02/2010 12:15am

Hi,

I got exactly the same problem: after Dompie's steps 1) and 2), and went to admin/dev/build - I still have version 2.3.3 shown in the backend. But the version files in css, saphire and jsparty (on the server) tell me it is SS 2.3.6.

Ok, I skipped the editing and the tea, but it should be the upgraded version anyway, shouldn't it?

Thanks for your help

Bex

Avatar
dompie

Community Member, 88 Posts

12 February 2010 at 6:59am

make sure to (first) delete the old folders and then paste the new folders.

Avatar
Sunnybex

Community Member, 39 Posts

12 February 2010 at 8:35pm

Edited: 12/02/2010 8:45pm

well, my problem was the core folder on my Hetzner-Server, public_html. It links to somewhere else, so if it is overwritten or deleted, the content is not touched here. (Maybe it´s the save-mode for idiots like me...) Anyway, never touch the public_html on Hetzner, just replace the folders inside. Nevertheless, you can call them and they will restore the folder with the ss2.3.3 (or whichever) from 'somewhereelse' and you can see the two folders with the old and the newer version.
And then, yes, it is a good way two rename the folders you would like to upload, then upload them in that public_html-file, delete the old ones from the sever and rename the new ones. (dev_build + flush)
Worked fine for my and now it´s time for tea....