Re: [Radiant] page_attachments doubt

2010-04-07 Thread Sharon Clift
I'm using an older version of page attachments but in my site the images
are stored within numbered folders in the public\page_attachment folder.
When I first uploaded an image it created a folder called  and
subsequent uploads create a new folder within there.

While the images are referenced in the database, the full path to an
image on our site would be something like 

radiant_path\public\page_attachments\\0273\image1.jpg 

Sharon


This e-mail has been scanned for all viruses by MessageLabs.
___
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

2010-04-07 Thread Ryan Ferretti
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] Radiant and Custom Page Forms

2010-04-07 Thread banane
Check out the scores example in the wiki, it's similar to what you want to do:

http://wiki.github.com/radiant/radiant/creating-a-custom-page-type

My opinion on these matters is to minimally change the interface, by
adding extended parts, not to create a special extension. Check out
the user-access levels member extension
(http://blog.aissac.ro/radiant/member-extension/), to simplify the
admin interface. This may remove a lot of the tech stuff you think
is confusing people.

Anna

On Wed, Apr 7, 2010 at 7:36 AM, Ryan Ferretti
rferre...@redpointtech.com 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


Re: [Radiant] Radiant and Custom Page Forms

2010-04-07 Thread José Adolpho da Silva Gordo Neto
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] newsletter extension

2010-04-07 Thread Steven Southard
Is anyone using the newsletter extension anymore?  Is Reader now doing  
the same job?

Steven


___
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