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.

Archive /

Our old forums are still available as a read-only archive.

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

SilverStripe v2.3.0 installation issues


Go to End


2 Posts   1515 Views

Avatar
danc

Community Member, 4 Posts

17 November 2008 at 3:37am

Hi,

I just downloaded the latest SilverStripe v2.3.0 to install on our hsoting space. I have found 2 issues, the 1st was the protected $baseDir; at line 526 of the install.php, this was generating an error that wouldn't start the install script. I commented this out and then the next issue I found is that our webhost company put a - in the database names i.e. when I created a database silver it will call it web056-silver . The install process kept stripping the - out of the db name and therefore would then refuse to find the db to continue the install process.

If anyone has comments or solutions to these issues I'd love to hear them as the CMs looks great and I can't wait to actuallly get it installed and play with it properly.

Avatar
martimiz

Forum Moderator, 1391 Posts

21 November 2008 at 2:01am

Edited: 21/11/2008 2:09am

I wonder if you found a solution already, but for those who haven't, the following quickfix should allow you to install (I tested it, it seems to be working). Mind - this goes with no warranties whatsoever, I'm not the expert...

In config-form.html - line 110, near the end: add the requested character (-) to the regexp like so (see the last character of the [] block):

... this.value.replace(/[^A-Za-z0-9_-]+/g,'') ...

Then shift reload the page

As to the 'protected $baseDir' error - this is not clear since you didn't provide the actual error. Are you using PHP5? PHP4 won't recognize the 'protected' keyword...