[Radiant] Trouble with Creating a Custom Page Type
Hey Everyone, I just started the tutorial for Creating a Custom Page Type (http://wiki.github.com/radiant/radiant/creating-a-custom-page-type) and I'm not getting the expected results. I started with a new Roasters project using version 0.8.1. Then I ran the script/generate extension_model tennis PlayerPage command and it generated everything that it was supposed to (using the normal path: app/models/player_page.rb)... next I changed the class that was created to inherit from Page. Next the tutorial says to start-up the server to make sure that PlayerPage is in the Page Type list on the edit screen. When I start the server I get a message that says : #NameError: uninitialized constant TennisExtension and the type does not show up in the list! What am I doing wrong here? I can see that the generate script created a migration that sets up a table... do I need to run a some sort of rake migrate task? There aren't too many steps to this part of the tutorial so I don't think I've missed one. There is a Troubleshooting part that says if I don't see my custom type I probably put the player_page.rb file somewhere other than app/models/ but the file is there, so I don't know what to do now. Any help or pointers would be greatly appreciated... 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] Radiant and Custom Page Forms
Anna and Fito... thanks a lot for your help. I'll check out the custom Page stuff tonight! - Ryan On Wed, Apr 7, 2010 at 11:23 AM, José Adolpho da Silva Gordo Neto fitogo...@gmail.com wrote: Hi Ryan, Unless I am missing something, I think Radiant can meet your needs out of the box with the help of a few extensions. However, I would do this a little differently than you describe for simplicity's sake. I would use the stereotype extension so that every page added under the / meetings page would be created with the necessary body parts (Date, Location, Description, etc...). Now everytime the non-technical user creates a page under meetings, the correctly named body parts are automatically added, and the user simply has to click on the relevant body part and fill in the necessary info. I think there is an extension for building forms and calling them through Radius tags, but I think the method I described above is a little more straight forward and more inline with the overall Radiant architecture. Someone please correct me if I'm wrong. -Fito On Apr 7, 2010, at 11:36 AM, Ryan Ferretti 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 ___ 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 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] Radiant and Custom Page Forms
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
