Re: [Radiant] Page Parts extension - Passenger failing
Just spotted that I'm getting the following error when creating a page using your file page part example. can't modify frozen hash Is this a problem in Production mode as well? Hi John, I can't reproduce this in either development or production. I tested this with the Radiant RC2 and Paperclip 2.3.1.1 gems, with just Factory + Parts installed and the file part as shown in the screencast -- anything different on your end? Interesting that something is calling `delete` when you're creating a page, looks like the transaction is getting rolled back for some reason; not sure if that's the cause or the effect of your error though. Even when I explicitly triggered validation errors on the file attachment or the page itself I couldn't duplicate your issue. j ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] Generic CRUD extension (John Polling)
I'm currently having to write a series of extensions for a new site I'm working on. All they are is a series of simple CRUD extensions and very repetitive. I was just wondering if there was a plugin that would cut out on this repetition? Radiant has its own CRUD controller, Admin::ResourceController. Depending on your needs you might be able to inherit from this, adjusting the authentication logic to suit. See the Snippets and Layouts controllers for two simple implementations. j ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] Page Parts extension - Passenger failing
Hi John, There are no configuration options for either PageParts or PageFactory; rather, you've uncovered a couple load order/load path issues on my part. While I look into them, here's the awkward workaround: 1) Load PageParts before PageFactory by editing config/environment, eg: config.extensions = [:page_parts, :all] 2) Run Radiant in development mode, assuming you're not working on a live site at the moment. There's some difference between dev and production w/r/t dependency loading that I haven't tracked down yet. I'll post back when I've got these sorted. Thanks, j ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] Page Parts extension - Passenger failing
Hi John, Can you update your copy of PageParts and try again? I've just pushed a change which should hopefully solve both of those issues. Please let me know if it works for you or not. Best, j ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
[Radiant] Page Parts extension - Passenger failing
Thanks for looking into this so quickly. Will run an update first thing in the morning. Oops -- you'll have to update PageFactory as well. I believe that's the last of it. j ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
[Radiant] [ANN] RadiantCasts 11: PageFactory and PageParts Extensions
With a lot of help from Cristi Duma, RadiantCasts 11 is out: http://radiantcms.org/blog/archives/2010/05/03/radiantcasts-episode-11-radiant-page-parts-and-page-factory-extensions Episode 11 covers PageParts and PageFactory, two extensions for managing large sites and complex content. Your feedback is appreciated! Josh ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] Custom Fields
I'm looking at using the Custom Fields extension for some pages, for example pages with information about upcoming events. Each of these pages would have a custom field for start/end date, location, organizer, etc. Is there any way to create a template for these pages that would include the custom fields (maybe with default values)? I don't see how to do this with either the Stereotypes or Page Factory extensions. If you're on edge, PageParts + PageFactory might approximate what you're trying to do. PageParts would store those extra fields as parts, not in another association; so it might not be exactly what you're looking for. But right out of the box, PP + PF would let you do this: class EventPageFactory PageFactory::Base part Start Date, :page_part_type = DatePagePart part Organizer, :content = Default value goes here end I'm putting together a screencast on the two extensions, it should be posted in a few days. j ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] page factory css
oops. i meant that it's not included on the factory pages but is included on the main page list. That's correct. The CSS only styles the popup on the pages index, so I didn't include it on the new/edit screens. I should have time tomorrow to look at the other issues you filed on Github. Thanks for the feedback! j ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] Radiant Digest, Vol 49, Issue 27
There are still some things to be worked out with gems and UI regions I spotted your earlier mention of this and did some digging, but I haven't been able to find anything specifically wrong with the region set stuff. While I was investigating I did uncover a load-order issue, so I wonder if you weren't seeing this: http://github.com/radiant/radiant/issues#issue/109 Is there a case where just the region sets are failing? If we're moving towards the idea of Rails 3 embeddable apps, I would want to have all my migrations in one place, clearly organized, where I can understand what's going on. There's been a long-running discussion within Rails proper about engine migrations. This is lengthy, but fundamental reading for anyone pondering migrations: https://rails.lighthouseapp.com/projects/8994/tickets/2058-rake-tasks-for-run-engine-migrations#ticket-2058-22 This has implications for both Radiant and Spree's extension systems. Overall I like the pattern that's emerged from that thread: copy migrations from each extension, re-timestamp them to preserve the order of operations, put them in RAILS_ROOT/db/migrate. I think there are some unanswered questions, but consensus is that this is probably the most viable pattern. j ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] 0.9.0-rc1 experience (Marshal Linfoot)
Taking 0.9 out for a test drive... here's an overview of what worked and what didn't. Radiant: radiant r9 --database sqlite3 cd r9; rake production db:bootstrap Hi Marshal, Based on these error messages it sounds like you're not actually running 0.9. The latest gem is still Radiant 0.8.1. To check out edge: radiant r9 -d sqlite3 cd r9 rake radiant:freeze:edge rake radiant:update rake db:bootstrap That should fix most or all of your errors. j On Apr 18, 2010, at 1:00 PM, radiant-requ...@radiantcms.org wrote: Send Radiant mailing list submissions to radiant@radiantcms.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.radiantcms.org/mailman/listinfo/radiant or, via email, send a message with subject or body 'help' to radiant-requ...@radiantcms.org You can reach the person managing the list at radiant-ow...@radiantcms.org When replying, please edit your Subject line so it is more specific than Re: Contents of Radiant digest... Today's Topics: 1. Model Associations in Radiant? (Derek Yau) 2. 0.9.0-rc1 and settings extension (Marshal Linfoot) 3. 0.9.0-rc1 experience (Marshal Linfoot) -- Message: 1 Date: Sun, 18 Apr 2010 02:11:11 -0700 From: Derek Yau derek@gmail.com Subject: [Radiant] Model Associations in Radiant? To: radiant@radiantcms.org Message-ID: o2n5ed78ae71004180211m5b4cd82cq19b451ddb8a9b...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 Hi everyone, I'm a newer developer to both Radiant and Rails - first of all want to thank you all for making such an awesome CMS, its been a joy to work with so far and the extensions system in particular is genius and very well designed/implemented. I have a question however, related to Radiant and models which I'm hoping someone here can answer. To illustrate my point imagine I have two entities: 1. Speakers (lecturers/panelists/etc.) 2. Videos (videos of those speakers/panelists giving a lecture) What I need to do is be able to relate these two models in the following way: - Speaker belongs_to Video - Video has_many Speakers (eg. in the case of a panel discussion) Basically each Speaker will have his own page detailing things about the speaker (name/etc.), and subsequently each lecture will have its own Video page detailing things about the video (description/etc.) BUT each Video page will also contain a list of Speakers that are featured in that video. (This needs to reference the Speakers model) So far, I've gotten so far as to follow the Custom-Page-Type tutorial ( http://wiki.github.com/radiant/radiant/creating-a-custom-page-type) which has been helpful, and now I have two custom page types up and running. The problem with this is that it sticks all the additional custom fields in the same table as the :pages model. So any given page will have all those columns (if it is of type Speaker, then the Video columns will be nulled etc.) This is all fine and dandy... except when you want to do associations as I mentioned above. I'm wondering is there a way to implement this properly? What I observed from looking at the way the comments extension was done is that a Comment ActiveRecord::Base and then had a foreign key to the Page model (using belongs_to). Then in the comments_extension.rb it uses the Page.class_eval method to put in associations to the Page model. I then thought that I could perhaps do something similar in my situation, but the challenge that I have is that both of those entities MUST be page-types and not thus inherit from Page as opposed to purely from ActiveRecord::Base. So then I'm currently stuck there - with some sort of thought of perhaps somehow doing... a foreign key from the Pages table to a new ActiveRecord Speakers table which would contain all the information? And then when setting the video, somehow pulling speakers from the Speakers model to populate a list or something that they can choose from? In theory this makes sense in my head, but I'm lost as to how to actually implement it properly in Radiant/Rails. Any help with this would be of great help - thanks everyone! Sincerely, -Derek -- Message: 2 Date: Sun, 18 Apr 2010 10:57:15 -0400 From: Marshal Linfoot mlinf...@gmail.com Subject: [Radiant] 0.9.0-rc1 and settings extension To: Radiant@radiantcms.org Message-ID: l2pcaef20e31004180757zffe13edv390c0fe461faf...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 I decided to take the plunge and investigate Radiant 0.9.0-rc1. Some things worked as expected and some didn't. Here's what I encountered; hope this might be helpful to others and/or provide information to developers and extension writers. Desktop: Ubuntu Lucid Lynx, Linux 2.6.32-21-generic Gems: (left out ones not used by
Re: [Radiant] [Radiant-Dev] [ANN] PageParts extension
PageParts is now available from the extension registry: http://ext.radiantcms.org/extensions/222-page-parts I fear I over-explained this originally, so here's a recap and some screen shots. The combination of page parts and Radius tags makes for a lot of flexibility, but sometimes it's not enough. Wouldn't it be great if you could just add a page part and get a file uploader instead of a text area? Or a calendar pop-up? Or even a fieldset with multiple form elements inside it? Enter PageParts. It allows you to create new kinds of page parts that handle any data, not just text. A few examples -- The Add Part popup. You'll notice something new here: http://cloud.github.com/downloads/digitalpulp/radiant-page-parts-extension/part_select.png A part for attaching files to a page: http://cloud.github.com/downloads/digitalpulp/radiant-page-parts-extension/file_part.png A page part with a calendar pop-up: http://cloud.github.com/downloads/digitalpulp/radiant-page-parts-extension/date_part.png It's really easy to get started, too. You can define new kinds of parts with just a few lines of code. Here's all the code needed for those two examples -- Defining a File part: http://gist.github.com/363600 Defining a Date part: http://gist.github.com/363609 Enjoy! j ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] Radiant and Custom Page Forms
Late response, but if you're running Radiant on edge you might also check out two recent extensions, PageFactory and PageParts. PageFactory accomplishes the same thing as Stereotypes, allowing you set up pages with default parts. The main difference is that these definitions live in app/models, instead of in the database. PageParts would allow you to enter meeting dates with a nice calendar pop-up instead of entering them as text (screenshot: http://bit.ly/c5KZ7R) . Additionally, you get some extra Radius tags for working with pages that have dates -- for instance, you could choose to display only meetings with dates after Date.today. (Self-promotion alert: I had a heavy hand in both of these.) j On Apr 7, 2010, at 1:00 PM, radiant-requ...@radiantcms.org wrote: Hey Everyone, I just started looking into Radiant to use as our team's CMS and it looks pretty cool... you guys have done a great job! My question basically is about whether Radiant supports creating custom admin forms so that someone non-technical could create a page. Something like this scenario that uses the Articles page and its children from the Roasters Template: A person who knows no html/ruby can go into the admin section and create a new Article for a Meeting by just filling out certain fields like Meeting Title( which is technically Page Title now), Date of Meeting, Location, and Description. This would just be simple form without the Page Parts (body, extended). And then a technical person would obviously have to write the main Meetings page which aggregates its children and adds all of the styling... something like this: r:children:each limit=5 order=desc div class=entry h3r:link //h3 -- This could stay as the title -- div class=posted Posted by r:author / on r:date format=%B %d, %Y /em|/ emimg src=http://spurrd.com/assets/123/comment.png; /a href=r:url /#disqus_threadComments/aem|/emr:linkRead full article/r:link /div Date of Meeting: r:content part=meeting_date / Location: r:content part=meeting_location / Description: r:content part=meeting_description / /div /r:children:each Is this possible out of the box or will it take a good amount of work to change the model/controller logic behind the scenes? Regardless of the answer we are definitely going to use Radiant on a different project with all technical people. Please let me know if I am not making sense. Thanks, Ryan ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] [ANN] PageFactory extension
PageFactory is now available in the extension registry: http://ext.radiantcms.org/extensions/221-page-factory One issue I haven't figured out how to handle yet is skipping the factory selection popup when there's only one option. My first thought was to return an appropriate header from the AJAX call that renders the popup, and redirect the top window before the Ajax.updater does its thing. I'm thinking I need to return a 302/303 with the proper location here if there's only 1 element in @factories: http://github.com/jfrench/radiant-page_factory-extension/blob/master/app/controllers/admin/page_factories_controller.rb But after that... I'm not sure what the right approach is for the JavaScript. Anyone want to point me in the right direction? Thanks, j ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
[Radiant] [ANN] PageParts extension
On behalf of Digital Pulp, I'm pleased to announce the release of another extension. We simply call it PageParts, and in my completely biased opinion it's the missing link for anyone who's struggled to represent complex content in Radiant. PageParts allows you to manage rich content, objects, and associations through custom page parts that you define. Anything you can do with ActiveRecord and a form builder you can now do inside a Radiant page, thanks to PageParts. PageParts extends the existing pagepart model to handle arbitrary content. For instance, there's a date picker and a single on/off checkbox which you can add to a page just like regular parts. These new parts get stored in the appropriate database columns: datetimes, booleans, c. But where PageParts really shines is with the ability to define your own custom parts. Your parts can manage complex data, create associations, and display themselves any way you want. Here are some of the uses we've found for PageParts: * Attaching file uploads to a page * Managing associations between a page and other records * Adding nested attributes to the page form * Populating Radius tags using form elements instead of markup * Serializing arbitrary data There are working examples of each of these supplied with the extension. I encourage you to take a look and see what's possible with PageParts. Many thanks to the Digital Pulp team and alumni who contributed to this extension: Kunal Shah, Alex Wallace, and Justin Blecher. We first extracted PageParts into its own extension one year ago today -- happy birthday, PageParts! PageParts only runs on 0.9 and will be up on the extension registry after we gather some feedback. Let us know what you think! http://github.com/digitalpulp/radiant-page-parts-extension ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] [ANN] PageFactory extension
I like this too. It sort of reminds me of the templates extension http://github.com/seancribbs/radiant-templates-extension, except you've provided some helpful automation and defaults. The template extension was initially written for one of our projects at Digital Pulp, and we've been evolving an in-house version ever since. PageFactory is my attempt to rethink the whole pattern and improve on the places that I personally found to have the most friction. I think this might be a hint that a CMS could benefit from having a way to quickly generate Admin UI for content objects: Keep watching this list :) -- Message: 4 Date: Wed, 31 Mar 2010 22:13:58 -0400 From: Chase Allen James chaseaja...@gmail.com Subject: Re: [Radiant] [ANN] PageFactory extension (Josh French) To: radiant@radiantcms.org Message-ID: y2u5ab9a5961003311913wf366b70aq726ec7cc8495...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 I like this too. It sort of reminds me of the templates extension http://github.com/seancribbs/radiant-templates-extension, except you've provided some helpful automation and defaults. I think this might be a hint that a CMS could benefit from having a way to quickly generate Admin UI for content objects: class EmployeePageFactory PageFactory layout Employee string 'first name' string 'last name' text 'biography', :content = 'Test', :description = 'A Biography' video 'video clip', :description = 'Upload your video' image 'bio picture', :description = 'Upload your picture' document 'resume', :description = 'Upload your resume' image_collection 'gallery', :description = 'Upload multiple images' end ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] [ANN] PageFactory extension (Josh French)
This is really awesome stuff. you made my day :-) Great! I'm still tinkering, so let me know if you have any feedback. On 31.03.2010, at 18:42, Josh French wrote: New extension on the loose: PageFactory. This is another take on content types/page templates (defining structure for your pages.) [ .. snipped .. ] See the readme for more on the goals and reasoning behind PageFactory. There's a detailed walkthrough in examples.md. http://github.com/jfrench/radiant-page_factory-extension This is really awesome stuff. you made my day :-) cu edi -- DI Edmund Haselwanter, edmund at haselwanter.com, http://edmund.haselwanter.com/ ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] Radiant] Layout Source Control (etc)
Question is, what is the best way of doing this - there seems to be a few extensions out there for copying layouts in and out of the database, but nothing that seems to make a file based layout a first class citizen... We've been using the File System extension (http://ext.radiantcms.org/extensions/67-file-system ) but I recently looked into File System Resources (http://ext.radiantcms.org/extensions/148-file-system-resources ) and I think I like its approach better. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] Radiant Digest, Vol 48, Issue 5
Browsing to http://kevin.local:3000/admin/pages does not show the pages for the new site it shows the pages for the site I first created, this is not what I expected Is this a bug/feature or am I missing something? Hi Kevin, There's no automatic detection of the current domain when viewing the page tree. You have to manually select which site to view -- there should be some links or a drop-down depending on which version of Radiant MultiSite you're using. A patch to automatically show the current domain's tree would definitely be welcome. Alternately, Spanner's got some multi-site addons and/or forks which scope various entities based on site; you may want to see if those match your use case: http://github.com/spanner j ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] Multi_Site and Help Extensions for 0.9
Only multi_site and help were not 0.9 ready as of Friday night. MultiSite should run fine on edge. Were you having a specific problem with it? Josh ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] trouble packaging extension as gem
thanks to some off-list help from Josh French the extension now works as either a gem or traditional vendored extension. the key change was just to add `unloadable` to the KramdownFilter class. John, I just pushed a change which should make that unnecessary. Gem extensions are now automatically unloaded, just like vendored extensions. Gold star for finding the issue! j ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
[Radiant] trouble packaging extension as gem
i'm at loss now for why it's not appearing in the drop down when loaded as a gem. no errors or anything unusual just a missing filter. I'm actually at a loss as to why it would appear when vendored if you're not explicitly loading that subclass. Radiant doesn't do any pre-loading of filter subclasses in the way that it automatically seeks out and loads Page subclasses. If you look at the textile and markdown extensions that ship within core, you'll see that both of them explicitly load the filter subclass within their #activate methods. It'll be safer to follow their example. j ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
[Radiant] trouble packaging extension as gem
def activate KramdownFilter end is not explicitly enough? Sorry, misread your post. Yes, this is correct, and you shouldn't need to do anything else. just noticed that extracting the textile_filter extension out into a gem also fails in the exact same ways that i've run into... I'll investigate. Thanks for giving the new extension system a thorough test-drive! j ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] Fwd: Multi Site extension working in Radiant 0.9?
I am curious if the multi-site extension works with Radiant 0.9. I'd like to upgrade, and I'm curious if it had been tested with that version. Just updated the extension, it's working on edge now. Please let me know if I missed anything. j ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Stories of stability
Hi Peter, What do folks consider a high-volume site? If I'm looking to handle 3 - 5 million page views monthly, which I can do with a few production Rails servers and a non-trivial production architecture (memcache, n-tier architecture, etc.), do folks think Radiant will be up to the task? We're using Radiant on a number of mid- to high-traffic sites. I don't have current numbers in front of me, but at last count our two largest clients had half a million unique visitors so let's assume a significant number of pageviews. All of our apps to date are given one dedicated app server and when called for, a separate DB server (one is backed by an Oracle cluster.) The built-in caching mechanism is adequate for all but the largest of those. Horizontal scaling has been achievable so far without much forethought at the application level. Have you used other CMS?s? Where did they fall short, or where did they have features that you miss? We've used the whole gamut. End users like Radiant because, as they tell us, the admin UI is more user-friendly and the core concepts more grokkable than the alternatives. From a developer perspective, Radiant is great because the core is built to be extensible. There's almost an a la carte approach to building out a CMS in Radiant, and when someone asks for a feature that doesn't exist yet, integration doesn't require armed combat with the framework. To be fair, some of the other platforms out there may be a better fit for portal or community sites. We've done a few Radiant sites that integrate the notion of user accounts, and in every case we've had to make concessions that affect performance. Just a fair warning, if that's your scenario. Hope this is helpful. If you want to talk specifics, feel free to email me. Josh ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Sphinx Extension help
When I run a search I'm getting the following error. undefined method `constantize' for nil:NilClass Hi John, This may help: http://jimneath.org/2009/11/09/thinkingsphinx-and-nil-results/ Best, Josh ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] [ANN] Audit Extension
Digital Pulp is releasing a new Radiant extension which provides an audit trail for all interactions with the admin console. Audit will track creation, updates, and deletion of the core models (Users, Pages, Snippets, and Layouts) as well as user logins and logouts. Audit was built with extensibility in mind and provides an easy framework for logging models and actions from other extensions. The Audit extension was extracted from a client project and is in use in a live environment. It is currently compatible with Radiant edge (0.9 release candidate) only. For more information, please see the repository: http://github.com/digitalpulp/radiant-audit-extension ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Sphinx Extension help
This works fine as all the news gets indexed, however I'm struggling to search the news article. When I do a search terms that has NewsArticles in it I get the following error message Hi John, The Sphinx Search extension was initially built to work with arbitrary models but the actual results page is a late addition and so may need some tweaking. Can you paste a little more of the stack trace where you're getting the undefined method `request' error? I suspect it's just that the results tags are expecting Page objects and your NewsArticle pages don't conform to some assumption. (I am assuming that NewsArticle is *not* a Page subclass -- is that correct?) does it mean that the tags are being indexed and as such and class or id attributes etc might appear I *think* the strip_html option operates before your content gets indexed, but you might want to verify that with the Sphinx folks. One final question, there doesn't appear to be a link tag in the extension's tag class. Do I need to write my own 'link' tag to link to the correct page? In your case, you'll need to because you have polymorphic results objects. There's no way of knowing if your models have methods like link, url, or slug, so I can't supply tags that automatically expose the proper links. In the simple case however -- a search that returns Page objects only -- within an r:results:each block you should be able to call any tag that a Page responds to, like r:url or r:title. Josh ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Site Search
I've been asked to add a site search facility to our intranet site I'm working on at the moment. I'm currently wondering what my best options are. The difficulty is that quite a bit of the site content is stored in extension specific tables. Is using sphinx my best option? Hi John, We've been using Sphinx (by way of the excellent Thinking Sphinx plugin) since switching from Ferret almost 2 years ago and never looked back. It's far more stable and the TS syntax is the best of the bunch, as far as I'm concerned. The Sphinx Search extension was written for your scenario. In addition to indexing page content, you only need to add a define_index block to your custom models and they'll be indexed as well. At the moment there's a search results page class and associated tags for outputting the results, but you may have to tinker to get the tags to work with models that aren't Pages. There may be a way to abstract that out using the newer excerpts feature of Thinking Sphinx, but I haven't investigated that yet. http://github.com/digitalpulp/radiant-sphinx-search-extension Let me know if you have any questions about usage. Best, Josh - - - - - - - - - - - - - - - - - - - - - - - Josh French Senior Engineer, Digital Pulp j...@digitalpulp.com // 212.679.0676 x230 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Extensions with 0.8
Shouldn't we just use rubygems? It already supports dependency management and versioning (this looks like the rails plugins vs gems discussion). We could version them with the radiant version so we could automate getting the proper version: - 0.7.1.2 (works on radiant 0.7.1) - 0.8.0.2 (works on radiant 0.8.0) This would actually be my preferred solution, and I'd like to do some investigative work to see what (if any) modifications would need to be made to the extension architecture to support this. I don't think it removes the need for a better set of community standards/guidelines for the development and management of extensions, though -- if anything, if you're going to maintain a product with actual concurrent releases you probably want a schema like the version- branches we've been discussion. But to the point, I like where this is headed. There's another thread out there about using application templates to bootstrap a Radiant instance; that plus `config.gem 'radiant-awesome-extension'` could be some powerful mojo. j ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: Re: [Radiant] Extensions with 0.8
Not obvious, but Josh French has committed changes for the next release that will allow extension developers to configure dependencies from the extension which might help with the installation process as far as things like error messages go. There will be more development on this in the future. One thing that we don't have is a way of ensuring that the proper version of an extension is installed from the get-go. I'm in the arguably bad habit of manually installing everything, so I was unaware of some of the problems that occur when trying to install extensions via script/extension or ray. To wit, using an installer to install a 0.8-style extension will fail if your base Radiant install is 0.7 or earlier. Because the extension is checked out at its head, the environment fails and neither rake:migrate nor rake:update can be run until the extension is frozen to a compatible tag/version. This could be solved by adding a version argument to the install method, or by baking knowledge of the current Radiant version into the installer. I've been tagging the extensions I'm involved with for compatibility at versions 0.7.1 and 0.8.0, but I've also been wondering if it wouldn't be better to maintain those via branches instead of tags -- have a 0.7 branch to hold bugfixes, but continue new development in 0.8 and so on. Thoughts on how best to manage extensions across multiple, possibly incompatible, versions of Radiant? j ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: multi_site extension and mysql error
Upon migrating getting mysql error: == 3 AddBaseDomainToSites: migrating == -- add_column(:sites, :base_domain, :string) rake aborted! Mysql::Error: Duplicate column name 'base_domain': ALTER TABLE `sites` ADD `base_domain` varchar(255) Hi Daniel, Looks like one of your earlier install attempts failed halfway through the extension migration. You have the full multisite schema, but this is not recorded in the schema_migrations table. Possible solutions: * Drop the sites table and remigrate the multisite extension. This is destructive, and if your schema_migrations is stuck at an intermediate version you'll have further problems. * Alter schema_migrations so that it contains all 3 multisite migrations. This is the quicker/easier fix. j On Jun 14, 2009, at 12:54 PM, radiant-requ...@radiantcms.org wrote: Send Radiant mailing list submissions to radiant@radiantcms.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.radiantcms.org/mailman/listinfo/radiant or, via email, send a message with subject or body 'help' to radiant-requ...@radiantcms.org You can reach the person managing the list at radiant-ow...@radiantcms.org When replying, please edit your Subject line so it is more specific than Re: Contents of Radiant digest... Today's Topics: 1. Creating a UL/IMG based Navigation Bar (Jeff Casimir) 2. multi_site extension and mysql error (Daniel O'Connell) 3. Re: Back Door conditionals iffy? (Steven Southard) 4. Re: Re: Possible to disable cache for a single page? (Nicholas Henry) -- Message: 1 Date: Sat, 13 Jun 2009 13:25:07 -0400 From: Jeff Casimir j...@casimircreative.com Subject: [Radiant] Creating a UL/IMG based Navigation Bar To: radiant@radiantcms.org Message-ID: 70dad9df0906131025m6d3b4894ue9f4882459f5d...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 Hi All, Today is my first day building my site with Radiant -- I'm loving it! Once I got the basic layout, snippets, and pages implemented, I had to figure out my navigation bar. It took me some tinkering, so I thought I'd post the results on the wiki: http://wiki.github.com/radiant/radiant/creating-a-ul-img-based-navigation-bar I'd appreciate any feedback or redirection if I did something ugly. I wrestled with the wiki for a few minutes trying to figure out why those extra grey spaces were showing up under each code block, but I didn't crack the problem. - Jeff -- Message: 2 Date: Sat, 13 Jun 2009 14:15:35 -0600 From: Daniel O'Connell d...@mac.com Subject: [Radiant] multi_site extension and mysql error To: radiant@radiantcms.org Message-ID: be0a9d26-49db-4d96-a1b6-0baa61220...@mac.com Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Hello to all, My first post to any list. I am new to radiant and rails and head long into my first project, a client website. I'm trying to install multi_site on Radiant 0.7.1. Using script/ extension install leads to a version that seems to be for radiant 0.8.0 (see multi_site_extension.rb) and will not correctly migrate. The very kind Josh French gave me instruction to check out the 0.7.1 tagged version, but I am still having problems Upon migrating getting mysql error: == 3 AddBaseDomainToSites: migrating == -- add_column(:sites, :base_domain, :string) rake aborted! Mysql::Error: Duplicate column name 'base_domain': ALTER TABLE `sites` ADD `base_domain` varchar(255) Restarted server hoping for the best, but Radiant crashes with an Application Error and I cannot login to admin and public site doesn't function. Using ray I disabled the extension and site is back online, but I really need this extension to work properly. Any ideas? Always Victory! -Daniel -- Message: 3 Date: Sat, 13 Jun 2009 15:16:17 -0500 From: Steven Southard ste...@stevensouthard.com Subject: Re: [Radiant] Back Door conditionals iffy? To: radiant@radiantcms.org Message-ID: 37a56ee1-1eb1-4b1d-a63b-a1e61c441...@stevensouthard.com Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Of course, that is much better. I sure like the idea of Back Door but giving up caching seems a high cost. On Jun 13, 2009, at 5:05 AM, Jim Gay wrote: It would appear that caching is not a good idea with that extension. I think you would be better served using Microsoft's conditional comments. Jim On Jun 13, 2009, at 2:26, Steven Southard ste...@stevensouthard.com wrote: Sure seem to be, which makes me wonder how this example shown at http://backdoor.rubyforge.org/ could ever be reliable. r:if cond=request.env[ 'HTTP_USER_AGENT'] =~ /MSIE/ !-- Internet Explorer needs some ugly hacks to render PNG images with transparency -- div id=logo style
[Radiant] RailsConf BoF
I'm sussing out interest in a Radiant BoF session at RailsConf. If anyone will be attending RailsConf and thinks they may be interested in attending a BoF session, please let me know. I'm also welcoming any suggestions for topics. Thanks, Josh ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] So how did things go this weekend?
Josh French -- please fill us in on what you and your group did on Saturday; I missed a lot of that. Andrew O'Brien, Mike Hale, Luke whose last name I am blanking on (apologies), and myself started work on extending the page class to accept arbitrary attributes -- booleans, integers, timestamps, c. This pattern shows up in numerous extensions and we saw a need for a generalized solution. The primary goal was to expose a number of simple object types (single-dimensional data, like the existing metadata fields) and allow these to be managed via a mechanism similar to the page-parts interface. We're also aiming for a solution that can eventually be extended to accept complex data structures. You can follow our progress at http://github.com/jfrench/radiant-page-attributes. j ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant T-Shirt design - Please give input!
Second, John suggested putting a pithy saying on the back of the shirt -- especially if we use the large gem in the center front. Radiant CMS (x-ray vision not included) was his suggestion. I'd appreciate some more input on that (or if you want a blank back). I'm of the less-is-more school of t-shirt philosophy: big logo, no text, empty back. This leads the casual observer to wonder: wither your awesome shirt, sir? leading to inquiry, evangelization, and eventual conversion to Radiant. (But if we must: how about simply No fluff on the back?) j ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] multiple domains under Phusion Passenger
I'm working on a pair of sites for a client that will be on two subdomains and hosted on a shared host (Dreamhost). I thought the multi-site extension would be ideal for that but have not yet figured out how to do this under Phusion Passenger, the preferred Rails deployment method at DH. To allow mod_rewrite, add this to your apache conf: RailsAllowModRewrite on Passenger's issue with mod_rewrite is that the default .htaccess supplied with Rails tries to funnel all requests through one of the dispatchers, so be sure to remove either the entire .htaccess file from /public, or remove everything but those parts you know you need (e.g. static caching, as Jay Levitt mentioned.) However, we've successfully served multiple subdomains without resorting to mod_rewrite by defining each subdomain from within the multisite extension -- main.tld and sub.main.tld, both being served from a single Radiant instance. Is that your use case? Your question implies you've got a dev or preview domain that may need additional http authentication -- that's also possible, but I don't want to confuse the issue if that's not your scenario. j ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Can't install radiant
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 the DB and refuse to install anything without a proper schema in place first? j -- Message: 8 Date: Wed, 25 Jun 2008 11:11:31 -0700 From: Alex Wayne [EMAIL PROTECTED] Subject: Re: [Radiant] Can't install radiant To: radiant@radiantcms.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes That's kind of a poor solution in general. Say you commit your radiant to git, and deploy via capistrano, extensions included. It would suck to uninstall those on the webserver. The better solution is that extension should be written so that they don't break bootstrapping. -Alex http://beautifulpixel.com On Jun 25, 2008, at 10:59 AM, Mohit Sindhwani wrote: Alex Wayne wrote: Just remove the gallery folder from vendor/extensions, get yourself up and running just as you were trying to do before (rake db:bootstrap), and then put the gallery extension back where it was. -Alex http://beautifulpixel.com Alex, should this be added to the wiki? Always bootstrap without any extensions? Cheers, Mohit. 6/26/2008 | 1:59 AM. ___ 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 End of Radiant Digest, Vol 27, Issue 70 *** ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Can't install radiant
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 extension non-reloadable (see http://tinyurl.com/4cwo6e). Based on the state of the DB or a user-set attribute, individual extensions could choose not to activate/reactivate. j ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Radiant Digest, Vol 25, Issue 32
Every extension that used shards has been rendered completely useless. None of the Admin UI additions provided by extensions show up anymore. Is there a way to fix this, has shards been integrated into core? I need help! Arik, This is a bug that snuck in to 0.6.5. Sean should be pushing a fixed release soon; in the meantime, you can apply this patch: http://github.com/jfrench/radiant/commit/ 52897147ae427b6dea4c8281e9e9bdf9e2c6fa9a j On Apr 20, 2008, at 12:55 PM, [EMAIL PROTECTED] wrote: Send Radiant mailing list submissions to radiant@radiantcms.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.radiantcms.org/mailman/listinfo/radiant or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than Re: Contents of Radiant digest... Today's Topics: 1. Re: Ruby Gems Installation Issue (Tom Cloyd) 2. Re: Ruby Gems Installation Issue (Rufo Sanchez) 3. Shards and Radiant 0.6.5 Chisel (Arik Jones) 4. Re: Ruby Gems Installation Issue (Tom Cloyd) 5. Re: Ruby Gems Installation Issue (Tom Cloyd) -- Message: 1 Date: Sat, 19 Apr 2008 18:40:22 -0700 From: Tom Cloyd [EMAIL PROTECTED] Subject: Re: [Radiant] Ruby Gems Installation Issue To: Radiant CMS List radiant@radiantcms.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=windows-1252; format=flowed I just updated to ver. 0.6.5. My essential problem remains: $ radiant --database sqlite3 /home/tom/Ruby projects - Toms/radiant-test-CMS bash: radiant: command not found Awaiting enlightenment. t. -- ~ Tom Cloyd, MS MA, LMHC Private practice Psychotherapist Bellingham, Washington, U.S.A: (360) 920-1226 [EMAIL PROTECTED] (email) TomCloyd.com (website psychotherapy weblog) sleightmind.wordpress.com (mental health issues weblog) directpathdesign.com (web site design consultation) ~ -- Message: 2 Date: Sat, 19 Apr 2008 23:52:05 -0400 From: Rufo Sanchez [EMAIL PROTECTED] Subject: Re: [Radiant] Ruby Gems Installation Issue To: [EMAIL PROTECTED], radiant@radiantcms.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1 On Sat, Apr 19, 2008 at 8:28 PM, Tom Cloyd [EMAIL PROTECTED] wrote: locate spewed out the files in /var/lib/gems/1.8/doc/radiant-0.6.4/, of course. It also listed /var/lib/gems/1.8/bin/radiant, so, I executed the radiant --database sqlite3 /home/tom/Ruby projects - Toms/radiant-test-CMS command I'd tried earlier, from within that dir, and once again got: bash: radiant: command not found Tom, Apologies if you know/tried this already, but sometimes it's the simple things... What happens if you run the radiant command using the absolute path, e.g. /var/lib/gems/1.8/bin/radiant ...instead of switching to the /var/lib/gems/1.8/bin directory? Most UNIX installs don't put the current directory in PATH for security reasons, so while that may have been the radiant command you tried to launch, the shell may not have found it. If that works, you can add the /var/lib/gems/1.8/bin directory to your PATH, and from that point on you should be good to go. Hope this helps, and good luck with your Radiant adventures, Rufo -- Message: 3 Date: Sun, 20 Apr 2008 06:11:17 +0200 From: Arik Jones [EMAIL PROTECTED] Subject: [Radiant] Shards and Radiant 0.6.5 Chisel To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=utf-8 Every extension that used shards has been rendered completely useless. None of the Admin UI additions provided by extensions show up anymore. Is there a way to fix this, has shards been integrated into core? I need help! -- Posted via http://www.ruby-forum.com/. -- Message: 4 Date: Sun, 20 Apr 2008 07:59:38 -0700 From: Tom Cloyd [EMAIL PROTECTED] Subject: Re: [Radiant] Ruby Gems Installation Issue Cc: radiant@radiantcms.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1; format=flowed Rufo Sanchez wrote: On Sat, Apr 19, 2008 at 8:28 PM, Tom Cloyd [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: locate spewed out the files in /var/lib/gems/1.8/doc/radiant-0.6.4/, of course. It also listed /var/lib/gems/1.8/bin/radiant, so, I executed the radiant --database sqlite3 /home/tom/Ruby projects - Toms/radiant-test-CMS command I'd tried earlier, from within that dir, and once again got: bash: radiant: command not found Tom, Apologies if you know/tried this already, but sometimes it's the simple things... What happens if you run the radiant command using the absolute
