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.
> 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.
SilverStripe 2.0.2-rc3 is released. It contains the following changes over 2.0.2-rc2:
- Changed tooltip for link insertion to say that text needs to be highlighted
- Check for existance of Permission table when authenticating for db/build
- Don't require authentification for db/build when running the installer
- Added templates to UserDefinedForm so that it works out of the box better
- Removed some debug messages in tiny_mce_improvements.js
- Fixed some php notice level warnings
Something which looks benign, but is just a little worrying, is this warning that pops up if you install into a blank, new database:
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 ...
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.