Anyone?
Further testing shows that when I don't include my module, I can verify
during any controller's spec that:
controllers_where_no_login_required = [SiteController]
As soon as I mix it in (even though it's an empty module), during the
environment init and just before specs start to
Does the site work ok when you boot the server? Or is it only tests
that are broken?
-Alex
http://beautifulpixel.com
On Jun 25, 2008, at 7:28 AM, Chris Parrish wrote:
Anyone?
Further testing shows that when I don't include my module, I can
verify during any controller's spec that:
But the provided matcher that does
page.should render(tag).as(expected)
is so handy! But you are definitely right. White space issues
especially make this a bit cumbersome. Perhaps that matcher needs to
be expanded. What if you could do this:
page.should render(tag).with_tag('h1',
Also, can you run `rake production db:bootstrap --trace` and put the
output in a pastie? (http://pastie.org)
Sean
Alfredo Perez wrote:
Hi, I have followed the steps mentioned at the radiant site.
1.- Created a project, radiant --database mysql my_project
2.- Created a mysql database
On Wed, Jun 25, 2008 at 11:29:40AM -0500, Sean Cribbs wrote:
Alfredo,
Which version are you using?
Sean
Alfredo Perez wrote:
Hi, I have followed the steps mentioned at the radiant site.
1.- Created a project, radiant --database mysql my_project
2.- Created a mysql database my_project
Here it is with --trace:
(in /usr/lib/ruby/gems/1.8/gems/radiant-0.6.7/photos)
** Invoke production (first_time)
** Execute production
** Invoke environment (first_time)
** Execute environment
rake aborted!
Mysql::Error: #42S02Table 'my_project.config' doesn't exist: SHOW FIELDS FROM
`config`
Alfredo Perez wrote:
On Wed, Jun 25, 2008 at 11:29:40AM -0500, Sean Cribbs wrote:
Alfredo,
Which version are you using?
Sean
Alfredo Perez wrote:
Hi, I have followed the steps mentioned at the radiant site.
1.- Created a project, radiant --database mysql my_project
2.- Created a
Only tests (specs, actually).
Alex Wayne wrote:
Does the site work ok when you boot the server? Or is it only tests
that are broken?
-Alex
http://beautifulpixel.com
On Jun 25, 2008, at 7:28 AM, Chris Parrish wrote:
Anyone?
Further testing shows that when I don't include my module, I can
Sorry I am a big time newbie
How do I do that?
Thanks Alex
Alfredo
On Wed, Jun 25, 2008 at 10:31:22AM -0700, Alex Wayne wrote:
/usr/lib/ruby/gems/1.8/gems/radiant-0.6.7/vendor/extensions/gallery/
app/models/gallery_item.rb:16
There's your problem. Try removing that extension,
I think it all matters based on your context. I do agree that I would
follow Sean's approach first. For example, Alex, I might do this:
r:box
div class=box
h2
img src=/images/icons/r:icon /.png /
r:title /
/h2
div class=content
r:content /
/div
/div
/r:box
You can scope your
Maybe config['foo'] should just return nil if no config table exists?
Or radiant maybe shouldn't load plugins at all if the project has no
database yet?
-Alex
http://beautifulpixel.com
On Jun 25, 2008, at 11:11 AM, Jim Gay wrote:
What would be the way to fix this for extension
The issue lies in Radiant's extension loader, and affects any
extension attempting to set config variables. I'm not sure the onus
is on the extension developer to catch an un-initialized environment.
Perhaps the upcoming extension registry's local interface should be
aware of the state of
I'm trying to use the radiant-settings extension and having a problem
in MySQL 5.0.27:
ActiveRecord::StatementInvalid (Mysql::Error: You have an error in
your SQL syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near 'key' at line 1:
SELECT
I don't know enough about the extension loading code to provide
insight, but Radiant.bootstrapped? seems like a good idea to me.
-Jim
On Jun 25, 2008, at 3:12 PM, Sean Cribbs wrote:
With the other recent problem related to bootstrapping, I'm
considering adding a method:
Use rake spec:extensions EXT=your_extension_name to just run the specs
for your extension.
By the way, does anyone else think it would be useful to run specific
spec(s) within an extension?
Perhaps using syntax like:
rake spec:extensions EXT=your_extension_name
Thats quite odd. Are you sure you are running the latest rspec gem?
Try a
gem install rspec
-Alex
http://beautifulpixel.com
On Jun 25, 2008, at 12:24 PM, Marty Haught wrote:
On Tue, Jun 24, 2008 at 9:15 PM, Alex Wayne
[EMAIL PROTECTED] wrote:
Radiant 0.6.7 generates extensions with a
Chris Parrish wrote:
Use rake spec:extensions EXT=your_extension_name to just run the
specs for your extension.
Oh, and you run it from the project's root - not the extension's.
-Chris
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search:
Alex Wayne wrote:
Thats quite odd. Are you sure you are running the latest rspec gem?
Try a
gem install rspec
-Alex
http://beautifulpixel.com
I've had troubles using the rSpec gem because Radiant ships with its own
version of rSpec and rSpec on Rails. Whenever I tried to use the gem,
Yes, I noticed that on one of my projects when I pushed it to the
server. Not patch yet. I think this is a bug in the rails MySQL
adapter for not treating key as a reserved word. I think.
-Alex
http://beautifulpixel.com
On Jun 25, 2008, at 12:08 PM, Jim Gay wrote:
I'm trying to use the
On Jun 25, 2008, at 3:12 PM, Sean Cribbs wrote:
With the other recent problem related to bootstrapping, I'm
considering adding a method: Radiant.bootstrapped?
I'm wondering if this behavior shouldn't belong to the extension base
class. Just yesterday I was wishing for a way to make an
20 matches
Mail list logo
