[Radiant] Re: Re: Re: Re: Re: Adminstrator and Developer role clarific
Chris Parrish wrote: > The problem here is that some sites use snippets extensively for content > and writers need to create and edit those in order to create pages. > That's the beauty of snippets, they're versatile. But like you noticed, > when snippets hold Layout or other design-level content, it gets hairy > because writers have permissions to those snippets. > > I once suggested that there could be Page Snippets and Layout Snippets > (or Content Snippets and Design Snippets) but you run into the > complication-factor. At some point we're sliding down the slippery > slope to WordPress or some other massively-featured CMS. > > -Chris True, the last thing we need is an open-source version of Vignette!! We could always tag the Snippets with a simple "content only" or "structural" boolean, and only show those snippets that are appropriate to the user level? Or perhaps, only show the edit controls for those that are tagged (allowing users to see the names of the Snippets available to use in pages)? Jon. -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Re: Re: Re: Re: Adminstrator and Developer role clarific
I think we need core extensions that handle these problems. Tools like Drupal and ExpressionEngine of PHP fame handle de-coupled functionality very well. I think RadiantCMS retains a well-defined code base and development platform. With that said, I think focus should be shifted to extension development. Extensions can provide all the granular functionality and control one would need. The Page Group Permissions extension definitely is a great example. http://github.com/freels/radiant-extensions/tree/master/page_group_permissions/README We have core developers for Radiant itself, but I think Radiant could use some core developers for just extensions. I think the community and the promotion of Radiant could benefit greatly from that. What do you guys think? -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Re: Re: Re: Re: Adminstrator and Developer role clarific
Arik Jones wrote: > I think we need core extensions that handle these problems. Tools like > Drupal and ExpressionEngine of PHP fame handle de-coupled functionality > very well. I think RadiantCMS retains a well-defined code base and > development platform. With that said, I think focus should be shifted to > extension development. > > Extensions can provide all the granular functionality and control one > would need. The Page Group Permissions extension definitely is a great > example. > > http://github.com/freels/radiant-extensions/tree/master/page_group_permissions/README > > We have core developers for Radiant itself, but I think Radiant could > use some core developers for just extensions. I think the community and > the promotion of Radiant could benefit greatly from that. > > What do you guys think? Good idea. There are still numerous issues I think need to be sorted at the core, but a lot of functionality could come in the form of bolt-ons. My only issue, is the complex setup to ensure everything you need is in one place (unzip some, SVN some more and GIT the rest), and the complexity with updating multiple projects. How about even deploying extensions as gems (still doesn't solve updates, but one step at a time...) and requiring them in a environment file (like the Rails 2.1 gem handler)? http://ryandaigle.com/articles/2008/4/1/what-s-new-in-edge-rails-gem-dependencies I've got a number of useful tool extensions I've built, including text manipulation (upcase, downcase etc), truncation, redirection and so forth. Could be persuaded to OS them... Jon. -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Event organizing extension for Radiant
Hi Radiant community! I've been working on a Rails app for event/conference organisation - similar in goals to meetup.com, except I want it to be more like a customisable site for conference organisers. It's called Ba and lives here: http://gitorious.org/projects/ba Currently it lets you set up new events (happenings/conferences), sign up users, submit talk proposals, administer fees and promotion codes etc. I'll be adding more admin stuff like set up a program, reject/approve talks, billing etc. What I have not implemented yet is the ability to tweak the layout, add custom pages with semi-static content etc, and it's while researching how to do this that I finally decided to check out Radiant for real. My first impression with Radiant is great documentation and, great community and great code. I still haven't set it up, but will soon (tonight probably). So here is my question to you folks: Would it make sense to refactor Ba (currently a standalone Rails app) to be a Radiant extension for conference/event organisation? Would anyone else be interested in using this? (provided I make it general and useful enough). Even if noone else would use it, do you think it would make sense for me given I want to use Radiant for the CMS parts? We're talking around 10 models and controllers in addition to the Radiant ones, so it would be a fairly big extension. Another thing - I'm currently on Rails edge. Should I downgrade, or is it safe to assume that Radiant will run ok on Rails edge? Cheers, Aslak ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Event organizing extension for Radiant
Aslak, Glad to have you in the community! Would it make sense to refactor Ba (currently a standalone Rails app) to be a Radiant extension for conference/event organisation? Would anyone else be interested in using this? (provided I make it general and useful enough). Even if noone else would use it, do you think it would make sense for me given I want to use Radiant for the CMS parts? We're talking around 10 models and controllers in addition to the Radiant ones, so it would be a fairly big extension. We've done our best to make it fairly painless to move an existing application into a Radiant extension. And 10 models/controllers is not that big; the site-specific customizations and additions to the Redken site were around 20-30 models and controllers in a single extension! I say go for it, if you feel Radiant is the right fit. That said, you might be able to appropriate some of Radiant's ideas about how to manage static content into Ba without making it an extension. It's totally up to you. Another thing - I'm currently on Rails edge. Should I downgrade, or is it safe to assume that Radiant will run ok on Rails edge? Sean Schofield converted Spree (which shares some of the same 'guts' as Radiant) to Rails 2.1 over the weekend and I don't think he ran into too many issues. We'll be moving to 2.1 soon. Sean Cribbs ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Git repository refactoring and Status update
Sean Cribbs wrote: > The Radiant git repository has been refactored! All of the existing > code has been added to a new, neutral, 'radiant' user on github. Please > update your watches and remove your forks of > github.com/seancribbs/radiant -- it will be disappearing soon. I will > do my best to incorporate existing pull requests into the new > repositories. Great work, Sean! I'm looking forward to the extension registry. - Dave -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Event organizing extension for Radiant
aslak hellesoy wrote: Hi Radiant community! I've been working on a Rails app for event/conference organisation - similar in goals to meetup.com, except I want it to be more like a customisable site for conference organisers. It's called Ba and lives here: http://gitorious.org/projects/ba Currently it lets you set up new events (happenings/conferences), sign up users, submit talk proposals, administer fees and promotion codes etc. I'll be adding more admin stuff like set up a program, reject/approve talks, billing etc. What I have not implemented yet is the ability to tweak the layout, add custom pages with semi-static content etc, and it's while researching how to do this that I finally decided to check out Radiant for real. My first impression with Radiant is great documentation and, great community and great code. I still haven't set it up, but will soon (tonight probably). So here is my question to you folks: Would it make sense to refactor Ba (currently a standalone Rails app) to be a Radiant extension for conference/event organisation? Would anyone else be interested in using this? (provided I make it general and useful enough). Even if noone else would use it, do you think it would make sense for me given I want to use Radiant for the CMS parts? We're talking around 10 models and controllers in addition to the Radiant ones, so it would be a fairly big extension. Another thing - I'm currently on Rails edge. Should I downgrade, or is it safe to assume that Radiant will run ok on Rails edge? Cheers, Aslak Hi Aslak This sounds great! It would be good if it were an extension :) Cheers, Mohit. 6/23/2008 | 11:28 PM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: [ANN] Summer Reboot Documentation
Mohit Sindhwani wrote: > We have been in discussion about starting up another effort to write up > Radiant documentation. I had earlier posted out something like a Table > of Contents that we could use as a preliminary outline. I've created > this on the wiki as 'Summer Reboot' (in honour of the thread that > started this push again!) and it's online at: > http://wiki.radiantcms.org/Summer_Reboot Thanks Mohit, this looks great. I tagged a few articles for myself, added a list item for the built-in Archive extension, and added a paragraph to the page intro about claiming articles with your initials. - Dave -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Event organizing extension for Radiant
> Would it make sense to refactor Ba (currently a standalone Rails app) > to be a Radiant extension for conference/event organisation? Would > anyone else be interested in using this? (provided I make it general > and useful enough). Even if noone else would use it, do you think it > would make sense for me given I want to use Radiant for the CMS parts? > We're talking around 10 models and controllers in addition to the > Radiant ones, so it would be a fairly big extension. Hi Aslak, I use Radiant to run the Boulder Ruby, a local Ruby users group. I've got a lightweight event extension that I use to associate pages with dates. Some of what you're proposing could be of use to what I'm doing and other general online communities that organize content around events. I'd be curious to see what the extension looks like and see how groups like mine could use it. Cheers, Marty ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Event organizing extension for Radiant
On Mon, Jun 23, 2008 at 5:35 PM, Marty Haught <[EMAIL PROTECTED]> wrote: >> Would it make sense to refactor Ba (currently a standalone Rails app) >> to be a Radiant extension for conference/event organisation? Would >> anyone else be interested in using this? (provided I make it general >> and useful enough). Even if noone else would use it, do you think it >> would make sense for me given I want to use Radiant for the CMS parts? >> We're talking around 10 models and controllers in addition to the >> Radiant ones, so it would be a fairly big extension. > > Hi Aslak, > > I use Radiant to run the Boulder Ruby, a local Ruby users group. I've > got a lightweight event extension that I use to associate pages with > dates. Some of what you're proposing could be of use to what I'm > doing and other general online communities that organize content > around events. I'd be curious to see what the extension looks like > and see how groups like mine could use it. > That's awesome Marty, Our conference registration open on August 10 (http://smidig2008.no), so if the Radiant extensification goes well, it should be ready by then. Just keep an eye on the Gitorious project. Cheers, Aslak > Cheers, > Marty > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: [ANN] Summer Reboot Documentation
David Piehler wrote: Mohit Sindhwani wrote: We have been in discussion about starting up another effort to write up Radiant documentation. I had earlier posted out something like a Table of Contents that we could use as a preliminary outline. I've created this on the wiki as 'Summer Reboot' (in honour of the thread that started this push again!) and it's online at: http://wiki.radiantcms.org/Summer_Reboot Thanks Mohit, this looks great. I tagged a few articles for myself, added a list item for the built-in Archive extension, and added a paragraph to the page intro about claiming articles with your initials. - Dave Thanks Dave, for filling in the gaps for me :) I love wikis :) Cheers, Mohit. 6/23/2008 | 11:46 PM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Two Slightly related Questions
John W. Long wrote: > On Jun 22, 2008, at 8:00 AM, Mohit Sindhwani wrote: >> 1. How can I add pictures to the wiki? I want to add screenshots to >> the Summer Reboot documentation. > > You will need to post the screenshots on another Web site to do this. > A tool like Flickr or Skitch could be used for this. Mohit, we should think about setting-up a Flickr account and migrating over screenshots so they aren't scattered around our personal/business websites. - Dave -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Bootstrapping problem
Hi again, I just pulled the code from Github, copied config/database.sqlite.yml to config/database.yml, cd into radiant/radiant and ran rake development db:bootstrap It fails with: SQLite3::SQLException: no such table: pages: SELECT DISTINCT class_name AS klass_name FROM pages WHERE class_name <> '' AND class_name IS NOT NULL I've seen similar errors mentioned in a couple of older threads, but nothing helped me. It seems several model classes are referenced while the db:bootstrap task is running, but I have an empty database. Seems like a catch 22 to me. Is there a simple workaround? Here is the full trace: C:\scm\radiant\radiant>rake development db:bootstrap --trace (in C:/scm/radiant/radiant) ** Invoke development (first_time) ** Execute development ** Invoke environment (first_time) ** Execute environment rake aborted! SQLite3::SQLException: no such table: pages: SELECT DISTINCT class_name AS klass_name FROM pages WHERE class_name <> '' AND class_name IS NOT NULL C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract_adapter.rb:150:in `log' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:132:in `execute' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:345:in `catch_schema_changes' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:132:in `execute' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:256:in `select' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:7:in `select_all_without_query_cache C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:55:in `select_all' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/base.rb:532:in `find_by_sql' C:/scm/radiant/radiant/app/models/page.rb:191:in `load_subclasses' C:/scm/radiant/radiant/app/models/page.rb:279 C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:203:in `load_without_new_constant_marking' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:203:in `load_file' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:342:in `new_constants_in' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:202:in `load_file' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:94:in `require_or_load' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:248:in `load_missing_constant' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:453:in `const_missing' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:465:in `const_missing' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:260:in `load_missing_constant' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:469:in `const_missing' C:/scm/radiant/radiant/app/models/user_action_observer.rb:2 C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:203:in `load_without_new_constant_marking' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:203:in `load_file' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:342:in `new_constants_in' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:202:in `load_file' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:94:in `require_or_load' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:248:in `load_missing_constant' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:453:in `const_missing' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:465:in `const_missing' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/inflector.rb:257:in `constantize' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/core_ext/string/inflections.rb:148:in `constantize' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/observer.rb:38:in `instantiate_observers' C:/scm/radiant/radiant/vendor/rails/activerec
Re: [Radiant] Bootstrapping problem
I've had good results with Radiant, SQLite3 and Mac 10.5 "just working" so if that's a possibility it might save you some effort. On 2008/06/23, at 10:19, aslak hellesoy wrote: Hi again, I just pulled the code from Github, copied config/database.sqlite.yml to config/database.yml, cd into radiant/radiant and ran rake development db:bootstrap It fails with: SQLite3::SQLException: no such table: pages: SELECT DISTINCT class_name AS klass_name FROM pages WHERE class_name <> '' AND class_name IS NOT NULL I've seen similar errors mentioned in a couple of older threads, but nothing helped me. It seems several model classes are referenced while the db:bootstrap task is running, but I have an empty database. Seems like a catch 22 to me. Is there a simple workaround? Here is the full trace: C:\scm\radiant\radiant>rake development db:bootstrap --trace (in C:/scm/radiant/radiant) ** Invoke development (first_time) ** Execute development ** Invoke environment (first_time) ** Execute environment rake aborted! SQLite3::SQLException: no such table: pages: SELECT DISTINCT class_name AS klass_name FROM pages WHERE class_name <> '' AND class_name IS NOT NULL C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ connection_adapters/abstract_adapter.rb:150:in `log' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ connection_adapters/sqlite_adapter.rb:132:in `execute' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ connection_adapters/sqlite_adapter.rb:345:in `catch_schema_changes' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ connection_adapters/sqlite_adapter.rb:132:in `execute' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ connection_adapters/sqlite_adapter.rb:256:in `select' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ connection_adapters/abstract/database_statements.rb:7:in `select_all_without_query_cache C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ connection_adapters/abstract/query_cache.rb:55:in `select_all' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ base.rb:532:in `find_by_sql' C:/scm/radiant/radiant/app/models/page.rb:191:in `load_subclasses' C:/scm/radiant/radiant/app/models/page.rb:279 C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:203:in `load_without_new_constant_marking' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:203:in `load_file' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:342:in `new_constants_in' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:202:in `load_file' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:94:in `require_or_load' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:248:in `load_missing_constant' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:453:in `const_missing' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:465:in `const_missing' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:260:in `load_missing_constant' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:469:in `const_missing' C:/scm/radiant/radiant/app/models/user_action_observer.rb:2 C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:203:in `load_without_new_constant_marking' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:203:in `load_file' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:342:in `new_constants_in' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:202:in `load_file' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:94:in `require_or_load' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:248:in `load_missing_constant' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:453:in `const_missing' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:465:in `const_missing' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/inflector.rb:257:in `constantize' C:/scm/radiant/radiant/vendor/rail
Re: [Radiant] Re: crashes with recently released ruby (1.8.6p230)
Apparently the Phusion guys have backported the security fixes to 1.8.6-p111 in their Ruby Enterprise edition. Might be worth checking out if you're stuck between security issues and a broken ruby. http://blog.phusion.nl/2008/06/23/ruby-186-p230187-broke-your-app-ruby-enterprise-edition-to-the-rescue/ On 2008/06/22, at 23:58, James Blanding wrote: Mohit Sindhwani wrote: [...] James, I read on the Ruby mailing list that the new version breaks Rails. Cheers, Mohit. 6/23/2008 | 1:30 PM. Ah, I see you're right. I had thought it was Radiant-specific because my two sites that don't run Radiant seemed to load fine. I did not test any further than the front pages, however. Perhaps if I had clicked around, those apps would have also gone down. Oh well, hopefully things will be fixed soon. Thanks, --James -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Patch to add a defauls.page.filter config
I sent a pull request to the GitHub "radiant" user, but I'm not sure that goes anywhere just yet. I have whipped up a quick and simple patch to allow you set a default filter for pages. On a freshly bootsrapped intance, you will see a new value on the config table named "defaults.page.filter". Its blank by default. Setting that to any one of: * Textile * Markdown * SmartyPants Will cause all new pages to have that filter selected by default. Handy. Anyone else want to +1 this if they find it useful? http://github.com/Squeegy/radiant/commit/318687e9be167f5b6549a28557ea039bd4651241 -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Patch to add a defauls.page.filter config
+1 On Jun 23, 2008, at 1:29 PM, Alex Wayne wrote: I sent a pull request to the GitHub "radiant" user, but I'm not sure that goes anywhere just yet. I have whipped up a quick and simple patch to allow you set a default filter for pages. On a freshly bootsrapped intance, you will see a new value on the config table named "defaults.page.filter". Its blank by default. Setting that to any one of: * Textile * Markdown * SmartyPants Will cause all new pages to have that filter selected by default. Handy. Anyone else want to +1 this if they find it useful? http://github.com/Squeegy/radiant/commit/318687e9be167f5b6549a28557ea039bd4651241 -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Re: crashes with recently released ruby (1.8.6p230)
john muhl wrote: > Apparently the Phusion guys have backported the security fixes to > 1.8.6-p111 in their Ruby Enterprise edition. Might be worth checking > out if you're stuck between security issues and a broken ruby. > > http://blog.phusion.nl/2008/06/23/ruby-186-p230187-broke-your-app-ruby-enterprise-edition-to-the-rescue/ Looks like they are trying to take these fixes and make an unofficial 1.8.6 patch: http://www.ruby-forum.com/topic/157034 - Dave -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Patch to add a defauls.page.filter config
Alex Wayne wrote: > I have whipped up a quick and simple patch to allow you set a default > filter for pages. On a freshly bootsrapped intance, you will see a new > value on the config table named "defaults.page.filter". +1 -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Patch to add a defauls.page.filter config
Alex (et al), Pull requests to the 'radiant' user will go to me for now, through an email alias. They tell me they will have "group" accounts soon, primarily for the open-source projects. In the meantime you can send pull requests to any of: * radiant * seancribbs * jlong * jfrench * mislav * lorenjohnson * aiwilliams Sean Alex Wayne wrote: I sent a pull request to the GitHub "radiant" user, but I'm not sure that goes anywhere just yet. I have whipped up a quick and simple patch to allow you set a default filter for pages. On a freshly bootsrapped intance, you will see a new value on the config table named "defaults.page.filter". Its blank by default. Setting that to any one of: * Textile * Markdown * SmartyPants Will cause all new pages to have that filter selected by default. Handy. Anyone else want to +1 this if they find it useful? http://github.com/Squeegy/radiant/commit/318687e9be167f5b6549a28557ea039bd4651241 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Git repository refactoring and Status update
On Mon, Jun 23, 2008 at 5:12 PM, David Piehler <[EMAIL PROTECTED]> wrote: > Sean Cribbs wrote: >> The Radiant git repository has been refactored! All of the existing >> code has been added to a new, neutral, 'radiant' user on github. Please >> update your watches and remove your forks of >> github.com/seancribbs/radiant -- it will be disappearing soon. I will >> do my best to incorporate existing pull requests into the new >> repositories. > http://github.com/radiant/radiant/tree/master seems to have been imported "raw" (without the git history). It would be nice if the svn history was kept intact. I suppose the plan is to have all the Radiant subprojects in separate Git repos from now on. To my regret it seems like they have all been imported without git-svn. In my opinion, the initial import to http://github.com/seancribbs/radiant/tree/master got it right. It seems to have been imported with git-svn. Is there any particular reason why git-svn has (apparently) not been used in the migration of the other radiant git repos? Cheers, Aslak > Great work, Sean! I'm looking forward to the extension registry. > > - Dave > > > -- > Posted via http://www.ruby-forum.com/. > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Git repository refactoring and Status update
On Tue, Jun 24, 2008 at 1:10 AM, aslak hellesoy <[EMAIL PROTECTED]> wrote: > On Mon, Jun 23, 2008 at 5:12 PM, David Piehler <[EMAIL PROTECTED]> wrote: >> Sean Cribbs wrote: >>> The Radiant git repository has been refactored! All of the existing >>> code has been added to a new, neutral, 'radiant' user on github. Please >>> update your watches and remove your forks of >>> github.com/seancribbs/radiant -- it will be disappearing soon. I will >>> do my best to incorporate existing pull requests into the new >>> repositories. >> > > http://github.com/radiant/radiant/tree/master seems to have been > imported "raw" (without the git history). It would be nice if the svn > history was kept intact. > One more recommendation: Git has a feature akin to svn:externals called Git submodule that lets you "symlink" other Git repos. Have you considered using this feature for the stuff under vendor and vendor/plugins? A lot of the stuff that is there is already at Github, and the stuff that isn't should be quick to clone up to Github/Gitorious. I think that in the long run it's better to use Git submodule than keeping hard forks of the various libraries. Cheers, Aslak > I suppose the plan is to have all the Radiant subprojects in separate > Git repos from now on. To my regret it seems like they have all been > imported without git-svn. > > In my opinion, the initial import to > http://github.com/seancribbs/radiant/tree/master got it right. It > seems to have been imported with git-svn. > > Is there any particular reason why git-svn has (apparently) not been > used in the migration of the other radiant git repos? > > Cheers, > Aslak > >> Great work, Sean! I'm looking forward to the extension registry. >> >> - Dave >> >> >> -- >> Posted via http://www.ruby-forum.com/. >> ___ >> Radiant mailing list >> Post: Radiant@radiantcms.org >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant >> > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Git repository refactoring and Status update
On Jun 23, 2008, at 4:10 PM, aslak hellesoy wrote: On Mon, Jun 23, 2008 at 5:12 PM, David Piehler <[EMAIL PROTECTED]> wrote: Sean Cribbs wrote: The Radiant git repository has been refactored! All of the existing code has been added to a new, neutral, 'radiant' user on github. Please update your watches and remove your forks of github.com/seancribbs/radiant -- it will be disappearing soon. I will do my best to incorporate existing pull requests into the new repositories. http://github.com/radiant/radiant/tree/master seems to have been imported "raw" (without the git history). It would be nice if the svn history was kept intact. I suppose the plan is to have all the Radiant subprojects in separate Git repos from now on. To my regret it seems like they have all been imported without git-svn. In my opinion, the initial import to http://github.com/seancribbs/radiant/tree/master got it right. It seems to have been imported with git-svn. Is there any particular reason why git-svn has (apparently) not been used in the migration of the other radiant git repos? Cheers, Aslak My guess is because they no longer follow the same structure they used to. It wouldn't make sense to have a history duplicated of a huge number of commits that don't even apply to the sliver of code that not exists in its own repo. -Alex http://beautifulpixel.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Git repository refactoring and Status update
Aslak, git-svn doesn't play nicely when you have other remote git repositories, as I found multiple times when trying to keep the old SVN up-to-date. At the time I created the new repos, SVN was out of date, and so it was not prudent to import from that. I may go back and recreate the main radiant repository from the older git repo, gaining all of its inherited SVN and git history. However, doing that for some 23 repositories is not my idea of fun. Sean aslak hellesoy wrote: On Mon, Jun 23, 2008 at 5:12 PM, David Piehler <[EMAIL PROTECTED]> wrote: Sean Cribbs wrote: The Radiant git repository has been refactored! All of the existing code has been added to a new, neutral, 'radiant' user on github. Please update your watches and remove your forks of github.com/seancribbs/radiant -- it will be disappearing soon. I will do my best to incorporate existing pull requests into the new repositories. http://github.com/radiant/radiant/tree/master seems to have been imported "raw" (without the git history). It would be nice if the svn history was kept intact. I suppose the plan is to have all the Radiant subprojects in separate Git repos from now on. To my regret it seems like they have all been imported without git-svn. In my opinion, the initial import to http://github.com/seancribbs/radiant/tree/master got it right. It seems to have been imported with git-svn. Is there any particular reason why git-svn has (apparently) not been used in the migration of the other radiant git repos? Cheers, Aslak Great work, Sean! I'm looking forward to the extension registry. - Dave -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Bootstrapping problem
On Mon, Jun 23, 2008 at 6:45 PM, john muhl <[EMAIL PROTECTED]> wrote: > I've had good results with Radiant, SQLite3 and Mac 10.5 "just working" so > if that's a possibility it might save you some effort. > Bootstrapping on OS X 10.4 (I doubt the OS version is relevant) and ruby 1.8.6 (2007-09-24 patchlevel 111) [i686-darwin8.11.1] fails too: aslak-hellesoys-computer-2:~/scm/radiant aslakhellesoy$ rake development db:bootstrap (in /Users/aslakhellesoy/scm/radiant) rake aborted! SQLite3::SQLException: no such table: pages: SELECT DISTINCT class_name AS klass_name FROM pages WHERE class_name <> '' AND class_name IS NOT NULL (similar trace) Is there any known way to prevent the bootstrapping task from loading AR classes that don't yet have their tables created? Aslak > On 2008/06/23, at 10:19, aslak hellesoy wrote: > >> Hi again, >> >> I just pulled the code from Github, copied config/database.sqlite.yml >> to config/database.yml, cd into radiant/radiant and ran rake >> development db:bootstrap >> >> It fails with: >> >> SQLite3::SQLException: no such table: pages: SELECT DISTINCT >> class_name AS klass_name FROM pages WHERE class_name <> '' AND >> class_name IS NOT NULL >> >> I've seen similar errors mentioned in a couple of older threads, but >> nothing helped me. It seems several model classes are referenced while >> the db:bootstrap task is running, but I have an empty database. Seems >> like a catch 22 to me. Is there a simple workaround? Here is the full >> trace: >> >> C:\scm\radiant\radiant>rake development db:bootstrap --trace >> (in C:/scm/radiant/radiant) >> ** Invoke development (first_time) >> ** Execute development >> ** Invoke environment (first_time) >> ** Execute environment >> rake aborted! >> SQLite3::SQLException: no such table: pages: SELECT DISTINCT >> class_name AS klass_name FROM pages WHERE class_name <> '' AND >> class_name IS NOT NULL >> >> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract_adapter.rb:150:in >> `log' >> >> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:132:in >> `execute' >> >> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:345:in >> `catch_schema_changes' >> >> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:132:in >> `execute' >> >> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:256:in >> `select' >> >> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:7:in >> `select_all_without_query_cache >> >> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:55:in >> `select_all' >> >> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/base.rb:532:in >> `find_by_sql' >> C:/scm/radiant/radiant/app/models/page.rb:191:in `load_subclasses' >> C:/scm/radiant/radiant/app/models/page.rb:279 >> >> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:203:in >> `load_without_new_constant_marking' >> >> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:203:in >> `load_file' >> >> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:342:in >> `new_constants_in' >> >> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:202:in >> `load_file' >> >> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:94:in >> `require_or_load' >> >> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:248:in >> `load_missing_constant' >> >> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:453:in >> `const_missing' >> >> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:465:in >> `const_missing' >> >> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:260:in >> `load_missing_constant' >> >> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:469:in >> `const_missing' >> C:/scm/radiant/radiant/app/models/user_action_observer.rb:2 >> >> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:203:in >> `load_without_new_constant_marking' >> >> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:203:in >> `load_file' >> >> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:342:i
Re: [Radiant] Re: Git repository refactoring and Status update
aslak hellesoy wrote: One more recommendation: Git has a feature akin to svn:externals called Git submodule that lets you "symlink" other Git repos. Have you considered using this feature for the stuff under vendor and vendor/plugins? A lot of the stuff that is there is already at Github, and the stuff that isn't should be quick to clone up to Github/Gitorious. I think that in the long run it's better to use Git submodule than keeping hard forks of the various libraries. I'll give that some thought and toss it around with the other committers. However, it may suffer the same weaknesses as svn:externals, which is dependency on the availability of those other repositories, which I don't like much. Sean ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Bootstrapping problem
I have seen this running edge radiant. I just removed vendor/radiant then bootstrapped, then put it back in. I'm sure this is a bug. You shouldn't need the database table to be present in order to bootstrap. -Alex http://beautifulpixel.com On Jun 23, 2008, at 4:22 PM, aslak hellesoy wrote: On Mon, Jun 23, 2008 at 6:45 PM, john muhl <[EMAIL PROTECTED]> wrote: I've had good results with Radiant, SQLite3 and Mac 10.5 "just working" so if that's a possibility it might save you some effort. Bootstrapping on OS X 10.4 (I doubt the OS version is relevant) and ruby 1.8.6 (2007-09-24 patchlevel 111) [i686-darwin8.11.1] fails too: aslak-hellesoys-computer-2:~/scm/radiant aslakhellesoy$ rake development db:bootstrap (in /Users/aslakhellesoy/scm/radiant) rake aborted! SQLite3::SQLException: no such table: pages: SELECT DISTINCT class_name AS klass_name FROM pages WHERE class_name <> '' AND class_name IS NOT NULL (similar trace) Is there any known way to prevent the bootstrapping task from loading AR classes that don't yet have their tables created? Aslak On 2008/06/23, at 10:19, aslak hellesoy wrote: Hi again, I just pulled the code from Github, copied config/ database.sqlite.yml to config/database.yml, cd into radiant/radiant and ran rake development db:bootstrap It fails with: SQLite3::SQLException: no such table: pages: SELECT DISTINCT class_name AS klass_name FROM pages WHERE class_name <> '' AND class_name IS NOT NULL I've seen similar errors mentioned in a couple of older threads, but nothing helped me. It seems several model classes are referenced while the db:bootstrap task is running, but I have an empty database. Seems like a catch 22 to me. Is there a simple workaround? Here is the full trace: C:\scm\radiant\radiant>rake development db:bootstrap --trace (in C:/scm/radiant/radiant) ** Invoke development (first_time) ** Execute development ** Invoke environment (first_time) ** Execute environment rake aborted! SQLite3::SQLException: no such table: pages: SELECT DISTINCT class_name AS klass_name FROM pages WHERE class_name <> '' AND class_name IS NOT NULL C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ connection_adapters/abstract_adapter.rb:150:in `log' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ connection_adapters/sqlite_adapter.rb:132:in `execute' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ connection_adapters/sqlite_adapter.rb:345:in `catch_schema_changes' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ connection_adapters/sqlite_adapter.rb:132:in `execute' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ connection_adapters/sqlite_adapter.rb:256:in `select' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ connection_adapters/abstract/database_statements.rb:7:in `select_all_without_query_cache C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ connection_adapters/abstract/query_cache.rb:55:in `select_all' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ base.rb:532:in `find_by_sql' C:/scm/radiant/radiant/app/models/page.rb:191:in `load_subclasses' C:/scm/radiant/radiant/app/models/page.rb:279 C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:203:in `load_without_new_constant_marking' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:203:in `load_file' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:342:in `new_constants_in' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:202:in `load_file' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:94:in `require_or_load' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:248:in `load_missing_constant' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:453:in `const_missing' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:465:in `const_missing' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:260:in `load_missing_constant' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:469:in `const_missing' C:/scm/radiant/radiant/app/models/user_action_observer.rb:2 C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:203:in `load_without_new_constant_marking' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:203:in `load_fi
Re: [Radiant] Bootstrapping problem
On Tue, Jun 24, 2008 at 1:22 AM, aslak hellesoy <[EMAIL PROTECTED]> wrote: > On Mon, Jun 23, 2008 at 6:45 PM, john muhl <[EMAIL PROTECTED]> wrote: >> I've had good results with Radiant, SQLite3 and Mac 10.5 "just working" so >> if that's a possibility it might save you some effort. >> > > Bootstrapping on OS X 10.4 (I doubt the OS version is relevant) and > ruby 1.8.6 (2007-09-24 patchlevel 111) [i686-darwin8.11.1] fails too: > > aslak-hellesoys-computer-2:~/scm/radiant aslakhellesoy$ rake > development db:bootstrap > (in /Users/aslakhellesoy/scm/radiant) > rake aborted! > SQLite3::SQLException: no such table: pages: SELECT DISTINCT > class_name AS klass_name FROM pages WHERE class_name <> '' AND > class_name IS NOT NULL > > (similar trace) > > Is there any known way to prevent the bootstrapping task from loading > AR classes that don't yet have their tables created? > OK, I found a workaround. Comment out the last line in app/models/page.rb when you run db:bootstrap for the first time: #Page.load_subclasses This statement should probably be run from a place that isn't triggered by the bootstrap task. I'm not familiar enough with the code to suggest an alternative place... Cheers, Aslak > Aslak > >> On 2008/06/23, at 10:19, aslak hellesoy wrote: >> >>> Hi again, >>> >>> I just pulled the code from Github, copied config/database.sqlite.yml >>> to config/database.yml, cd into radiant/radiant and ran rake >>> development db:bootstrap >>> >>> It fails with: >>> >>> SQLite3::SQLException: no such table: pages: SELECT DISTINCT >>> class_name AS klass_name FROM pages WHERE class_name <> '' AND >>> class_name IS NOT NULL >>> >>> I've seen similar errors mentioned in a couple of older threads, but >>> nothing helped me. It seems several model classes are referenced while >>> the db:bootstrap task is running, but I have an empty database. Seems >>> like a catch 22 to me. Is there a simple workaround? Here is the full >>> trace: >>> >>> C:\scm\radiant\radiant>rake development db:bootstrap --trace >>> (in C:/scm/radiant/radiant) >>> ** Invoke development (first_time) >>> ** Execute development >>> ** Invoke environment (first_time) >>> ** Execute environment >>> rake aborted! >>> SQLite3::SQLException: no such table: pages: SELECT DISTINCT >>> class_name AS klass_name FROM pages WHERE class_name <> '' AND >>> class_name IS NOT NULL >>> >>> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract_adapter.rb:150:in >>> `log' >>> >>> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:132:in >>> `execute' >>> >>> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:345:in >>> `catch_schema_changes' >>> >>> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:132:in >>> `execute' >>> >>> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:256:in >>> `select' >>> >>> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:7:in >>> `select_all_without_query_cache >>> >>> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:55:in >>> `select_all' >>> >>> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/base.rb:532:in >>> `find_by_sql' >>> C:/scm/radiant/radiant/app/models/page.rb:191:in `load_subclasses' >>> C:/scm/radiant/radiant/app/models/page.rb:279 >>> >>> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:203:in >>> `load_without_new_constant_marking' >>> >>> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:203:in >>> `load_file' >>> >>> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:342:in >>> `new_constants_in' >>> >>> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:202:in >>> `load_file' >>> >>> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:94:in >>> `require_or_load' >>> >>> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:248:in >>> `load_missing_constant' >>> >>> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:453:in >>> `const_missing' >>> >>> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:465:in >>> `const_missing' >>> >>> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:260:in >>> `load_missing_constant' >>> >>> C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_su
Re: [Radiant] Re: Git repository refactoring and Status update
On Tue, Jun 24, 2008 at 1:21 AM, Sean Cribbs <[EMAIL PROTECTED]> wrote: > Aslak, > > git-svn doesn't play nicely when you have other remote git repositories, as > I found multiple times when trying to keep the old SVN up-to-date. At the > time I created the new repos, SVN was out of date, and so it was not prudent > to import from that. I may go back and recreate the main radiant repository > from the older git repo, gaining all of its inherited SVN and git history. > However, doing that for some 23 repositories is not my idea of fun. > Understood. SCM history is overrated anyway :-) Aslak > Sean > > aslak hellesoy wrote: >> >> On Mon, Jun 23, 2008 at 5:12 PM, David Piehler <[EMAIL PROTECTED]> >> wrote: >> >>> >>> Sean Cribbs wrote: >>> The Radiant git repository has been refactored! All of the existing code has been added to a new, neutral, 'radiant' user on github. Please update your watches and remove your forks of github.com/seancribbs/radiant -- it will be disappearing soon. I will do my best to incorporate existing pull requests into the new repositories. >> >> http://github.com/radiant/radiant/tree/master seems to have been >> imported "raw" (without the git history). It would be nice if the svn >> history was kept intact. >> >> I suppose the plan is to have all the Radiant subprojects in separate >> Git repos from now on. To my regret it seems like they have all been >> imported without git-svn. >> >> In my opinion, the initial import to >> http://github.com/seancribbs/radiant/tree/master got it right. It >> seems to have been imported with git-svn. >> >> Is there any particular reason why git-svn has (apparently) not been >> used in the migration of the other radiant git repos? >> >> Cheers, >> Aslak >> >> >>> >>> Great work, Sean! I'm looking forward to the extension registry. >>> >>> - Dave >>> >>> >>> -- >>> Posted via http://www.ruby-forum.com/. >>> ___ >>> Radiant mailing list >>> Post: Radiant@radiantcms.org >>> Search: http://radiantcms.org/mailing-list/search/ >>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant >>> >>> >> >> ___ >> Radiant mailing list >> Post: Radiant@radiantcms.org >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant >> >> > > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Git repository refactoring and Status update
On Tue, Jun 24, 2008 at 1:23 AM, Sean Cribbs <[EMAIL PROTECTED]> wrote: > aslak hellesoy wrote: >> >> One more recommendation: Git has a feature akin to svn:externals >> called Git submodule that lets you "symlink" other Git repos. Have you >> considered using this feature for the stuff under vendor and >> vendor/plugins? A lot of the stuff that is there is already at Github, >> and the stuff that isn't should be quick to clone up to >> Github/Gitorious. I think that in the long run it's better to use Git >> submodule than keeping hard forks of the various libraries. >> > > I'll give that some thought and toss it around with the other committers. > However, it may suffer the same weaknesses as svn:externals, which is > dependency on the availability of those other repositories, which I don't > like much. > True, but as long as everything is hosted at the same host (Github) - if one repo is available, so will the others. Aslak > Sean > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Bootstrapping problem
OK, I found a workaround. Comment out the last line in app/models/page.rb when you run db:bootstrap for the first time: #Page.load_subclasses This statement should probably be run from a place that isn't triggered by the bootstrap task. I'm not familiar enough with the code to suggest an alternative place... Cheers, Aslak This is related to a change made to handle when you are upgrading a site and not all of the extensions (i.e. other Page subclasses) are available. Essentially it creates those missing classes so that you can start up the site and change or modify them as necessary. I'm working on a fix as I write this. Sean ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Bootstrapping problem
http://github.com/radiant/radiant/commit/20d8f44d45f11a0e28231fdf86ded522ed927f6d Cheers, Sean aslak hellesoy wrote: On Tue, Jun 24, 2008 at 1:22 AM, aslak hellesoy <[EMAIL PROTECTED]> wrote: On Mon, Jun 23, 2008 at 6:45 PM, john muhl <[EMAIL PROTECTED]> wrote: I've had good results with Radiant, SQLite3 and Mac 10.5 "just working" so if that's a possibility it might save you some effort. Bootstrapping on OS X 10.4 (I doubt the OS version is relevant) and ruby 1.8.6 (2007-09-24 patchlevel 111) [i686-darwin8.11.1] fails too: aslak-hellesoys-computer-2:~/scm/radiant aslakhellesoy$ rake development db:bootstrap (in /Users/aslakhellesoy/scm/radiant) rake aborted! SQLite3::SQLException: no such table: pages: SELECT DISTINCT class_name AS klass_name FROM pages WHERE class_name <> '' AND class_name IS NOT NULL (similar trace) Is there any known way to prevent the bootstrapping task from loading AR classes that don't yet have their tables created? OK, I found a workaround. Comment out the last line in app/models/page.rb when you run db:bootstrap for the first time: #Page.load_subclasses This statement should probably be run from a place that isn't triggered by the bootstrap task. I'm not familiar enough with the code to suggest an alternative place... Cheers, Aslak Aslak On 2008/06/23, at 10:19, aslak hellesoy wrote: Hi again, I just pulled the code from Github, copied config/database.sqlite.yml to config/database.yml, cd into radiant/radiant and ran rake development db:bootstrap It fails with: SQLite3::SQLException: no such table: pages: SELECT DISTINCT class_name AS klass_name FROM pages WHERE class_name <> '' AND class_name IS NOT NULL I've seen similar errors mentioned in a couple of older threads, but nothing helped me. It seems several model classes are referenced while the db:bootstrap task is running, but I have an empty database. Seems like a catch 22 to me. Is there a simple workaround? Here is the full trace: C:\scm\radiant\radiant>rake development db:bootstrap --trace (in C:/scm/radiant/radiant) ** Invoke development (first_time) ** Execute development ** Invoke environment (first_time) ** Execute environment rake aborted! SQLite3::SQLException: no such table: pages: SELECT DISTINCT class_name AS klass_name FROM pages WHERE class_name <> '' AND class_name IS NOT NULL C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract_adapter.rb:150:in `log' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:132:in `execute' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:345:in `catch_schema_changes' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:132:in `execute' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/sqlite_adapter.rb:256:in `select' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:7:in `select_all_without_query_cache C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:55:in `select_all' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/base.rb:532:in `find_by_sql' C:/scm/radiant/radiant/app/models/page.rb:191:in `load_subclasses' C:/scm/radiant/radiant/app/models/page.rb:279 C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:203:in `load_without_new_constant_marking' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:203:in `load_file' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:342:in `new_constants_in' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:202:in `load_file' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:94:in `require_or_load' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:248:in `load_missing_constant' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:453:in `const_missing' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:465:in `const_missing' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:260:in `load_missing_constant' C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:469:in `const_missing' C:/scm/radiant/radiant/app/models/user_action_observer.rb:2 C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../activesupport/lib/active_sup
[Radiant] Odd Behavior During Testing
I'm completely lost here. Can anyone shed some light on this? In the SnS extension I have created the following... In styles_n_scripts_extension.rb (activate method): SiteController.send :include, SiteControllerExtensions In the /lib/site_controller_extensions.rb file: module SiteControllerExtensions; end (Yes, it's empty. I stripped everything out trying to debug) In the failing spec (describing SiteController): it "should render an existing page" do get :show_page, :url => '/' response.body.should == "Hello World!" end Apparently, the SiteController also mixes-in the login_system which creates its own before_filter that calls the #authenticate method. This method, in turn, calls no_login_required? SiteController *should* respond 'true' -- that no login is required. But here's where it gets weird... If I comment out my include line (the one in the extension's activate method above) SiteController does, indeed respond 'true' to no_login_required? But, the minute I add in that include and mix in my extensions -- even with *nothing* in my mixed-in module -- SiteController starts responding 'false' -- that login is required. My spec'ed get request then returns a redirect to the login page. This only happens when running specs. Testing with a server in development mode works fine. Thoughts anyone? -Chris ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Summer Reboot Documentation
On 22 Jun 2008, at 09:17, Mohit Sindhwani wrote: Hi Guys We have been in discussion about starting up another effort to write up Radiant documentation. I had earlier posted out something like a Table of Contents that we could use as a preliminary outline. I've created this on the wiki as 'Summer Reboot' (in honour of the thread that started this push again!) and it's online at: http://wiki.radiantcms.org/Summer_Reboot I've also created a section on the page called 'Author Abbreviations' - just put your name there with an abbreviation. Then, you can use the abbreviation to claim certain articles as your own :) I've just added my name and claimed a few articles. I'd like to write an introductory piece on Radius tags. Cheers, Drew ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
