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

Errors after upgrade to v. 2.3.3 (from 2.2.3)


Reply


3 Posts   1407 Views

Avatar
evski

Community Member, 6 Posts

8 September 2009 at 8:05pm

Errors after upgrade to v. 2.3.3 (from 2.2.3)

Any assistance appreciated !

EVan

Followed upgrade instructions deleting

cms, sapphire, jsparty and auth_openid

and replacing these directories from the download ( although auth_openid wasnt in the download of 2.3.3 so didnt copy over; )

after run http://mysite.com/db/build?flush=1

goes to

http://mysite.com/Security/login

with error

XML Parsing Error: junk after document element
Location: http://mysite.com/Security/login
Line Number 2, Column 1:

<b>Warning</b>: file_exists() [<a href='function.file-exists'>function.file-exists</a>]: open_basedir restriction in effect. File(/home/httpd/vhlinks/mysite.com/.safe_mode/_config.php) is not within the allowed path(s): (/tmp:/usr/local/lib/php:/usr/local/apache/phpinc/:/home/nzsnow/mydirectory/) in <b>/home/nzsnow/mydirectory/sapphire/core/i18n.php</b> on line <b>1739</b><br />
^

and if i try my home page

http://mydirectory/

XML Parsing Error: junk after document element
Location: http://mysite.com/
Line Number 2, Column 1:<b>Warning</b>: file_exists() [<a href='function.file-exists'>function.file-exists</a>]: open_basedir restriction in effect. File(/home/httpd/vhlinks/mysite.com/.safe_mode/_config.php) is not within the allowed path(s): (/tmp:/usr/local/lib/php:/usr/local/apache/phpinc/:/home/nzsnow/mydirectory/) in <b>/home/nzsnow/mydirectory/sapphire/core/i18n.php</b> on line <b>1739</b><br />
^

Avatar
Double-A-Ron

Community Member, 604 Posts

15 November 2009 at 9:23pm

Hi evski,

Can you try creating a folder in your root (along side sapphire, jsparty etc) called "silverstripe-cache".

Give this folder 777 permissions. Try again and let me know how that goes.

Aaron

Avatar
zenmonkey

Community Member, 532 Posts

3 December 2009 at 10:47am

I'm experiencing a similar error, and I have a silverstripe-cache dir set to 777