[Radiant] Re: Edge Radiant on Heroku SASS/Compass problem
Thank you. That helps. On 19 дек, 03:55, john muhl wrote: > On Sat, Dec 18, 2010 at 1:31 PM, Martin Silenus wrote: > > Hi everyone. I have a problem with my Radiant application. I try > > running it on heroku.com, but can't get it work. > > i put `Sass::Plugin.options[:never_update] = true` at the end of my > environment and use `sass --watch` to keep things up to date in > development. you'll need to commit the static versions to your repo. > there's also a plugin called hassle that works by emitting generated > css to RAILS_ROOT/tmp
Re: [Radiant] Re: Duplicate 'slug' and 'breadcrumb' fields after adding page_fields extension
On 18 Dec 2010, at 19:00, Joshua Danger French wrote: > On Dec 17, 2010, at 10:52 PM, Todd wrote: >> Do you think edge is stable enough for me to get by for a while? I >> know edge is, by definition, not "stable," but I would really like to >> have the PageFields functionality (without my site going down in >> flames). > > Edge has been baking for a while and I know others are using it. As far as I > know all the outstanding issues are enhancements, which should mean there are > no *known* bugs. I think the last feature added was Spanner's config work, so > he's probably the current authority on whether edge is stable or not... > personally, I'm comfortable with it. I've been using it in public without problems and it tests clean. The next things that happen - as far as I know - are more fundamental so what you get at the moment is probably as stable as it will be for a while. will
[Radiant] Re: Duplicate 'slug' and 'breadcrumb' fields after adding page_fields extension
You're comfortable with it, but your middle name is also Danger. :-) But anyway that's good enough for me. We're not actually launching for another month or so...long enough to catch anything major. And maybe the next "stable" version will be released by then. Thanks, Joshua. On Dec 18, 12:00 pm, Joshua Danger French wrote: > On Dec 17, 2010, at 10:52 PM, Todd wrote: > > > Do you think edge is stable enough for me to get by for a while? I > > know edge is, by definition, not "stable," but I would really like to > > have the PageFields functionality (without my site going down in > > flames). > > Edge has been baking for a while and I know others are using it. As far as I > know all the outstanding issues are enhancements, which should mean there are > no *known* bugs. I think the last feature added was Spanner's config work, so > he's probably the current authority on whether edge is stable or not... > personally, I'm comfortable with it.
Re: [Radiant] Edge Radiant on Heroku SASS/Compass problem
On Sat, Dec 18, 2010 at 1:31 PM, Martin Silenus wrote: > Hi everyone. I have a problem with my Radiant application. I try > running it on heroku.com, but can't get it work. i put `Sass::Plugin.options[:never_update] = true` at the end of my environment and use `sass --watch` to keep things up to date in development. you'll need to commit the static versions to your repo. there's also a plugin called hassle that works by emitting generated css to RAILS_ROOT/tmp
[Radiant] extensions not visibile after deploy w/ capistrano + git
I can't figure out why - but I'm not seeing my extensions (code_ray and capistrano) in the admin panel after I deploy my radiant app w/ capistrano + git. I have capistrano configured to deploy the extensions as git submodules and they appear to be deployed properly per the ls below but again - nothing showing up in the admin panel. Thanks for the help! [f...@localhost radiant]$ ls -lh current/vendor/extensions/code_ray/ total 32K drwxrwxr-x 3 fima fima 4.0K Dec 18 11:06 app -rw-rw-r-- 1 fima fima 282 Dec 18 11:06 code_ray_extension.rb drwxrwxr-x 3 fima fima 4.0K Dec 18 11:06 lib drwxrwxr-x 3 fima fima 4.0K Dec 18 11:06 public -rw-rw-r-- 1 fima fima 4.2K Dec 18 11:06 Rakefile -rw-rw-r-- 1 fima fima 1.5K Dec 18 11:06 README drwxrwxr-x 3 fima fima 4.0K Dec 18 11:06 spec
[Radiant] Edge Radiant on Heroku SASS/Compass problem
Hi everyone. I have a problem with my Radiant application. I try running it on heroku.com, but can't get it work. heroku logs print that: # Logfile created on Sat Dec 18 11:14:37 -0800 2010/!\ FAILSAFE /!\ Sat Dec 18 11:14:41 -0800 2010 Status: 500 Internal Server Error Read-only file system - /disk1/home/slugs/ 382843_374637c_e736-6a817119-daa4-4a15-a488-029af9c67e0d/mnt/public/ stylesheets/admin/main.css /disk1/home/slugs/382843_374637c_e736-6a817119-daa4-4a15- a488-029af9c67e0d/mnt/vendor/radiant/vendor/plugins/haml/rails/../lib/ sass/plugin.rb:231:in `initialize' /disk1/home/slugs/382843_374637c_e736-6a817119-daa4-4a15- a488-029af9c67e0d/mnt/vendor/radiant/vendor/plugins/haml/rails/../lib/ sass/plugin.rb:231:in `open' /disk1/home/slugs/382843_374637c_e736-6a817119-daa4-4a15- a488-029af9c67e0d/mnt/vendor/radiant/vendor/plugins/haml/rails/../lib/ sass/plugin.rb:231:in `update_stylesheet' /disk1/home/slugs/382843_374637c_e736-6a817119-daa4-4a15- a488-029af9c67e0d/mnt/vendor/radiant/vendor/plugins/haml/rails/../lib/ sass/plugin.rb:85:in `update_stylesheets' /disk1/home/slugs/382843_374637c_e736-6a817119-daa4-4a15- a488-029af9c67e0d/mnt/vendor/radiant/vendor/plugins/haml/rails/../lib/ sass/plugin.rb:78:in `each' /disk1/home/slugs/382843_374637c_e736-6a817119-daa4-4a15- a488-029af9c67e0d/mnt/vendor/radiant/vendor/plugins/haml/rails/../lib/ sass/plugin.rb:78:in `update_stylesheets' /disk1/home/slugs/382843_374637c_e736-6a817119-daa4-4a15- a488-029af9c67e0d/mnt/vendor/radiant/vendor/plugins/haml/rails/../lib/ sass/plugin.rb:76:in `each' I read this topic http://groups.google.com/group/radiantcms/browse_thread/thread/8bfee0698ec1f7dc/04a7abfab43e83d2?lnk=gst&q=sass+heroku#04a7abfab43e83d2 but it didn't help me at all.. Is there a way to use static sass? Or may be another way to solve the problem? Thanks.
Re: [Radiant] Re: Duplicate 'slug' and 'breadcrumb' fields after adding page_fields extension
On Dec 17, 2010, at 10:52 PM, Todd wrote: > Do you think edge is stable enough for me to get by for a while? I > know edge is, by definition, not "stable," but I would really like to > have the PageFields functionality (without my site going down in > flames). Edge has been baking for a while and I know others are using it. As far as I know all the outstanding issues are enhancements, which should mean there are no *known* bugs. I think the last feature added was Spanner's config work, so he's probably the current authority on whether edge is stable or not... personally, I'm comfortable with it.
Re: [Radiant] Re: deploying radiant 0.9.1 with capistrano
looks like this was an issue w/ my env path from what i could tell -
everything is working fine now . i'm able to deploy + migrate cleanly.
woohoo!
On Fri, Dec 17, 2010 at 4:31 PM, Fima Leshinsky wrote:
> so here's where things are failing for me now. This seems like it's
> specific to capistrano and not radiant :/
>
> * executing `deploy:update_code'updating the cached checkout on all
> servers
> executing locally: "git ls-remote g...@github.com:fleshins/radiant.git
> master"
> * executing "if [ -d /var/www/html/radiant/shared/cached-copy ]; then cd
> /var/www/html/radiant/shared/cached-copy && git fetch -q origin && git reset
> -q --hard 04edfa7f2f3f00635ac7dcda343ab891cf06fd68 && git submodule -q init
> && for mod in `git submodule status | awk '{ print $2 }'`; do git config -f
> .git/config submodule.${mod}.url `git config -f .gitmodules --get
> submodule.${mod}.url` && echo Synced $mod; done && git submodule -q sync &&
> git submodule -q update && git clean -q -d -x -f; else git clone -q
> g...@github.com:fleshins/radiant.git
> /var/www/html/radiant/shared/cached-copy && cd
> /var/www/html/radiant/shared/cached-copy && git checkout -q -b deploy
> 04edfa7f2f3f00635ac7dcda343ab891cf06fd68 && git submodule -q init && git
> submodule -q sync && git submodule -q update; fi"
>
> I tried running this locally on the target server and got a syntax error.
> :P
>
>
>
> On Fri, Dec 17, 2010 at 1:22 PM, Fima Leshinsky wrote:
>
>> hm .. so it looks like git is placing the submodules (extensions) located
>> in vendor/extensions in shared/cached-copy instead of the 'current'
>> directory . do i need to symlink the extensions from the shared directory to
>> 'current'?
>>
>>
>> On Fri, Dec 17, 2010 at 11:06 AM, Fima Leshinsky wrote:
>>
>>> ok so the log file error is due to the log file not existing in my shared
>>> directory - not sure how to address it but probably not a show stopper
>>>
>>> the extension errors appear to be due to me not using Git properly? I
>>> found a thread that discusses having to use Git submodules to manage
>>> extensions .. going to play with that and see what happens :P
>>>
>>
>
Re: [Radiant] Event Calendar extension - ERROR: relation "taggings" does not exist
Stoyan, You need 'taggable' too. 'taggable_events' is just a bit of glue to apply it to the calendar. Best, Will Pardon brevity: small phone, fat thumbs. On 17 Dec 2010, at 23:08, SS wrote: > Hi, > > I've been looking for the right extension/gem that will fix this error > message that I keep getting when creating a new Calendar using the > Event Calendar extension: > > > Admin::CalendarsController#create (ActiveRecord::StatementInvalid) > "PGError: ERROR: relation \"taggings\" does not exist\n: SELECT > a.attname, format_type(a.atttypid, a.atttypmod), d.adsrc, a.attnotnull > \n FROM pg_attribute a LEFT > > > Here are all the extensions I've installed in Radiant: > > event_calendar > taggable_events > > > I thought all I needed were those two extensions. Do I need another > Rails gem? Any suggestions on what to install or configure? > > > Thanks, > S
