Re: [Radiant] This Website was done with Radiant
Radiant gem 0.6.9. All tough I've got plans to upgrade to 0.7.x soon. Some other great pieces of software we have used: CentOS Apache HTTP Server Phusion Passenger Ruby Enterprise Edition /simon On Tue, 21 Apr 2009 12:13:02 -0400 Jason Garber wrote: > What version of Radiant did you use? Just curious. > > On Apr 21, 2009, at 5:41 AM, Simon Josi wrote: > > > A while ago we released a redesign of our company's website: > > > > http://www.puzzle.ch > > > > Used Extensions: > > admin_breadcrumbs date_names ray > > admin_tree_structure default_page_parts search > > aggregation drag_order settings > > alias_pageheader_authorizesibling_tags > > blog helpsns > > change_author mail_to sns_minifier > > comments paginatesubscriber_lists > > conditional_tags paperclippedsuper_export > > copy_move parameterized_snippets tags > > dashboard radiant_extensions vapor > > > > This CMS is absolutely great! Thanks to all for the superior work! > > > > > > /simon > > ___ > > 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 signature.asc Description: PGP signature ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] This Website was done with Radiant
A while ago we released a redesign of our company's website: http://www.puzzle.ch Used Extensions: admin_breadcrumbs date_names ray admin_tree_structure default_page_parts search aggregation drag_order settings alias_pageheader_authorizesibling_tags blog helpsns change_author mail_to sns_minifier comments paginatesubscriber_lists conditional_tags paperclippedsuper_export copy_move parameterized_snippets tags dashboard radiant_extensions vapor This CMS is absolutely great! Thanks to all for the superior work! /simon signature.asc Description: PGP signature ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Using absolute urls
I'm still using 0.6.9, I don't know if this issue is fixed for 0.7.x. I've fixed this in my fork of the comments extensions: http://github.com/turingmachine/radiant-comments/commit/c5efa910e5c83ebd7402a7c263064c6f28741bd1 /simon On Thu, 2 Apr 2009 17:01:27 +0200 Victor Elsendoorn wrote: > Dear list, > > I found out having trouble with the comments extension in > combination with the usages of a navigation snippet based on using > the tag. > > It seems that it has something to do with the fact that the > tag is producing relative url's rather than absolute > url's. Can someone tell me how to use absolute url's instead of the > relative ones? > > By the way, the error produced by the comments controller: not > expecting nil_relative_url_for > > Hope someone can help me out here. > > Regards, > Victor > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant signature.asc Description: PGP signature ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] what extensions do you have installed?
$ git-submodule | cut -d / -f 3- admin_breadcrumbs (heads/master) admin_tree_structure (heads/master) aggregation (heads/master) blog_tags (heads/master) comments (heads/master) conditional_tags (v0.4) copy_move (heads/master-1-g9f3dd2a) dashboard (heads/master) default_page_parts (heads/master) header_authorize (remotes/origin/HEAD) help (v1-23-gc327650) mail_to (heads/master) paginate (heads/master) paperclipped (heads/master-19-g2e48f3f) parameterized_snippets (heads/master) radiant_extensions (heads/master) ray (1.3) reorder (heads/master-4-g22ed6cd) search (heads/master) settings (remotes/origin/HEAD) sibling_tags (remotes/origin/HEAD) sns (v0.7.1) subscriber_lists (heads/master) tags (pre-radiant-0.7~1) signature.asc Description: PGP signature ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] tags extension
Maybe this could work: http://github.com/Aissac/radiant-extensions-extension greets /simon On Wed, 28 Jan 2009 12:14:42 +1100 Enrico Teotti wrote: > Hi, > I need to have the tag list for each page coming out of: > > > I'd use a: > > > but since that's not allowed by radius I am now clueless. How would > you do it? Is anybody doing such a thing? > Cheers, > Enrico signature.asc Description: PGP signature ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Cache Home Page (prevent the long delay)
You could fetch your homepage in a regular intervall via a cronjob. E.g. wget -r -nd --delete-after http://yoursite.com /simon On Thu, 22 Jan 2009 16:50:12 +0100 Ben Morrow wrote: > I run Radiant on Passenger and I was wondering if there was a way to > have the home page of a site always cached. > > When there have been no visitors to a site for about a day, it often > takes the sever more than 20 seconds to respond to a request for a > page. signature.asc Description: PGP signature ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] XSS in Comments Moderation Page
Amendment: It's only handled correctly in the frontend if
comments.filters_enabled is false.
On Mon, 12 Jan 2009 11:37:42 +0100
Simon Josi wrote:
> XSS ist possible in the admin part of the comments extensions.
>
> Reproduce:
> 1. Post a Comment with say "alert("oh my xss")"
> 2. Login as admin, goto comments tab
> 3. you see...
>
> In the frontend, the output is handled correctly.
> This gives an attacker the possibility to take over an admin account.
>
>
> /simon
signature.asc
Description: PGP signature
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] XSS in Comments Moderation Page
XSS ist possible in the admin part of the comments extensions.
Reproduce:
1. Post a Comment with say "alert("oh my xss")"
2. Login as admin, goto comments tab
3. you see...
In the frontend, the output is handled correctly.
This gives an attacker the possibility to take over an admin account.
/simon
signature.asc
Description: PGP signature
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Set published_at date
Thank you! On Tue, 06 Jan 2009 18:45:37 +0800 Mohit Sindhwani wrote: > Simon Josi wrote: > > I can remember that previous version of radiant did allow to modify > > the published_at date in the edit mode of a page. Is this no longer > > possible? > > > Hi Simon, > > http://wiki.radiantcms.org/Publication_Date_Fields_Disappear > > Cheers, > Mohit. > 1/6/2009 | 6:45 PM. > > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant signature.asc Description: PGP signature ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Set published_at date
I can remember that previous version of radiant did allow to modify the published_at date in the edit mode of a page. Is this no longer possible? /simon signature.asc Description: PGP signature ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Conditions in r:children
Any chance this gets merged into core? Should I pack it into an extension? Or maybe integrate it into an existing extension with similar aim like blog_tags or sibling_tags? I would suggest to merge it into core because it's only a small addition to an already existing tag (). greetings, /simon On Sat, 25 Oct 2008 21:23:43 +0100 Andrew Neil wrote: > Today is the Radiant sprint day. I made a proposal for an > enhancement to the standard Radius tags: > > http://pastie.org/300372 > > I've implemented this now in my own fork of Radiant. Check it out > here: > > http://github.com/nelstrom/radiant/tree/master > > I'd be interested to hear of any thoughts on this. > > Cheers, > Drew > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- Simon Josi Linux System-Ingenieur Puzzle ITC GmbH www.puzzle.ch Telefon +41 31 370 22 00 Direkt +41 31 370 22 43 Mobile +41 79 732 98 35 Fax +41 31 370 22 01 Puzzle ist Mitglied der Eclipse Foundation: <http://www.puzzle.ch/eclipse/> signature.asc Description: PGP signature ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Tags extension: move to latest edge breaks db migration
The task rake db:migration breaks on a file of the Tags extensions if I move to latest edge. http://pastie.org/312887 /simon signature.asc Description: PGP signature ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Conditions in r:children
Absolutel great! That's what I was looking for since quite some time. Unfortunately I didn't took the time to implement it myself. Accordinlgy I would like to see those changes to be merged and thereby available in edge. /simon On Sat, 25 Oct 2008 21:23:43 +0100 Andrew Neil <[EMAIL PROTECTED]> wrote: > Today is the Radiant sprint day. I made a proposal for an > enhancement to the standard Radius tags: > > http://pastie.org/300372 > > I've implemented this now in my own fork of Radiant. Check it out > here: > > http://github.com/nelstrom/radiant/tree/master > > I'd be interested to hear of any thoughts on this. > > Cheers, > Drew > ___ > 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] parameterized_snippets extension
Thank you! Unfortunately i've came across another error: The tag ist not working, as for my example it only works if I change the line: class=""> to "> Stack trace: http://pastie.org/297893 The latter variant is absolutely perfect mor me though, thank you. /simon On Wed, 22 Oct 2008 04:44:32 +0200 "Manuel Meurer" <[EMAIL PROTECTED]> wrote: > Fixed, thanks for testing. > Please grab a fresh copy from > http://github.com/manuelmeurer/radiant-parameterized-snippets-extension/ > > Manuel > > On Tue, Oct 21, 2008 at 12:10 PM, Simon Josi <[EMAIL PROTECTED]> wrote: > > I've got a case where parameters to snippets are not availabe. It > > occurs when I call a snippet with parameters from another snippet: > > > > Content of page "Referenzen": > > > > > > The "Referenzen" page contains childs with "text", "image" and > > "body" parts defined. > > > > Content of snippet "list_childs_as_generic_entries": > > > > > > > > > > > >!(photo)()! > > > > > > > > > > > > > > Content of snippet "image_with_border": > > class=" > name="class" />"> > class="top"> > class="body"> > class="bottom"> > > > > The class parameter is not set if a open the page "Referenzen". > > > > If i call the snippet "image_with_border" directly from a page and > > not from a snippet, it works. > > > > Any ideas on that? > > > > Thx, > > /smon > > ___ > > 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] parameterized_snippets extension
I've got a case where parameters to snippets are not availabe. It occurs when I call a snippet with parameters from another snippet: Content of page "Referenzen": The "Referenzen" page contains childs with "text", "image" and "body" parts defined. Content of snippet "list_childs_as_generic_entries": !(photo)()! Content of snippet "image_with_border": class=""> The class parameter is not set if a open the page "Referenzen". If i call the snippet "image_with_border" directly from a page and not from a snippet, it works. Any ideas on that? Thx, /smon ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] r:children:if_first r:children:if_last
I mostly agree with what Jim said. It'd be more natural to work with "speaking" tags like or . Radius tags are a cornerstone of radiant, and as complexity grows, more tags emerge. Sticking all functionality into one does IMHO not reduce complexity nor does the user have less to learn. Nonetheless there is certainly room for extensions like the one from Chris. I'd especially like the variables part, i could use it to "parametrize" snippets, a feature which I'm missing too. Chris, is your extension available on GitHub? /simon On Thu, 26 Jun 2008 21:41:11 -0600 Chris Parrish <[EMAIL PROTECTED]> wrote: > Thanks for your response and kind words, Jim. See my comments > below... > > Jim Gay wrote: > > I agree that the list of if_this unless_that can get very long, but > > there is a benefit in that the intentions of the code are clear. > > I remember seeing emails about your extension and being very > > interested in the past, Chris, but I didn't have time to take a > > look at it. > > > > I agree with the principle that a single r:if would make life > > simpler, but my gut reaction is that it starts looking less > > natural. But maybe I'd feel better with some nomenclature changes. > > > > Please resurrect it. I've got some questions that might just be > > cleared by using it. > > At this point, I plan to bring it back. I have two issues I'd like > to address and time is the big factor. > > > > > Something just bugs me when I see shortcuts such as the attribute > > "cond" when I feel like "condition" would be clearer. I think that > > in a system like Radiant, which seems to have some good coverage > > with non-technical users, clear intentions are important. > > I agree. Actually, in my original version I permitted both > cond="xxx" and condition="xxx" to allow for quicker typing among the > geeks. > > > > > I would scope the variables stuff more explicitly, such as > > and > > Because, although I haven't done it yet, I think a simple ecommerce > > web store would be a nice extension and would make sense > > there. > > Good idea. Other variations included > I'm now thinking that a better approach would be book="John" chapter="3" verse="16" />. It seems more readable. > > By the way, I opted to only create a specific variable setter but a > generalized getter. Since my > had to be able to evaluate page.title to compare it, it seemed > natural to create a way to output anything evaluation-able. So you > can also: or > > > Now, these two examples overlap with the existing and > which are more concise, but it makes it > nice for extension writers to easily offer: > > > (more on "this.that" below...) > > > > > > You mentioned using but should > > that have a double equal (==)? > > It currently allows "x=1", "x ==1", or "x equals 1" since radiant is > geared at the non-programmer. Incidentally, "x == y" is also > permitted. > > > Does it allow the use of RegExp matching with =~ ? > > It currently allows "x matches /regexp/" and "x match /regexp/" but > also including "=~" would be trivial. > > In addition, the following comparisons are permitted: > > * "x exists", "x exists?", or just "x" > * "x blank", "x is_blank", or "x blank?" > * "x empty", "x is_empty", or "x empty?" > * "x not 12" or "y != 'my string value'" > * "x < y" or "1 lt 2" (> and gt also available) > * "y <= 'A'" or "x lte z" (>= and gte also available) > > > > Does the extension provide a way to easily describe how to parse > > things like "children.index" or "this.that" ? > > No -- though I've always considered this critically needed. This is > where I got stuck as my ruby and radiant chops just weren't there. > I'd love to look into it now that I am much more familiar with > radiant but this is also the place I would very much welcome help. > > Basically, my code parses the condition into left and right symbols > and the comparison element and then hands off the symbols to be > evaluated. I'd want extension writers to be able to add in code to > define how to evaluate their own custom symbols. I need a good > mechanism for that. So if you define a current_shopper.index, you > could instantly offer: > > makes me think, "huh?" > > > > Just this evening I was walking a client through parts of their > > Radiant site. I always say something to the effect of "you can > > always contact us when things need to be changed, but this is how > > its done..." Some people speak up and say "Ok, forget it, I don't > > need to see that" while others pay attention. > > When I walked through a few examples we have with > part="part_name"> the client said, "Oh, cool". The intentions of > > that code are very clear and I have little fear (depending on the > > user) that someone can screw that up. > > > > That's not to say that everything should be dumbed down, but to me > > something like is very friendly. So a > > DRYer would be nice, but I think a friendly dialect (for
[Radiant] r:children:if_first r:children:if_last
The tag r:children could provide two more tags that can be used to determine with which element we are working with in each iteration. This example implements the functionality with currently available tags: I need to assign the class "first" to the first element and the class "last" to the last element. It would be nice to make it work like that: "> The snippet blogentry_preview_class would look like this: first last Would anyone else would want to have these tags available? cheers /simon ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
