17487 Posts in 4473 Topics by 1978 members
|Go to End||Next >|
9 July 2007 at 11:36pm
Today Andrew went through bugs reported since rc1 and so you can now sleep easier with the following improvements:
ChangeLog since 2.0.2-rc1:
- db/build authorisation fixed for dev sites
- Changes to improve compatibility when upgrading from older versions
- Removed debug messages that showed up when changing pages on
servers beginning with dev.*
- Improvements to image inserter
- Fix multiple "broken" in class attribute of HTML Content
- Fixed bug with TreeDropdownField when you clicked the expand link 3
or more times, it wouldn't close
- Added dimension fields when inserting images to provide more control on image sizes
10 July 2007 at 1:42pm
I just noticed while adding a blog post to silverstripe.com that somewhere in the past few months we broke the insert-flash object; you can choose a folder but no objects appear to insert into your HTML Editor. Elijah's having a look at this ...
10 July 2007 at 2:20pm
> somewhere in the past few months we broke the insert-flash
> object; you can choose a folder but no objects appear to insert into
> your HTML Editor. Elijah's having a look at this ...
Here is a patch that fixes the Insert Flash button: BUGFIX-Make-Insert-Flash-work-cms-sapphire-gsoc-r38163.patch
I've tested, and this patch applies cleanly to silverstripe-v2.0.2-rc2.
I'll commit this to the gsoc branch.
Hope this helps,
11 July 2007 at 7:21am Last edited: 11 July 2007 7:23am
> ChangeLog since 2.0.2-rc1:
> db/build authorisation fixed for dev sites
I installed SilverStripe 2.0.2-rc2 on new.elijahlofgren.com which runs Apache 1.3.37 (Unix) MySQL 5.0.27-standard PHP 5.2.3
It installed fine, but I was unable to run /db/build until I temporarily commented out this line in sapphire/core/model/DatabaseAdmin.php:
BasicAuth::requireLogin("SilverStripe developer access. Use your CMS login", "ADMIN");
I tried setting this in mysite/_config.php, but it did not work:
Security::setDefaultAdmin('<admin login>','<admin password>');
Anyone else had problems with running /db/build on 2.0.2-rc2?
Note, I had the same problem with 2.0.2-rc1.
11 July 2007 at 7:58am
This was an area that Andrew worked with on the last release so is probably why you're finding this ... basically you DO want protection from running db-build, but it seems it now may be too hard to run it
11 July 2007 at 9:45am
It shouldn't ask for authorisation if the site is in dev mode. Should I add code to the default _config.php to put the site in dev mode by default?
11 July 2007 at 9:53am Last edited: 11 July 2007 9:57am
I think a rule, say in _config.php along the lines of
if (http_host=='localhost' or http_host begins with 'dev.') then devmode=true
(Sam and I had discussed an interface in the installer to do this, however I'd suggest the above instead, for the sake of speed and not introducing issues; I'd really like us to release 202 ASAP as I want to mention it in a newsletter in a few days)
Additionally, though, wasn't Elijah's problem the fact that while /db/build did ask for a password, it didn't let him type in any password to actually let him proceed ...
11 July 2007 at 10:34am
> Additionally, though, wasn't Elijah's problem the fact that while /db/build did ask for a password, it didn't let him type in any password to actually let him proceed ...
Yeah, it basically wasn't accepting any password. However, it works on Apache/2.2.3 (Ubuntu) PHP/5.2.1 so I should do some debugging to see what the problem is.
Off to eat supper,
|Go to Top||Next >|