Tried out the page_factory extension this morning using:
config.gem 'radiant-page_factory-extension', :lib=> 'page_factory' (in
environment.rb)
rake db:migrate:extensions
rake radiant:extensions:update_all
Added lib/news_item_page_factory.rb and presto... Working awesomely
locally.
Push to Herok
The page_parts extension works perfectly fine in general but when trying to
add a file page_part in a small custom extension I get an error. Is there
anything following that I might have screwed up?
First, the setup.
Radiant 0.9.1. Latest page_parts extension. paperclip is installed. gem
put
> Push to Heroku seems fine, gem installed ok, but get NoMethodError
> (undefined method `page_factory=' for #).
I would guess either your Heroku instance needs to run the extension
migrations, or just get restarted to pick up the new columns. I haven't tried
running it on Heroku myself, sorry.
Thanks for the quick reply Josh. I'll give that a try. My whole
database was pushed up to heroku, and a restart is automatic after the
git push or db:push but it might just do the trick.
On Sep 16, 1:01 pm, Josh French wrote:
> > Push to Heroku seems fine, gem installed ok, but get NoMethodErro
> The error occurred while evaluating nil.include?
Is this happening in development mode? If so, it is probably my favorite*
ActiveRecord bug:
https://rails.lighthouseapp.com/projects/8994/tickets/1339-arbase-should-not-be-nuking-its-children-just-because-it-lost-interest
The workaround is to e
Very strange. Changed in environment.rb:
# Make Active Record use UTC-base instead of local time
config.active_record.default_time_zone :utc
# config.time_zone = 'UTC'
Mongrel running in dev mode - still getting the error.
In production - no error.
Color me baffled
On Thu, Sep 16, 2010 at 4:1
All it needed was a heroku restart. I did the db:push after the git
push. Had I done it the other way around i wouldn't have tripped.
On Sep 16, 1:12 pm, jazzhermit wrote:
> Thanks for the quick reply Josh. I'll give that a try. My whole
> database was pushed up to heroku, and a restart is au
> Mongrel running in dev mode - still getting the error.
> In production - no error.
You won't see this in production thanks to class caching; this only happens in
dev mode, when certain modules fail to reload cleanly between requests.
I created a new 0.9.1 project using just the extensions and
Thanks Josh! I'll give it another shot with a fresh project and see what
happens. Hopefully it does the trick
- Joel
On Sep 16, 2010, at 5:54 PM, Josh French wrote:
>> Mongrel running in dev mode - still getting the error.
>> In production - no error.
>
>
> You won't see this in production
Apparently, 'chronicle' and 'globalize2' are wildly incompatible[1]. Does
anyone know of a solution that'll give me solid page versioning and
multi-language content management? Both extensions look fantastic in and of
themselves...it's just a shame they don't get along. :-(
-dan
-- Footnotes
[1]
10 matches
Mail list logo