[Radiant] Multi-site Templates
Multi-site is friggin wonderful. However, I have seen a persistent need for site templates. Here is how I imagine it'd work. I create a sort of boilerplate site complete with intended pages, their parts and maybe some "get started" content. Is there a way to save this data as a template for use in a new site in multi-site? I assume not, so would anyone be interested in building this out? I'm just a designer. :( -- 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] Any easy way to extract sites from multi-site installation?
Hi! I've been doing a bit of testing I've found that an instance of Radiant +Rails easily eats up up to 80MB of memory for a while when using mod_rails, after a while one of the processes dies and about half of the memory usage is left hanging for quite some time. (I'm using Dreamhost so I don't think I can configure the timeout periods in any ways.) So this leaves me with the conclusion that the only sensible way to host small Radiant-sites is using the multi-site extension, even when using mod_rails (at least at Dreamhost where you can't shorten the timeout periods for things). So because of this I might want to jam all of the small sites that I've made for my customers into a single multi-site installation of Radiant. But what do I do then if I for some reason later would have to move one site out of that installation? Do I just copy & paste all of the material? No that can't be the case, can it? :) cheers, Simon ___ 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] Conditional Tags Extension
Chris Parrish wrote: This is interesting. I'll have to think about this. Essentially what you're going for here is the removal of the attributes (something I agree with). I bet my extension would be more comfortable if only you could write: I haven't thought this through, but what about separating the condition, and having it swallow the tag output? This page is highly accurate! Warning: This page contains factual errors. I dunno if Radius can deal with "intermediary" tags like that; if not, you could do , but that might get ugly. And I'm not sure if the whole "containing tag" concept is too painful for non-techies. But ISTM that an "if" that can test any tag's output is mighty powerful... Jay ___ 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: radiant-tags-extension with PostgreSQL?
Benny Degezelle wrote: 5. I also think I sent a pull request to everyone else. Hope that's the right thing to do. Pull request received and handled. I cherry-picked your commits instead of merging though, because i think the tag_list_technorati stuff by ehaselwanter should go in a seperate branch. Oops, you're right.. I was blindly merging everything. Re your Weekly wacky suggestion; we coùld rename the extension (I'd prefer radiant-metatags-extension), but that is not going to stop people from referring to it as the tags extension, so I'm not too sure if that would make googling for it easier?.. yeah, probably not, unless you also changed the [radius] tags themselves - e.g. r:metatags:each, r:metatags:cloud, etc. I'm not sure if it's actually worth it; I was kinda thinking out loud. I figured either someone would love the idea, or they'd hate it. Or they'd think it's okay. Jay ___ 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/Radius/Extensions + HTML 4.01
As far as paperclipped is concerned, I think the only tag that actually generates HTML is the r:image tag and r:link. You could easily use the r:url and some page parts to make your own system using HTML 4. In general though, I think this would be a nuisance and get in the way of nice clean tags. Keith Bingman On Oct 26, 2008, at 7:19 PM, Sean Cribbs wrote: With a few exceptions (links and form stuff like 'mailer'), it's my opinion that your Radius tags should not generate markup, but should assist you in generating markup. Putting too much markup in a tag definition is a bad code smell; it also makes them harder to test. That said, that kind of configuration option sounds like more of a hassle than a benefit. Maybe you could get the extension authors to modify the extension(s) or do the github thing and fork it and change it yourself. Sean Jeffrey Jones wrote: Hello all, At the moment it seems the Radiant ecosystem is setup to generate XHTML tags (paperclipped comes to mind). As I am going to make my site HTML 4.01 this presents something of a nuisance. I can easily alter the paperclipped code to output HTML but that is fixing a symptom and not addressing a core issue. Would it be possible to include a standard RadiantConfig option to specify the output format of tags? If a standardised config option was chosen then all extensions that output HTML/XHTML code could then check the option and output the correct tags for the given specification. Naturally it would default to the current XHTML code but it would offer a bit of flexibility. Note that I am talking only about the main site code. The admin system can whatever it likes. What do you guys think? RJ ___ 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] Radiant/Radius/Extensions + HTML 4.01
With a few exceptions (links and form stuff like 'mailer'), it's my opinion that your Radius tags should not generate markup, but should assist you in generating markup. Putting too much markup in a tag definition is a bad code smell; it also makes them harder to test. That said, that kind of configuration option sounds like more of a hassle than a benefit. Maybe you could get the extension authors to modify the extension(s) or do the github thing and fork it and change it yourself. Sean Jeffrey Jones wrote: Hello all, At the moment it seems the Radiant ecosystem is setup to generate XHTML tags (paperclipped comes to mind). As I am going to make my site HTML 4.01 this presents something of a nuisance. I can easily alter the paperclipped code to output HTML but that is fixing a symptom and not addressing a core issue. Would it be possible to include a standard RadiantConfig option to specify the output format of tags? If a standardised config option was chosen then all extensions that output HTML/XHTML code could then check the option and output the correct tags for the given specification. Naturally it would default to the current XHTML code but it would offer a bit of flexibility. Note that I am talking only about the main site code. The admin system can whatever it likes. What do you guys think? RJ ___ 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] Radiant/Radius/Extensions + HTML 4.01
Hello all, At the moment it seems the Radiant ecosystem is setup to generate XHTML tags (paperclipped comes to mind). As I am going to make my site HTML 4.01 this presents something of a nuisance. I can easily alter the paperclipped code to output HTML but that is fixing a symptom and not addressing a core issue. Would it be possible to include a standard RadiantConfig option to specify the output format of tags? If a standardised config option was chosen then all extensions that output HTML/XHTML code could then check the option and output the correct tags for the given specification. Naturally it would default to the current XHTML code but it would offer a bit of flexibility. Note that I am talking only about the main site code. The admin system can whatever it likes. What do you guys think? RJ ___ 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-tags-extension with PostgreSQL?
> 5. I also think I sent a pull request to everyone else. Hope that's the > right thing to do. Pull request received and handled. I cherry-picked your commits instead of merging though, because i think the tag_list_technorati stuff by ehaselwanter should go in a seperate branch. 6. If all the power goes out somewhere, let me know. It could possibly be > my fault, but I'm pretty sure I canceled that in time. I noticed the lights flickering, but the generators seem to have coped succesfully ;) Thanks for your contributions! Re your Weekly wacky suggestion; we coùld rename the extension (I'd prefer radiant-metatags-extension), but that is not going to stop people from referring to it as the tags extension, so I'm not too sure if that would make googling for it easier?.. Regards, Benny ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Problem using children:each and the Dynamic Image extension
Finally found the cause for this problem. Change the file lib/dynamic_image.rb in the Dynamic Image extension: #13 is config = tag.attr but should be config = tag.attr.dup Manuel On Sat, Oct 4, 2008 at 4:29 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote: > Hi! > > I'm experiencing some strange behavior using the children:each tag and > the Dynamic Image extension > (http://github.com/narced133/radiant-dynamic-image-extension) > I have a page with, say, 3 subpages and implement the following code > in the main page: > > > > > > I expect to see the title of each subpage in the given size, font > color and background color. > The thing that happens, though, is that only the title of the first > subpage appears in the correct size and colors. The other titles > appear in the size and colors defined as standards in my > environment.rb. > Seems that the tag attributes (size, color and background) are only > transferred for the first child. > > Any thoughts and comments are appreciated! > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
