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 2.0.2-rc1


Go to End


35 Posts   79700 Views

Avatar
Sigurd

Forum Moderator, 628 Posts

11 July 2007 at 2:05pm

Elijah... although "Director::set_environment_type('dev');" does a lot more than just turn off that password, hence my suggestion it is behind an "if". You don't want this running on a live, public, website, ever.

Avatar
elijahlofgren

Google Summer of Code Hacker, 222 Posts

11 July 2007 at 2:50pm

> Elijah... although "Director::set_environment_type('dev');" does a lot more than just turn off that password, hence my suggestion it is behind an "if". You don't want this running on a live, public, website, ever.

Hmm.. Then should I spent time trying to fix/find source of the problem where db/build authentication does not work on my remote server? Or should I just leave it since it works fine on my local test server and likely most other people's servers as well.

Avatar
Sigurd

Forum Moderator, 628 Posts

11 July 2007 at 11:37pm

Edited: 11/07/2007 11:40pm

Something which looks benign, but is just a little worrying, is this warning that pops up if you install into a blank, new database:

Installing SilverStripe...

I am now running through the installation steps (this should take about 30 seconds)

If you receive a fatal error, refresh this page to continue the installation
# Creating 'mysite/_config.php'...
# Creating '.htaccess' file...
# Building database schema...
# Waiting until the database is created before compiling the manifest

Warning: None of these templates can be found: ErrorPage.ss, Page.ss, ContentController.ss in /sites/dev.silverstripe.com/smagnusson/sigtest/silverstripe-v2.0/sapphire/core/SSViewer.php on line 53
# Checking mod_rewrite works

Installed SilverStripe successfully. I will now try and direct you to home/successfullyinstalled to confirm that the installation was successful.

Is this actually causing a problem? I'm assuming it doesn't need these files anyway, and this is a false alarm. I wouldn't want to delay 202rc3 from going live... ? Because there's no such thing as ErrorPage.ss nor ContentController.ss ...

Avatar
Sam

Administrator, 690 Posts

12 July 2007 at 2:31pm

For some reason, the system is tryig to render a 404 page before the manifest has been generated, or before the Page.ss has been copied to the right place, or before the _config.php has been generated.

Andrew - this should be investigated prior to releasing 2.0.2 stable.

Avatar
Sigurd

Forum Moderator, 628 Posts

12 July 2007 at 4:03pm

Edited: 12/07/2007 4:07pm

I also thought I'd look over the log files to see what sorts of files get requested when installed. I don't see any issue here:

192.168.1.11 - smagnusson [12/Jul/2007:16:01:38 +1200] dev56k:80 "GET smagnusson/sigtest/silverstripe-v2.0/InstallerTest/testRewrite HTTP/1.0" 200 2 "-" "-" (-)

192.168.1.22 - smagnusson [12/Jul/2007:16:01:33 +1200] dev56k:80 "POST /smagnusson/sigtest/silverstripe-v2.0/install.php HTTP/1.1" 200 562 "http://dev56k/smagnusson/sigtest/silverstripe-v2.0/install.php" "Mozilla/5.0 (Windows; U; Windows NT 5.2; en-G
B; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4" (54)

192.168.1.22 - smagnusson [12/Jul/2007:16:01:40 +1200] dev56k:80 "GET /smagnusson/sigtest/silverstripe-v2.0/home/successfullyinstalled HTTP/1.1" 200 2916 "http://dev56k/smagnusson/sigtest/silverstripe-v2.0/install.php" "Mozilla/5.0 (Windows; U; Windows NT 5.2; en-GB; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4" (-)

192.168.1.22 - smagnusson [12/Jul/2007:16:01:41 +1200] dev56k:80 "GET /smagnusson/sigtest/silverstripe-v2.0/cms/images/dialogs/alert.gif HTTP/1.1" 200 1916 "http://dev56k/smagnusson/sigtest/silverstripe-v2.0/home/successfullyinstalled" "Mozilla/5.0 (Windows; U; Windows NT 5.2; en-GB; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4" (-)

Avatar
Matt

Community Member, 86 Posts

12 July 2007 at 4:26pm

That warning has been there for a few versions now - since 2.0.1-rc1 I think?

It can be 'safely' ignored (aka. it doesn't stop the site from installing, but should be looked at sometime).

Avatar
Matt

Community Member, 86 Posts

12 July 2007 at 4:45pm

I think I know what the problem is actually.

Sam's right - it's looking for the template before the manifest is compiled, because as part of db/build, ErrorPage will create a file in the assets directory that will be used when the website is broken. (This is in case the error is in the template processor somewhere, meaning we can't render anything - it can at least show some kind of error message).

What it does mean is that it's looking for the ErrorPage.ss etc. template files before the manifest has been created.

In other words, it's an error that doesn't matter, because the next time you do a db/build or save the error page in the CMS, it will create that error message anyway.

Andy: It might be worth investigating a way for ErrorPage to know whether or not it's being called by the installer, and to not create a file if it is.

Avatar
Sigurd

Forum Moderator, 628 Posts

12 July 2007 at 4:49pm

Edited: 12/07/2007 5:19pm

Well I just lost my post, so here goes again.

1. If there's a warning detected by the installer (e.g. php mem limit under 32MB), you don't get the choice of theme. It just installs blackcandy. Not a biggie. See attached PDF

2. If memory limit is low (e.g. 25MB), it doesn't install and leaves you in a random, undefined state. You just see:

--
Installing SilverStripe...

I am now running through the installation steps (this should take about 30 seconds)

If you receive a fatal error, refresh this page to continue the installation
# Creating 'mysite/_config.php'...
# Creating '.htaccess' file...
# Building database schema...