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.

Archive /

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

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

SilverStripe 2.0.2-rc1


Reply


38 Posts   75149 Views

Avatar
Matt

Core Development Team, 84 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

Core Development Team, 84 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. [url=SilverStripe-202rc3-has-no-theme-option-when-warnings-present.pdf]See attached PDF[/url]

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...

Avatar
Sigurd

Forum Moderator, 628 Posts

12 July 2007 at 5:00pm

Edited: 12/07/2007 5:01pm

Matt/Sam/Andy. The warning that I raised also existed in 2.0.1 so unless its really obvious and simple to fix, I say hold off!

Here's an excerpt from me just installing 201:

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 'assets' folder...
# Creating 'mysite/_config.php'...
# Creating '.htaccess' file...
# Building database schema...
# Waiting until the 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
# Populating initial content and administrative account

Avatar
Sigurd

Forum Moderator, 628 Posts

12 July 2007 at 5:15pm

Edited: 12/07/2007 5:17pm

Here's an idea. Given if you get a warning with SilverStripe (low memory), your site may not install properly, I don't think we need to delay the release to make it work when the warning shows.

People will attribute any issues back to the warning they saw.

Secondly, if the installer says everything is sweet, there are no known errors. Except for a meaningless warning that pops up for about 200ms that's been around for months anyway.

So... I say we release it as-is, but work on fixing the above issues shortly, on the basis that 202 is known to be superior than 201, and we need some lead-in time before OSCON, and I want to release the newsletter in the next few days.

Avatar
Tim

Core Development Team, 201 Posts

12 July 2007 at 8:21pm

Edited: 12/07/2007 8:22pm

If the issues is detecting the amount of memory allocated to PHP before installing is sufficient, will the [url=http://us2.php.net/memory_get_usage]memory_get_usage[/url]
function help?

Also, somewhat related is this [url=http://www.ibm.com/developerworks/opensource/library/os-php-v521/]article on 5.20 memory management[/url]

Avatar
elijahlofgren

Google Summer of Code Hacker, 222 Posts

14 July 2007 at 3:44pm

> SilverStripe 2.0.2-rc3 is released.

Andy, the "Insert Flash" button is broken on 2.0.2-rc3, I've [url=http://www.silverstripe.com/contributions/flat/2128]posted a 2 line patch that fixes it[/url].

Hope this helps,

Elijah

Avatar
Sigurd

Forum Moderator, 628 Posts

14 July 2007 at 4:01pm

I've renamed 202rc3 to SilverStripe 2.02 official release, so those with 202rc3 have the same as 202 official, no need to upgrade :)

Please let us know of any bugs! :)

We'll work on releasing the windows version now