[Radiant] Extensions repository
Hey guys, I was just wondering whether there should be a centralized extensions repo for tested-and-approved extensions? For now it seems that there are several working extensions on different places and svn repos. I think it would help to have them in one place. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Preview (extension?)
Alright, I just realized that Radiant needs (badly) a module/extension for previewing articles before publishing (mostly when using formatting filters). I haven't been following the list too close as of late, but is anyone working on this? Any code I can take a stab at? ___ Radiant mailing list Post: [EMAIL PROTECTED] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Mongrel Cluster vs. Apache-FCGI
Hi folks, I recently got my rails app to serve with a mongrel cluster with a balancer in front of it and Apache Proxying in front of that. That app used to run on rails-Apache-FCGI straight and I really can't tell the difference performance-wise. Granted, the point of a cluster and balancer is for heavy loads not just one request, but there's a bit diminishing returns going on with low traffic websites (< 5K page views/week). Has any of you done any actual performance analysis on rails-mongrel cluster vs rails-apache-fcgi? Just curious. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Slicehost
Hey, To all folks who recommended Slicehost...thank you very much. It's is indeed what I was looking for. Excellent price-value deal. The flexibility of dedicated hosting @ shared hosting prices. My customer will now be a lot less wary about hosting. Oh yeah and running a Mongrel cluster in the slices is easy as cake (if you know what you're doing). Peace. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant Digest, Vol 12, Issue 53
Thanks a lot for the info guys. Seems SliceHost is the way to go. Will talk to the client, see if this seems acceptable to them. Best, Ruben On 3/28/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Send Radiant mailing list submissions to > radiant@lists.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: Hosting Companies (Kevin Ansfield) > > > -- > > Message: 1 > Date: Wed, 28 Mar 2007 12:09:14 +0100 > From: "Kevin Ansfield" <[EMAIL PROTECTED]> > Subject: Re: [Radiant] Hosting Companies > To: radiant@lists.radiantcms.org > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="utf-8" > > You can add my vote for slicehost too. Very solid and reliable from my > experience, definitely no overloaded servers and it's really simple to set > up new slices or rebuild them. > > Kevin > > > On 3/28/07, Sander de Goeij <[EMAIL PROTECTED]> wrote: > > > > Wow, Slicehost looks really interesting. Thanks for the heads up! > > > > -- > > Sander de Goeij > > [EMAIL PROTECTED] > > ___ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > > -- next part -- > An HTML attachment was scrubbed... > URL: > http://lists.radiantcms.org/pipermail/radiant/attachments/20070328/88b0b264/attachment-0001.htm > > -- > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > End of Radiant Digest, Vol 12, Issue 53 > *** > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Hosting Companies
Hello folks, I recently signed a customer and they were terrified to know that their Rails app was going to be hosted on the hosting co whom with I do most biz (don't wish to mention who they are). NowI've heard SliceHost and MediaTemple are really good...I'd like to know if any of you has an account with them and if you've had any problems with either of them? Your answers are much appreciated. Best, Ruben ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] 0.5.2 -- Setup and design
Alright...Radiant (and its mailing list) has been gathering so much interest that I'm switching my subs to digest mode -- in case I don't respond immediately. On 1/29/07, John W. Long <[EMAIL PROTECTED]> wrote: > Andrew Klein wrote: > > Still getting a hang of this all and just looking for some > > input;insight. I've been running a fairly simple design of Radiant > > (Read: almost source) and want to expand the design a little. Here is > > kind of what I want to do: > > > > - Home (Shows either just News or all of the heading, > > chronilogically) > > -- > > --- News > > --- Articles > > --- Tutorials > > -- Downloads > > -- Gallery > > -- RSS (Covers chronologically the news/articles/tutorial tree) > > --- RSS > > > > I just need some insight on how to do the RSS feeds. Also, curious if > > you could include 'categories' somehow or 'tags' for each Sub under all > > the categories. > > Presently, there is not an easy way to provide a list of articles from a > tree. You can list a page's immediate children with the > tag, but you will probably need to create a custom tag if you want to > display an entire branch of a tree. > > > As well, wondering if there is plans for a commenting system. > > Commenting is scheduled to be incorporated in the release following the > next release. The focus of the next release is the extension system. The > focus of the following release is blogging. > > I believe Sean Cribbs has done some work on a commenting extension. > > -- > John Long > http://wiseheartdesign.com > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Mailer Behaviour Error
Is this in development mode? Rails might be caching your yml file if you're working on production mode. On 1/26/07, Oliver Coningham <[EMAIL PROTECTED]> wrote: > My config part is at follows: > > mailers: >contact: > subject: Contact Form > from: [EMAIL PROTECTED] > redirect_to: /contact/thank-you/ > recipients: >- [EMAIL PROTECTED] > > But it doesn't seem to make any difference to the subject line? > > Sean Cribbs wrote: > > Oh, I see what you mean. Use the subject: line in your 'config' part, > > just > > as you do for the from, recipients, etc. > > > > Sean > > > -- > Posted via http://www.ruby-forum.com/. > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Ordering of pages
Anton,
Even though Radiant has evolved fairly quickly, the fact is that it is
a work in process which, in turn, means that many times people have to
hack their work-arounds to get stuff working the way they want. So, if
there's a specific task that you cannot concieveably accomplish with
existing tags, then you will HAVE TO write your own custom tags (i.e.
Ruby coding).
By field is meant a database field. Fields can also be though as the
columns in a database table. So, for example, you have a table with
the following structure:
id|name|children|parent
where id, name, children and parent are fields (columns).
Now let's say that you want to get all the list of children sorted
alphabetically, descending by name, you would write something like
(sql):
SELECT children FROM tablename ORDER BY name DESC;
or with the super easy Radius tags you would write something like
#do stuff here ... useful stuff preferably
P.S.: someone please check this for accuracy as I have not slept a
wink in the last couple of days/nights.
On 1/26/07, Anton Aylward <[EMAIL PROTECTED]> wrote:
> Sean Cribbs said the following on 01/26/2007 08:08 AM:
> > You can order by any field on the 'pages' table/ Page model.
>
> Right.
> I see that in the documentation, but beyond 'title' and when it was
> published, what constitutes a "field"? I really don't want to pour
> backwards and forwards though the code - this out to be documented!
>
> Can the existence of a page part (the tab when editing like 'sidebar' or
> 'extended') or its content be used? If I have one called 'current' can I
> percolate that to the top? If I have one called "order" in each of the
> pages can I use its content to sort?
>
> > Give the
> > 'order' attribute which direction you want to order it in ('asc'/'desc')
> > and the 'by' attribute the field you want to order on.
>
> Yes, that asc/desc is clearly documented. But the 'by' remains confusing.
>
> > For your other situation, you'll probably have to create your own tag
> > definition (to order by something that's in a part/tab).
>
> In English, does that mean I have to write Ruby code to do this?
>
> > There has been
> > some work in the past on adding an arbitrary ordering to Radiant with
> > acts_as_list.
>
> I suspect you and I use the word 'arbitrary' slightly differently :-)
> What I'm thinking of isn't at all arbitrary, its quite strictly controlled.
> And I'm really surprised that better ordering of the children isn't an issue.
>
> Of course I may just be completely misunderstanding what you mean by
> 'field'. But as I say, it doesn't grab me in the documentation or the code
> for
>
> I hope that there is something in there and Its just that I don't understand
> what you mean by 'field'.
>
> > If this is an increasingly requested feature and the
> > implementation and case for it is solid, it might be added. However,
> > features need to have a real pressing need before they are added, generally.
>
> I do understand about time and resource constraints! Oh boy, yes!
>
> /a
>
>
>
>
>
> ___
> Radiant mailing list
> Post: Radiant@lists.radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] API through XML-RPC (was: Re: JS-free view ? (newcomer))
Boris, XML-RPC would be great. I don't know the innards of Radiant (mental) enough to give a definitive answer, but if it can be done, it would give Radiant tremendous flexibility. On 1/25/07, Boris <[EMAIL PROTECTED]> wrote: > "John W. Long" <[EMAIL PROTECTED]> writes: > > > Boris wrote: > > [...] > > >> So how could I bypass the admin view requiring JS ? Is there a way to > >> manage content offline ? > > > > 1. You can create and submit patches to repair the current implementation. > > > > 2. You can create an extension which provides a text-browser friendly > > version of the admin. > > I finally think that a good solution would be to provide an API > through XML-RPC, like others already do. This would be real > luxury:-). Maybe it's non-trivial, but at least I won't be alone to > use it... so hopefully not alone for achieving it! > > What do you think about that? > > Thanks, > -- > Boris Daix > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Food for thought
Andrew, You're right. However, I think the efforts (or intentions thereof) are out there. I started messing with the quick start page, sadly I really haven't had the time to finish even though have every intention to do so. Some people have already turned useful mailing lists post into proper Wiki entries. So I think the intention is there is just that I'm assuming most of us have busy lives that forbid us from spending couple of hours writing and re-arranging and so forth. Forums are the proberbial double-edge sword. In concept it sounds like a great idea; however in practice, forums require a lot of attention and time. Have seen way too many times forums turning into boxing rinks. I've also seen forums turned into SPAM post galore and e-mail harvesters paradise. Yes they can and are very useful, but John and/or someone he chooses would have to be lurking around making sure things roll smothly. Yes the documentation needs to be improved and yes communication *could* be improved; however, I'm not sure forums are the solution. IMO On 1/20/07, Andrew Klein <[EMAIL PROTECTED]> wrote: > Hey all! > > You're all probably getting annoyed with hearing from me by this point. > However, I may have some suggestions pertaining not directly to Radiant > itself but moreso better communications. > > I find that maillists are great for the most part for keeping in contact > with people, clients, members and so forth and to have linear > conversations that may not be pertinent down the road. One benefit with > Radiant's mailgroup setup is that you can search the history of the > mailgroups. > > However, speaking from someone who has developed applications in a group > setting as well as now being a new adopter of a package developed as a > group, I'm starting to see that mailgroups and their lack of continuity > and constraint of 'flow' in a linear message-by-message system, the lack > of ability to review a group of messages discussing the same topic > quickly and even moreso difficult when you toss in the fact when people > change the subject of a line of messages making searching impossible. > > My first suggestion is a decent way of communicating. I know you may all > groan when I say 'forums', but right now the forums may be the best > option to manage this level of communications effectively. I'm sure it > would significantly reduce 'reasking' (like I'm sure I did with my last > email), hunting for links, tracking suggestions and more. I feel that > with the level of emails coming through the group and the great expanse > they cover, that forums would be far more logical, not only for now, but > for the future and ability to track what has been discussed in the past. > > My second suggestion is the wiki being more actively maintained by not > just developers, but the community as well. It is a much more logical > way to maintain an online 'manual' of sorts where people can place more > and more documentation for the benefit of the users and developers > alike. While I feel that the wiki was a great addition; the > implementation is not being carried through by all. > > I hope I am not over-stepping my boundaries; after being on this group > for a few weeks now, stomping around the site looking for more > information on expanding, these are the feelings I felt myself. I love > this system; it's the first CMS I've actually enjoyed messing with. I > can be as simplistic or detailled as I want to be and makes it easy to > maintain as well. I am a fan of Ruby and Ruby on Rails, which makes > this system that much more enjoyable to use. I just do not want to see > Radiant go downhill and would like to help however I can. > > Thank you for listening to my opinion :) > > Andrew > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Ruby/Rails Conference
Bryan and Marty, Thanks a lot for your input. As I said, I already convinced my employer to send me to either of those. I'd love to attend Rails Edge with Dave Thomas & Co. but it's too close--datewise. I'll probably head to Oregon to RailsConf as it sounds pretty interesting as well. On 1/19/07, Marty Haught <[EMAIL PROTECTED]> wrote: > > I was able to convince my employer to pay for me to attend either > > RailsConf or RubyCon or Rails Edge (even though we're a .Net shop with > > no plans to deploy Rails anytime soon). Have any of you attended any > > of them and can would you suggest attending one? > > I attended all three. It really depends on what you're looking to get > out of the conference. If you want to improve your skills with Rails > and Ruby, I'd suggest Rails Edge especially if someone is footing the > bill. I like all three for different reasons and will attend both > RailsConf 2007 and RubyConf 2007 on my own dime. > > Cheers, > Marty > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] What about...
Adam, I recently made a post in the same vein. And I would agree that while not copying, per se, is sometime worth looking into more mature products. As a pragmatic person, I don't believe in re-inventing the wheel, just perfecting it, thus, I think Radiant should at least consider looking into existing solutions and approaches instead of trying to figure out stuff as we go--but that's up to all the developers and, more importantly, John. On 1/19/07, Adam Salter <[EMAIL PROTECTED]> wrote: > This might come across as sacrilege but I recently installed Drupal 5.0. > I would suggest that everybody here do the same... It's got a lot > going for it in terms of CMS functionality. I'm personally looking > for something in between Radiant and Drupal... But the main point is > that the configuration/admin interface is 'kick ass', and that's > without any exaggeration. > > It might be worth taking a few pointers from their admin interface. I > find the current Radiant one a bit cumbersome. On the flipside, I > find the Drupal "content creation" interface very cumbersome - so > that's why I say I'm looking for something in between. > > Perhaps the Drupal goals and Radiant goals don't see eye to eye, but > I don't see anything wrong with learning from another's success. > > On 18/01/2007, at 10:51 AM, Brian Gernhardt wrote: > > > > > On Jan 17, 2007, at 6:05 PM, Daniel Sheppard wrote: > > > >> Yes, but I thought we were talking about the problem that using a > >> config > >> page part is too complicated and error-prone for an end user. > >> > >> If it's meant for a developer to change, hard code it, and tell > >> developers to change it if they need to. If it's meant for an end > >> user > >> to change, go the extra mile and give them a proper interface to > >> change > >> it. > > > > And my message was a plea to keep the config page part around or > > something at least as simple to use from a development point of view > > (only a couple lines of code to use, at most). A config page part > > may be too error-prone for complex uses, but is perfect for the > > simple ones. It's also great for testing an extension before it gets > > released. I simply find it too useful, and I'd probably end up > > making an extension to add it back in if it was removed. > > > > Unless a generic configuration system is added, the need to write a > > configuration interface for every simple plugin would limit my > > interest in developing for Radiant. If a particular extension is > > having problems, then fix it to have a better interface. But don't > > remove something that's working because it doesn't work in some cases. > > > > For an example of where it's great is the VirtualDomainsBehavior, as > > I mentioned. It's not hard to explain what the following config part > > means and I don't see a compelling reason to write a custom interface > > for it because of the limited usage it gets: > > > > - 8< - > > dev.example.com: development > > example.org: non-profit > > *: main > > - 8< - > > > > However, a good argument can be made that a central configuration > > system would be a good thing for Radiant to have. It would allow for > > a consistent interface across all extensions. The extension could > > provide a set of global variables and types that would be available > > from either the extensions page or a new page dedicated to the task > > (good if we add configuration for Radiant there too), and Page types > > could provide a set of variables for each page. It would keep > > developers from having to design a completely custom interface for > > each extension, which is horribly confusing for the users. > > > > But until that exists, let me use my config page part! > > > > ~~ Brian > > > > P.S. I haven't eaten today, so I apologize for any incoherence. > > ___ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Ruby/Rails Conference
Hey guys, I was able to convince my employer to pay for me to attend either RailsConf or RubyCon or Rails Edge (even though we're a .Net shop with no plans to deploy Rails anytime soon). Have any of you attended any of them and can would you suggest attending one? Thx. P.S.: Didn't post this in either Rails or Ruby-lang's mailing list because I didn't want to get like 1 responses our of which 9 are people fighting each other. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Mental Branch Revision?
Daniel, Could not agree the more. It's a step many people either skip or give for granted. Before you do any kind of migration you MUST back up all the DB, and all the radiant 0.5.x files your site is currently using. In fact, unless you are tinkering with a testing/dev intall, you need to make backups before you mess with any file and/or the DB. Best, Ruben On 1/19/07, Daniel Sheppard <[EMAIL PROTECTED]> wrote: > 0) backup the entire site dir + database incase it breaks anything > > > 1) do an svn:co into my site directory (which will put all the > > radiant/rails 1.2 pre release over the old generated radiant rails > > app). > ... > > Right? > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Custom Tags and Code reuse
Nice Wiki entry, Michael. I'm sure it'll come handy soon to many of us. If not for the navigation tag itself, but for the tag customization. On 1/17/07, Michael Jones <[EMAIL PROTECTED]> wrote: > I added a wiki HowTo that contains some of the great information I got > on this thread about the 'Navigation Tag'. > > Thanks again for you great indepth explanations Sean. And for a great CMS > John. > > http://dev.radiantcms.org/radiant/wiki/HowToUnderstandNavigationTagCode > > Cheers- > Michael > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] What about...
That does not sound bad at all. Simply set the config files as a Ruby class set all the values in a hash table (though it would be nice if we standarize nomenclature and so forth). Though I don't know if that scheme would still suffer from page-specific problems. On 1/17/07, Adam Williams <[EMAIL PROTECTED]> wrote: > On Jan 17, 2007, at 2:29 AM, Erik van Oosten wrote: > > > Another option is to simply use Ruby in configuration files. > > This would get my vote. > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] What about...
Can we store these settings in a table in the DB with a page_id foreign key? Wouldn't that circumvent the page-specific problem? We could agree upon a string format for the settings (i.e. comma separated, pipe "|" separated etc) to be stored in. The schema would look something like this: id | page_id | extension_id | settings | -- 1 5 1 userName|pass|port|protocol On 1/16/07, Sean Cribbs <[EMAIL PROTECTED]> wrote: > That's the thing, though. Page#config renders the 'config' part and > then parses the YAML from it. > > > What happened to Page#config()? I'd use that because it allows you to > > change the configuration of an extension through the admin interface. > > Of course, it has it's limitations. But I would rather try to find a > > solution to these issues than relying too heavily on > > file-system-level-config files. > > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] What about...
Sean, For instance the config for the Mailer beahvior is a candidate but I'm talking in general (i.e. any extension built that does require some user settings). It does not have to, but it seems to me, from the user's POV that having "platform-independent" format would make life much easier. In fact, even the database.yml file gave me a few problems (even using the venerable vim) because of spacing. Of course, the database.yml config file is "internal" to RoR (right?) so it can't be easily substituted with an XML file. Again, these are just ideas (probably not well thought out) to consider that could make Radiant more accessible to everyone who wishes to try it out. On 1/16/07, Sean Cribbs <[EMAIL PROTECTED]> wrote: > Ruben, > > What configuration needs are you thinking of? > > Sean > > Ruben D. Orduz wrote: > > It seems that many of the problems with extensions that require some > > sort of config file are due to cross-platform treatment of text > > (speacially \s and \t). Wouldn't it make sense to use > > not-so-space-sensitive XML files instead of the beloved yml? I know > > that a big faction of Ruby/Rails users squeel at just the thought of > > an XML, but really, it's about pragmatics? So would it be that bad an > > idea to use XML files for config stuff? Just wondering. > > ___ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] What about...
It seems that many of the problems with extensions that require some sort of config file are due to cross-platform treatment of text (speacially \s and \t). Wouldn't it make sense to use not-so-space-sensitive XML files instead of the beloved yml? I know that a big faction of Ruby/Rails users squeel at just the thought of an XML, but really, it's about pragmatics? So would it be that bad an idea to use XML files for config stuff? Just wondering. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Custom Tags and Code reuse
Michael, Anyone can open a Wiki account. If you don't find a good home for the text, then you can create a page (it will be at the discretion of John wether to leave it or remove it). On 1/16/07, Michael Jones <[EMAIL PROTECTED]> wrote: > > Hmmm this smells like and looks like a great candidate for the > > Wiki...or is it just me? > > Yeah I agree, Sean has written up some pretty good stuff. I'll be > happy to wikify some notes on this once I figure it out. > > Are wiki accounts open to anyone or do I need to get some account info > in order to post? Any special area this should be placed? > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Custom Tags and Code reuse
Hmmm this smells like and looks like a great candidate for the
Wiki...or is it just me?
On 1/16/07, Sean Cribbs <[EMAIL PROTECTED]> wrote:
>
> > I must be missing it, I don't see an expand method anywhere other than here:
> > http://radius.rubyforge.org/classes/Radius/TagBinding.html#M11
> >
> Ok, looks like I'll have to explain in more detail. For reference, I'm
> looking at
> http://dev.radiantcms.org/radiant/browser/branches/mental/radiant/app/models/standard_tags.rb#L461
> .
>
> The second line inside the tag definition, line 463, calls
> 'tag.expand'. This causes any tags nested inside (in the page, mind
> you) to be rendered/evaluated. The tags usually nested inside
> are listed starting at line 489. Here's their definitions:
>
> [:normal, :here, :selected, :between].each do |symbol|
> tag "navigation:#{symbol}" do |tag|
> hash = tag.locals.navigation
> hash[symbol] = tag.block
> end
> end
>
> This generates tag definitions for everything in that array in the first
> line of the snippet. So, for each one, we grab the
> 'tag.locals.navigation' that was assigned by the *parent tag*
> (originally blank), and assign the hash key associated with this tag to
> the tag block. So essentially, you're passing a block/closure/proc back
> to the parent tag that can be evaluated contextually (multiple times).
>
> So here's an overview, again:
>
> 1) somewhere in your page invokes the tag definition.
> 2) We assign a blank Hash to tag.locals.navigation (and also,
> incidentally, to a local var called 'hash' -- all variables are just
> references/by-reference in Ruby, so they're really the same object)
> 3) We evaluate the contained block inside by calling
> tag.expand
> 3.5) Each contained tag of 'normal', 'here', 'selected', 'between'
> assigns its contained block to a key in tag.locals.navigation for future
> evaluation.
> 4) evaluation continues -- parsing the urls/titles,
> evaluating various of the passed blocks on each one, depending on URL,
> then joining them together for output.
>
> Let me know if I can clear anything else up.
>
> Cheers,
>
> Sean Cribbs
> ___
> Radiant mailing list
> Post: Radiant@lists.radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Release of how to set up on DreamHost the proper way coming
Well, if you insist in intalling from gem, then I suggest you first set Radiant in *development* mode, and kill all FGCI/Rails/Ruby pocesses associated with Radiant. a good way is to run the command "top" in the shell and see which FCGI/Rails/Ruby are owned by Radiant. Then very ungracefully kill them (kill -9 pid). Once you've killed all related pid's, then fix whatever you need to fix and then point your browser to our Radiant install. I cannot emphasize enough how easy it was to install from source though. On 1/16/07, Andrew Klein <[EMAIL PROTECTED]> wrote: > Yes I am. Had to check myself to make sure. :) > > This DreamHost thing is whoppin' my butt. I got radiant --unpack working > fine with a buncha small changes, but without --unpack, it refuses to > run. The error is as such: > > /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:18:in > `require__': no such file to load -- bluecloth (MissingSourceFile) > > It picks up Radiant and everything now, but when I try the bluecloth mod > as desribed on the Wiki, no luck. Doesn't seem to make a lick of > difference, no matter where I put that. I don't know what would make the > unpack and the instance version is any different really (Looking through > it all. Tons of sifting) > > Thanks again! > > Ruben D. Orduz wrote: > > Andrew, > > > > Are you running on production mode? > > > > On 1/16/07, Andrew Klein <[EMAIL PROTECTED]> wrote: > > > >> Okay. Got the fix started. Here's the problem (Again) -- It nags that > >> bluecloth does not exist. I've dropped bluecloth.rb in RAILS_ROOT, no > >> avail. vendor/, nope. vendor/plugins/, nope again. GEM_PATH, nope again. > >> Can't access GEM_HOME. I've ran out of ideas. radiant and radius is > >> seen, as is everything else. Just not seeing bluecloth. My previous fix > >> by tossing bluecloth into RAILS_ROOT isn't working now. Ideas? > >> > >> Just as an FYI, I've tossed the following two lines into my dispatch.cgi > >> and dispatch.fcgi. No luck: > >> > >> ENV['GEM_HOME']='/usr/lib/ruby/gems/1.8' > >> ENV['GEM_PATH']='/usr/lib/ruby/gems/1.8:/home/bladedthoth/.gems' > >> > >> It made it so that ruby would see my gem folder. > >> > >> Ideas on how to make radiant see bluecloth? > >> > >> Andrew Klein wrote: > >> > >>> May have a fix for this: Waiting for my backup site to come online on > >>> DreamHost. DreamHost's DNS servers seem to be having issues ATM again. > >>> > >>> BladedThoth > >>> ___ > >>> Radiant mailing list > >>> Post: Radiant@lists.radiantcms.org > >>> Search: http://radiantcms.org/mailing-list/search/ > >>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant > >>> > >>> > >>> > >> ___ > >> Radiant mailing list > >> Post: Radiant@lists.radiantcms.org > >> Search: http://radiantcms.org/mailing-list/search/ > >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant > >> > >> > > ___ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Release of how to set up on DreamHost the proper way coming
Andrew, I *HIGHLY* suggest you install from source. Will make your life much easier. On 1/15/07, Ruben D. Orduz <[EMAIL PROTECTED]> wrote: > Andrew, > > Are you running on production mode? > > On 1/16/07, Andrew Klein <[EMAIL PROTECTED]> wrote: > > Okay. Got the fix started. Here's the problem (Again) -- It nags that > > bluecloth does not exist. I've dropped bluecloth.rb in RAILS_ROOT, no > > avail. vendor/, nope. vendor/plugins/, nope again. GEM_PATH, nope again. > > Can't access GEM_HOME. I've ran out of ideas. radiant and radius is > > seen, as is everything else. Just not seeing bluecloth. My previous fix > > by tossing bluecloth into RAILS_ROOT isn't working now. Ideas? > > > > Just as an FYI, I've tossed the following two lines into my dispatch.cgi > > and dispatch.fcgi. No luck: > > > > ENV['GEM_HOME']='/usr/lib/ruby/gems/1.8' > > ENV['GEM_PATH']='/usr/lib/ruby/gems/1.8:/home/bladedthoth/.gems' > > > > It made it so that ruby would see my gem folder. > > > > Ideas on how to make radiant see bluecloth? > > > > Andrew Klein wrote: > > > May have a fix for this: Waiting for my backup site to come online on > > > DreamHost. DreamHost's DNS servers seem to be having issues ATM again. > > > > > > BladedThoth > > > ___ > > > Radiant mailing list > > > Post: Radiant@lists.radiantcms.org > > > Search: http://radiantcms.org/mailing-list/search/ > > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > > > > > > ___ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Release of how to set up on DreamHost the proper way coming
Andrew, Are you running on production mode? On 1/16/07, Andrew Klein <[EMAIL PROTECTED]> wrote: > Okay. Got the fix started. Here's the problem (Again) -- It nags that > bluecloth does not exist. I've dropped bluecloth.rb in RAILS_ROOT, no > avail. vendor/, nope. vendor/plugins/, nope again. GEM_PATH, nope again. > Can't access GEM_HOME. I've ran out of ideas. radiant and radius is > seen, as is everything else. Just not seeing bluecloth. My previous fix > by tossing bluecloth into RAILS_ROOT isn't working now. Ideas? > > Just as an FYI, I've tossed the following two lines into my dispatch.cgi > and dispatch.fcgi. No luck: > > ENV['GEM_HOME']='/usr/lib/ruby/gems/1.8' > ENV['GEM_PATH']='/usr/lib/ruby/gems/1.8:/home/bladedthoth/.gems' > > It made it so that ruby would see my gem folder. > > Ideas on how to make radiant see bluecloth? > > Andrew Klein wrote: > > May have a fix for this: Waiting for my backup site to come online on > > DreamHost. DreamHost's DNS servers seem to be having issues ATM again. > > > > BladedThoth > > ___ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] POLL: Upgrading Unpacked Radiant Applications
Hm.. Hm. (grooming the goatee, now rolling my hypothetical mustage a la Dali)errcould we add to the backlog a poll behaviour to Radiant? (nudge, nudge, wink, wink). On 1/15/07, Ruben D. Orduz <[EMAIL PROTECTED]> wrote: > Ditto Giovanni. > > >On 1/15/07, Giovanni Intini <[EMAIL PROTECTED]> wrote: > > Source / No / No > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] POLL: Upgrading Unpacked Radiant Applications
Ditto Giovanni. >On 1/15/07, Giovanni Intini <[EMAIL PROTECTED]> wrote: > Source / No / No ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Sticky Posts
Huh huh...very, very, very interesting Daniel. Don't know if you saw my other post regarding this issue, but in essence I "cheated" and didn't mess with mental branch at all. I basically created a column in the pages table called "is_featured" of type tinyint (I only want 1||0), default 0. Then I used the tag and used the "by=columnName" argument to retrieve the latest post marked as featured. Then hacked a checkbox in the admin interface that sets an article as being featured. On 1/15/07, Daniel Sheppard <[EMAIL PROTECTED]> wrote: > > > If you're willing to play with the mental branch, I've done something > similar in my extension that I'm working on for the website I'm working on - > The main page will always have a feature article that might not necessarily > be the latest article - it will simply be the most recent article marked as > a 'feature'. > > Poke around > http://soxbox.no-ip.org/radiant/svn/extensions/x_groggy/ > - there's heaps of other crap in there, but mainly you just want to look at > the article_page.rb, article_metadata.rb and the articles:feature and > articles:each tags in lib/groggy_tabs.rb. I haven't added in the bit to > actually SET that flag, but it'll just be a check-box on the article editing > page. > > Dan. > > > > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Ruben D. Orduz > Sent: Tuesday, 14 November 2006 3:28 AM > To: radiant@lists.radiantcms.org > Subject: [Radiant] Sticky Posts > > > Hey guys (I know...I should be debugging .Net code...I'm a bad employee), > > What's would be the most painless way to add a "sticky" behavior to posts? > For example..something I wish to remain in the front page in spite of its > publishing date. Any help is much appreciatedJose...if I can get a few > more minutes off, I'll look into the routes.rb file and let you know which > lines I'd be messing with :) > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: > http://lists.radiantcms.org/mailman/listinfo/radiant > > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Release of how to set up on DreamHost the proper way coming
Andrew, I'll be interested in giving that a read. I have an account with them and am surprised so many people have had problems installing Radiant there. Maybe my experience is an anomaly, but I was up and running with Radiant in about 5-7 minutes. On 1/15/07, Andrew Klein <[EMAIL PROTECTED]> wrote: > This is my first post here, so bear with me. :) > > I felt, as since there has been previous interest and current interest, > and that current 'methods' of this are not working AT ALL. *shiver* I > spent a few days fighting to get Radiant running; it is exactly what I > need; I hate PHP CMS setups (mostly cause they are unwieldy at best,) > and other CMSs (Ruby and otherwise) do not fit my needs well. Granted > Radiant doesn't fit it perfectly, it does pretty good. > > Anyways, off topic; as since all the other sites (not JUST Radiant's) > for setup on Dreamhost are incorrect (Some of them are so far off it's > pathetic,) I am assembling a set of instructions on proper setup (And > moreso especially FastCGI support -- Evil to work with, to say the > least) and will be releasing them within the week. > > As well, I may assemble a tarball for an unpacked site as since I'm not > overly graceful with the setup of this package yet that people can just > tar -xvf it and follow a much shorter set of instructions. For this, it > would be nice to see if someone else is on a different Dreamhost server > to test this idea (IE:- ruby/etc in same location on each server) > > Anyways, cheers all! > BladedThoth > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Typo3 instead of Radiant?
Hey guys, @John, I totally understand because I myself only get to tinker with Rails/Radiant for one or two hours a day max (living to make, son & wife at home). Just wanted to bring up attention to some outstanding issues that I think need to be worked on. I, for one, will keep working on user roles and documentation in general. It would be cool if BJ can hack something out for the act_as_versioned and maybe the page-caching-retooling bloke (am terribly sorry guy, totally forgot your name) can help getting that working. I also totally understand the complexity of giving the option to download pages as PDF/PS/CSV(if it's a data-intensive page)...just something someone could take a stab at. On 1/14/07, John W. Long <[EMAIL PROTECTED]> wrote: > BJ Clark wrote: > > Just to throw my $.02 in, I agree with most of what Ruben says, > > especially with regards to MailerBehavior. > > The mailer behavior seems to have outlived it's usefulness. I definitely > agree that we need to do something better. > > > I also agree that user roles and the publishing system needs to be > > improved. I'm not talking about a total re-design but it would be nice > > to be able to change a page, view some sort of "draft" before it gets > > published, and then publish it if it was ok. Also, versioned pages > > would be VERY nice, and I wouldn't think it would be that difficult to > > implement with acts_as_versioned, but I've never tried. > > Send in the patches. > > > And then there is the documentation, which I plan to help with as soon > > as I get my site launched. > > That would be awesome. > > -- > John > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Typo3 instead of Radiant?
Sean, I love how you dismiss genuine claims. Am sure, because of posts in this list that several other people feel the same way I do. But whatever, it's your prerogative to keep thinking otherwise. On 1/14/07, Sean Cribbs <[EMAIL PROTECTED]> wrote: > Flamebait. RadiantUsers wiki page. PDI. That is all. > > Ruben D. Orduz wrote: > > This is not intended as a flame or to cause controversy, please don't > > take it as such. > > > > I just recommended a customer to adopt Typo3 instead of Radiant CMS, why? > > > > * Mailer Behaviour is shaky at best. > > * Print page to PDF/PS/CSV is not even completely supported by Rails. > > * User roles. > > > > Those were three of the most important things that they told me they > > needed. They're a small-ish (~15 people) company and are not planning > > in having huge traffic on their site or anything. However, I had to > > recommend the adoption of a CMS that is probably an overkill for what > > they need, but with Radiant and its extensions being in such a > > "puerile" stage, it's too much risk telling them to adopt it. > > > > The point I'm trying to drive home is that all of us that are in some > > way or another involved in the development of Radiant (whether the > > core, extensions, documentation, etc.) need to ramp up development of > > Radiant if we really want to make it a production-grade CMS. I believe > > for what I've read as of late that a whole lot of people is interested > > in helping out and I sense the time is ripe for John and whoever else > > leads Radiant to "manage" the momentum built up to help get this baby > > out the door. > > > > Sorry for soapboxing, but in closing I must echo the thoughts of a > > list contributor who said something to the effect that if a project > > stagnates for too long, it eventually fades away. > > ___ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Typo3 instead of Radiant?
This is not intended as a flame or to cause controversy, please don't take it as such. I just recommended a customer to adopt Typo3 instead of Radiant CMS, why? * Mailer Behaviour is shaky at best. * Print page to PDF/PS/CSV is not even completely supported by Rails. * User roles. Those were three of the most important things that they told me they needed. They're a small-ish (~15 people) company and are not planning in having huge traffic on their site or anything. However, I had to recommend the adoption of a CMS that is probably an overkill for what they need, but with Radiant and its extensions being in such a "puerile" stage, it's too much risk telling them to adopt it. The point I'm trying to drive home is that all of us that are in some way or another involved in the development of Radiant (whether the core, extensions, documentation, etc.) need to ramp up development of Radiant if we really want to make it a production-grade CMS. I believe for what I've read as of late that a whole lot of people is interested in helping out and I sense the time is ripe for John and whoever else leads Radiant to "manage" the momentum built up to help get this baby out the door. Sorry for soapboxing, but in closing I must echo the thoughts of a list contributor who said something to the effect that if a project stagnates for too long, it eventually fades away. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] 503 on Radiant site
Two words: *dedicated hosting*. If you don't have the cash for that, maybe open a donations account to pay for it--it's worth it...every penny of it. On 1/12/07, Sean Cribbs <[EMAIL PROTECTED]> wrote: > > I am also hosted on TextDrive and had issues. I think someone broke their > Apache config file. John, is radiantcms.org on "alberni" too? > > Sean > > Nathaniel Talbott wrote: > On 1/12/07, Michael Jones <[EMAIL PROTECTED]> wrote: > > > > Where did the site go? > > I'm getting a 503: > > http://radiantcms.org/ > http://dev.radiantcms.org/ > > Service Temporarily Unavailable > The server is temporarily unable to service your request due to > maintenance downtime or capacity problems. Please try again later. > > I shouldn't rag on the host since John's paying for it, not me, but, > um, yah. It's back up now. > > > > > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: > http://lists.radiantcms.org/mailman/listinfo/radiant > > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Translating Radiant: Looking for an Update
I concur with the notion that localization is of utmost importance for any project's success. I can help with translation to Spanish and Italian...just need the "platform" to do it. Of course, I need to finish helping with the Wiki as well :/ If I could only find the time. On 1/12/07, Jamie Wilkinson <[EMAIL PROTECTED]> wrote: > On Jan 11, 2007, at 8:06 PM, Ronny Hanssen wrote: > > > I was planning to submit a patch to the dev-masters when done. Now > > I am > > a bit sure if they really want it or not? > > I for one am very interested in seeing this in core! Localisation is > an essential feature > -j > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Password protection part of a radiant web site
Luigi, Yeah .htaccess will not work under litespped or lighthttpd, so John's suggestion probably won't work. And if the password protection of the extension relies on HTTP auth, then it probably won't work either. On 1/11/07, Luigi Rizzo <[EMAIL PROTECTED]> wrote: > Ruben D. Orduz wrote: > > What I don't get is how can he be running Radiant w/o an app folder > > inside RAILS_ROOT dir? I'm still puzzled about that one. Sensa una > > buona explicazione non puo fare niente. > > Hello Ruben. > > I installed radiant from a gem, and not as an application bu as an > instance. Here is what the installation dir has inside: > http://pastie.caboo.se/32595 > > (Note: the show_page.rhtml file in the "app/views/site" was added today) > > It seems to me the problem is with the HTTP Authentication part of the > password_protected behavior, which doesn't seem to happen ... (maybe > because of litespeed?). I'm using the latest behavior available and I > installed it as a plugin. > > Thank you for you assistance. > > L > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Password protection part of a radiant web site
What I don't get is how can he be running Radiant w/o an app folder inside RAILS_ROOT dir? I'm still puzzled about that one. Sensa una buona explicazione non puo fare niente. On 1/11/07, John W. Long <[EMAIL PROTECTED]> wrote: > Luigi Rizzo wrote: > > Hello. > > > > Is there any working solution made available by the radiant > > development/user community to password protect a part of a radiant-based > > web site? > > > > Unluckily it seems the password_protected behavior doesn't work with > > 0.5.2 (see below for the error I get) :( > > Probably the easiest thing to do is to setup basic authentication with > an apache .htaccess file. Would that work for you? > > -- > John Long > http://wiseheartdesign.com > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Password protection part of a radiant web site
Luigi, ho questo archivio "app/views/site/show_page.rhtml" in questo diretorio? On 1/10/07, Luigi Rizzo <[EMAIL PROTECTED]> wrote: > Hello. > > Is there any working solution made available by the radiant > development/user community to password protect a part of a radiant-based > web site? > > Unluckily it seems the password_protected behavior doesn't work with > 0.5.2 (see below for the error I get) :( > > Many thanks in advance! > > Luigi > > ActionController::MissingTemplate (Missing template > /usr/lib/ruby/gems/1.8/gems/radiant-0.5.2/lib/../app/views/site/show_page.rhtml): > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:1034:in > `assert_existence_of_template_file' > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:724:in > `render_file' > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:648:in > `render_with_no_layout' > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/layout.rb:245:in > `render_without_benchmark' > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/benchmarking.rb:53:in > `render' > /usr/lib/ruby/1.8/benchmark.rb:293:in `measure' > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/benchmarking.rb:53:in > `render' > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:942:in > `perform_action_without_filters' > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/filters.rb:368:in > `perform_action_without_benchmark' > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/benchmarking.rb:69:in > `perform_action_without_rescue' > /usr/lib/ruby/1.8/benchmark.rb:293:in `measure' > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/benchmarking.rb:69:in > `perform_action_without_rescue' > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/rescue.rb:82:in > `perform_action' > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:408:in > `send' > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:408:in > `process_without_filters' > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/filters.rb:377:in > `process_without_session_management_support' > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/session_management.rb:117:in > `process' > /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/dispatcher.rb:38:in > `dispatch' > /opt/lsws/fcgi-bin/RailsRunner.rb:12 > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] radisu tags
Sara, First...r yuo dsylxeic? j/k :) Second, I personally edit all pages inside Radiant (truly despise copy-and-paste) on a trial-and-error basis (on development mode so there's no page caching). Don't know of eclipse plug-ins for Radius tags. Go Gators!!! On 1/8/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hello, > > I read allt eh documenation on the wiki, but I am still having some > problems with it. The main problem is that I use aptana + radrails to > do my pages, but currently I have to do it there and then past them in > radiatn and then test it to see if its right. I am wondering if there > is any IDE that understand radius tags or do you just do all your > pages inside radiant (you guys must be really good to do all your > html, java and radius tags ) Maybe if I know your workflow it would > help since right know I have a bunch of back and forth between aptana > and radiant. > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Admin using Internet Explorer 6
doing a file diff, amazingly (even to myself, after all the fiddling I
did) it seems the only two changes I did were:
#content table.fieldset td.label {
padding-top: 10px;
vertical-align: top;
>>> text-align: left;
width: 20%;
}
#content table.fieldset td.field .textbox {
>>> width: 75%;
}
On 1/6/07, Ruben D. Orduz <[EMAIL PROTECTED]> wrote:
> John, let me see if I can get the admin CSS I fiddled with in a more
> presentable form...I poked around it so much (trying to fix things in
> IE) that it looks (and is) very hocky-poky. If and when I do, I'll be
> sure to submit a ticket for it. Also, please accept my apologies for
> not finishing the Wiki, but I've been up to my nose @ work and @ home,
> have had little time to get these side projects done.
>
> As for Sara's problem it was a two-fold problem (which I believe it's
> fixed): 1)yml formatting and 2) file permissions. She still hasn't
> been able to fix her WEBrick server, but I think that has more to do
> with server config and not related to the app.
>
>
>
> On 1/6/07, John W. Long <[EMAIL PROTECTED]> wrote:
> > Ruben D. Orduz wrote:
> > > I once had those problems it has to do with IE6's CSS quirkiness. I
> > > had to fiddle with the stylesheet until I got a more desirable,
> > > cross-browser solution--it's not by any means perfect, but it looks
> > > much better in the IE family.
> >
> > Are the changes worth submitting as a patch?
> >
> > --
> > John Long
> > http://wiseheartdesign.com
> > ___
> > Radiant mailing list
> > Post: Radiant@lists.radiantcms.org
> > Search: http://radiantcms.org/mailing-list/search/
> > Site: http://lists.radiantcms.org/mailman/listinfo/radiant
> >
>
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Admin using Internet Explorer 6
John, let me see if I can get the admin CSS I fiddled with in a more presentable form...I poked around it so much (trying to fix things in IE) that it looks (and is) very hocky-poky. If and when I do, I'll be sure to submit a ticket for it. Also, please accept my apologies for not finishing the Wiki, but I've been up to my nose @ work and @ home, have had little time to get these side projects done. As for Sara's problem it was a two-fold problem (which I believe it's fixed): 1)yml formatting and 2) file permissions. She still hasn't been able to fix her WEBrick server, but I think that has more to do with server config and not related to the app. On 1/6/07, John W. Long <[EMAIL PROTECTED]> wrote: > Ruben D. Orduz wrote: > > I once had those problems it has to do with IE6's CSS quirkiness. I > > had to fiddle with the stylesheet until I got a more desirable, > > cross-browser solution--it's not by any means perfect, but it looks > > much better in the IE family. > > Are the changes worth submitting as a patch? > > -- > John Long > http://wiseheartdesign.com > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Admin using Internet Explorer 6
Todd, I once had those problems it has to do with IE6's CSS quirkiness. I had to fiddle with the stylesheet until I got a more desirable, cross-browser solution--it's not by any means perfect, but it looks much better in the IE family. On 1/6/07, Todd McGrath <[EMAIL PROTECTED]> wrote: > Hi, > > I'm using the /admin site in IE 6 today and see a couple things when creating > or > editing pages- > > * the page part "popups" load at the bottom of the page beneath all other > content (not like firefox where it's on top of the other content in the middle > of the page) > > * The fields under the more/less link are not the same size and aligned > differently. > > Is this a known issue? I've searched the mailing lists but I'm not coming up > with anything relevant to the two issues above. > > > Todd > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] installing on Ubuntu
John, will do. I'm almost certain it has to do with formating (spacing/tabs) of her DB config files. On 1/4/07, John W. Long <[EMAIL PROTECTED]> wrote: > Ruben D. Orduz wrote: > > Sorry to hear you're having such a hard time getting Radiant to work. > > You can write me directly if you want, so we don't bother the rest. > > If you continue off list, please post the solution here. It's helpful > when people are searching through the archives for the same problem in > the future. > > -- > John Long > http://wiseheartdesign.com > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] installing on Ubuntu
Sara, Sorry to hear you're having such a hard time getting Radiant to work. You can write me directly if you want, so we don't bother the rest. I need to know the following: * Are you sure mysqld is running? * Are you developing on windows? * Can you copy and paste both your db yml file and the db setup script? ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] installing on Ubuntu
Sara, Other people have had problem with yml files since they ARE tab- and space-sensitive. Make sure you're editing them in a text-safe environment and that there's no cross-OS problems. Also, you can try doing a SVN revert on that yml file and make sure you don't mess with the spacing or tabs. On 1/4/07, Sara <[EMAIL PROTECTED]> wrote: > All, > If I try that I get this > $ ruby script/setup_database production > Run `setup_database --help` for information on additional options. > > Loading production environment...FAILED > /usr/lib/ruby/1.8/yaml.rb:133:in `load': syntax error on line 7, col -3: > `test: (ArgumentError) > adapter: mysql > database: radiant_test > username: myusername > password: mypassword > > > production: > adapter: mysql > database: radiant_live > username: myusername > password:mypassword > ' from /usr/lib/ruby/1.8/yaml.rb:133:in `load' > from /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:459:in > `database_configuration' > from /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:181:in > `initialize_database' > from /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:84:in > `process' > from /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:42:in > `run' > from ./script/../config/environment.rb:15 > from script/setup_database:78:in `load_environment' > from script/setup_database:258:in `announce' > from script/setup_database:77:in `load_environment' > from script/setup_database:17:in `run' > from script/setup_database:9:in `run' > from script/setup_database:297 > [EMAIL PROTECTED]:/usr/lib/ruby/gems/1.8/gems/radiant-0.5.2$ ruby > script/server webrick -e production > => Booting WEBrick... > /usr/lib/ruby/1.8/fileutils.rb:243:in `mkdir': Permission denied - tmp > (Errno::EACCES) > from /usr/lib/ruby/1.8/fileutils.rb:243:in `fu_mkdir' > from /usr/lib/ruby/1.8/fileutils.rb:217:in `mkdir_p' > from /usr/lib/ruby/1.8/fileutils.rb:215:in `mkdir_p' > from /usr/lib/ruby/1.8/fileutils.rb:201:in `mkdir_p' > from /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/commands/server.rb:29 > from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:27:in > `require' > > from > /usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:147:in > `require' > from script/server:3 > > > > > On Thursday 04 January 2007 14:36, Chris O'Meara wrote: > > I believe I took the sample file and whacked the socket entry. > > > > On Jan 4, 2007, at 2:24 PM, Ruben D. Orduz wrote: > > > no host specified? Or did you purposely ommited it? > > > > > > On 1/4/07, Chris O'Meara <[EMAIL PROTECTED]> wrote: > > >> Here's what my database.yml looks like for my Radiant install on > > >> Unbuntu: > > >> > > >> production: > > >>adapter: mysql > > >>database: cr_radiant_live > > >>username: user > > >>password: password > > >> > > >> I'm running on SliceHost. My RAILS_ENV is production (obviously). > > >> > > >> Cheers, > > >> Chris > > > > ___ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] installing on Ubuntu
no host specified? Or did you purposely ommited it? On 1/4/07, Chris O'Meara <[EMAIL PROTECTED]> wrote: > Here's what my database.yml looks like for my Radiant install on > Unbuntu: > > production: >adapter: mysql >database: cr_radiant_live >username: user >password: password > > I'm running on SliceHost. My RAILS_ENV is production (obviously). > > Cheers, > Chris > > > On Jan 4, 2007, at 1:44 PM, Sara wrote: > > > All, > > > > i keep on getting the same error, I have no idea what might be > > going wrong > > since I managed to install both mephisto and RAM so I am lost as to > > what is > > going wrong. Loading production environment...FAILED > > /usr/lib/ruby/1.8/yaml.rb:133:in `load': syntax error on line 5, > > col 2: ` > > host: localhost' (ArgumentError) > > from /usr/lib/ruby/1.8/yaml.rb:133:in `load' > > from /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/ > > initializer.rb:459:in > > `database_configuration' > > from /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/ > > initializer.rb:181:in > > `initialize_database' > > from /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/ > > initializer.rb:84:in > > `process' > > from /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/ > > initializer.rb:42:in > > `run' > > from ./script/../config/environment.rb:15 > > from script/setup_database:78:in `load_environment' > > from script/setup_database:258:in `announce' > > from script/setup_database:77:in `load_environment' > > from script/setup_database:17:in `run' > > from script/setup_database:9:in `run' > > from script/setup_database:297 > > > > > > > > On Thursday 04 January 2007 12:53, Ruben D. Orduz wrote: > >> Sara, > >> > >> Indeed if you delete the socket line and use either 127.0.0.1 or just > >> plain ol' localhost works fine. > >> > >> On 1/4/07, Sara <[EMAIL PROTECTED]> wrote: > >>> Jim, > >>> > >>> Thanks so if I understand that correctly you deleted the sockets > >>> lines > >>> all together and instead wrote a > >>> host:127.0.0.1 instead? > >>> > >>> On Thursday 04 January 2007 12:42, Jim Herring wrote: > >>>> I'm running Dapper and had this problem too. What worked for me was > >>>> removing the socket lines from database.yml and using host: > >>>> 127.0.0.1 > >>>> instead. > >>>> > >>>> Hope that help! > >>>> > >>>> Jim > >>>> > >>>> On 1/4/07, Sara <[EMAIL PROTECTED]> wrote: > >>>>> Semt, > >>>>> I know I created a symlink to it and it still did not work and > >>>>> then I > >>>>> just deleted the link and just enter the /vr/run/ location and > >>>>> now I > >>>>> get the same > >>>>> eror just with that location > >>>>> $ruby script/setup_database production > >>>>> > >>>>> Run `setup_database --help` for information on additional options. > >>>>> > >>>>> Loading production environment...FAILED > >>>>> /usr/lib/ruby/1.8/yaml.rb:133:in `load': syntax error on line > >>>>> 5, col > >>>>> 2: ` socket:/var/run/mysqld/mysqld.sock' (ArgumentError) > >>>>> from /usr/lib/ruby/1.8/yaml.rb:133:in `load' > >>>>> from /usr/lib/ruby/gems/1.8/gems/rails-1.1.6 > >>>>> /lib/initializer.rb:459:in > >>>>> `database_configuration' > >>>>> from /usr/lib/ruby/gems/1.8/gems/rails-1.1.6 > >>>>> /lib/initializer.rb:181:in > >>>>> `initialize_database' > >>>>> from /usr/lib/ruby/gems/1.8/gems/rails-1.1.6 > >>>>> /lib/initializer.rb:84:in > >>>>> `process' > >>>>> from /usr/lib/ruby/gems/1.8/gems/rails-1.1.6 > >>>>> /lib/initializer.rb:42:in > >>>>> `run' > >>>>> from ./script/../config/environment.rb:15 > >>>>> from script/setup_database:78:in `load_environment' > >>>>> from script/setup_database:258:in `announce' >
Re: [Radiant] installing on Ubuntu
Sara, Indeed if you delete the socket line and use either 127.0.0.1 or just plain ol' localhost works fine. On 1/4/07, Sara <[EMAIL PROTECTED]> wrote: > Jim, > > Thanks so if I understand that correctly you deleted the sockets lines all > together and instead wrote a > host:127.0.0.1 instead? > > > On Thursday 04 January 2007 12:42, Jim Herring wrote: > > I'm running Dapper and had this problem too. What worked for me was > > removing the socket lines from database.yml and using host: 127.0.0.1 > > instead. > > > > Hope that help! > > > > Jim > > > > On 1/4/07, Sara <[EMAIL PROTECTED]> wrote: > > > Semt, > > > I know I created a symlink to it and it still did not work and then I > > > just deleted the link and just enter the /vr/run/ location and now I get > > > the same > > > eror just with that location > > > $ruby script/setup_database production > > > > > > Run `setup_database --help` for information on additional options. > > > > > > Loading production environment...FAILED > > > /usr/lib/ruby/1.8/yaml.rb:133:in `load': syntax error on line 5, col 2: ` > > > socket:/var/run/mysqld/mysqld.sock' (ArgumentError) > > > from /usr/lib/ruby/1.8/yaml.rb:133:in `load' > > > from /usr/lib/ruby/gems/1.8/gems/rails-1.1.6 > > > /lib/initializer.rb:459:in > > > `database_configuration' > > > from /usr/lib/ruby/gems/1.8/gems/rails-1.1.6 > > > /lib/initializer.rb:181:in > > > `initialize_database' > > > from /usr/lib/ruby/gems/1.8/gems/rails-1.1.6 > > > /lib/initializer.rb:84:in > > > `process' > > > from /usr/lib/ruby/gems/1.8/gems/rails-1.1.6 > > > /lib/initializer.rb:42:in > > > `run' > > > from ./script/../config/environment.rb:15 > > > from script/setup_database:78:in `load_environment' > > > from script/setup_database:258:in `announce' > > > from script/setup_database:77:in `load_environment' > > > from script/setup_database:17:in `run' > > > from script/setup_database:9:in `run' > > > from script/setup_database:297 > > > > > > anyone has any other ideas as to what could be wrong. > > > > > > Sara Vasquez > > > > > > On Thursday 04 January 2007 05:12, Andreas Semt wrote: > > > > Hi Sara, > > > > > > > > on my machine (Ubuntu 6.10 Edgy Eft) the value for 'socket:' > > > > (in 'config/database.yml') is set to: '/var/run/mysqld/mysqld.sock'. > > > > Hope that helps. > > > > > > > > > > > > Best regards, > > > > Andreas Semt > > > > > > > > Sara schrieb: > > > > > Hello, > > > > > > > > > > I am having problems installing Radiant on my ubuntu machine here is > > > > > > the > > > > > > > > output > > > > > > > > > > $ ruby script/setup_database production > > > > > Run `setup_database --help` for information on additional options. > > > > > > > > > > Loading production environment...FAILED > > > > > /usr/lib/ruby/1.8/yaml.rb:133:in `load': syntax error on line 5, col > > > > > > 2: ` > > > > > > > > socket: /tmp/mysql.sock' (ArgumentError) > > > > > from /usr/lib/ruby/1.8/yaml.rb:133:in `load' > > > > > from > > > > > /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:459:in > > > > > `database_configuration' > > > > > from > > > > > /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:181:in > > > > > `initialize_database' > > > > > from > > > > > /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:84:in > > > > > `process' > > > > > from > > > > > /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:42:in > > > > > `run' from ./script/../config/environment.rb:15 > > > > > from script/setup_database:78:in `load_environment' > > > > > from script/setup_database:258:in `announce' > > > > > from script/setup_database:77:in `load_environment' > > > > > from script/setup_database:17:in `run' > > > > > from script/setup_database:9:in `run' > > > > > from script/setup_database:297 > > > > > > > > > > I took a look at the file, but nothing seems to be wrong. Any help > > > > > > would > > > > > > > > be greatly appreciated > > > > > > > > > > > > > > > Sara Vasquez > > > > > ___ > > > > > Radiant mailing list > > > > > Post: Radiant@lists.radiantcms.org > > > > > Search: http://radiantcms.org/mailing-list/search/ > > > > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > > > > ___ > > > > Radiant mailing list > > > > Post: Radiant@lists.radiantcms.org > > > > Search: http://radiantcms.org/mailing-list/search/ > > > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > > ___ > > > Radiant mailing list > > > Post: Radiant@lists.radiantcms.org > > > Search: http://radiantcms.org/mailing-list/search/ > > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ > Radiant mailing list >
Re: [Radiant] Displaying a specific child's content
Not to toot my own horn, but that was explained in the Getting started wiki. BTW, John, I need to get back to finish that off...maybe this weekend if I can find the time. Best, Ruben On 1/3/07, BJ Clark <[EMAIL PROTECTED]> wrote: > I figured it out. > I was trying to pull a page that was 2 levels below where I was trying > to pull it from. > I had to call it by url="level1/pagename" > But that works just dandy. > Thanks all, > BJ > > On 1/2/07, Andreas Semt <[EMAIL PROTECTED]> wrote: > > @BJ, > > > > it works for me. The content tag is also described > > here: http://radiantcms.org/blog/2006/05/11/tag-primer/ > > > > The example says: > > --- > > → Content from the sidebar part of the page. > > > > The part attribute (shown above) allows you to specify which part of the > > page you would like to render. When used without a part attribute the > > content tag will render the "body" part. > > --- > > > > > > Best regards, > > Andreas Semt > > > > BJ Clark schrieb: > > > @Ruben, > > > I'm just trying to display the content of certain pages in other pages. > > > > > > @Andreas, > > > Are you sure this works for you? It's not putting anything in my page. > > > I don't get an error, but it doesn't do anything either. > > > > > > > > > Thanks 2 everyone, > > > BJ Clark > > > > > > On 1/1/07, Andreas Semt <[EMAIL PROTECTED]> wrote: > > >> @Ruben, > > >> > > >> perhaps it's necessary to code it this way: > > >> > > >> --- > > >> > > >> > > >> > > >> > > >> > > >> > > >> --- > > >> > > >> > > >> Best regards, > > >> Andreas Semt > > >> > > >> Ruben D. Orduz schrieb: > > >>> I suppose I misunderstood his question. I thought he wanted to know > > >>> how to access the content of a child page, but in retrospect, I > > >>> realize that he just wanted to show the actual content of a child page > > >>> somewhere else. I think the tag definitely helps, but I don't > > >>> know if it is able to bring specific parts of a child page or of it > > >>> will retrieve the content of the whole page. I guess he could play > > >>> with the DB and then do a ??? > > >>> > > >>> On 1/1/07, Andreas Semt <[EMAIL PROTECTED]> wrote: > > >>>> @Clark, > > >>>> > > >>>> --- > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> --- > > >>>> > > >>>> This includes the content of the page 'about' into your actual > > >>>> page. > > >>>> Alternative you could write '', because per default > > >>>> the body page part is shown (or you could include self defined > > >>>> page parts). > > >>>> > > >>>> > > >>>> Best regards, > > >>>> Andreas Semt > > >>>> > > >>>> BJ Clark schrieb: > > >>>>> Hello All, > > >>>>> I'm trying to display the content of a specific child page. > > >>>>> Is there anyway to do this via radius tags? > > >>>>> > > >>>>> I realize that I can do all children (or whatever) via > > >>>>> r:children:each or :first but I need to do :specificpage and I'm not > > >>>>> sure how that is done. > > >>>>> > > >>>>> Is there a way to do that? > > >>>>> Thanks, > > >>>>> BJ Clark > > ___ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Ideas for reimplementation of radiant caching
Dan,
It seems you have given this quite a bit of thought, and it could
work. I'm just worried about when will the ROI of performace hit make
it be worth.
Just as an anecdote, I've worked with paid enterprise-grade CMS's,
open-source CMS's and I've only seen two types of caching:
1) The classic: time expiry unless forced by hand.
2) Tag-level caching: You can choose which tags NOT to cache. So for
example, in a news site, pretty much the whole site could be cached,
except for content produced by <%breaking-news%>.
Maybe something like that could be adapted for Radiant (i.e. give the
choice which caching is desired).
On 1/1/07, Daniel Sheppard <[EMAIL PROTECTED]> wrote:
> I want radiant to have a more robust caching mechanism than the current
> 'expire every x minutes' method of doing things - I'd like it to be able
> to handle just removing things from the cache when things actually
> change. I've roughed out a plan on how I think this should be done in a
> safe manner.
>
> It sounds like it should work, but this is mainly just what I thought of
> on the way to work this morning - I'd like people to poke holes in it
> and figure out any edge-cases I'm missing out on - if this process EVER
> misses out on the clearing of a cached page, it's pretty much useless.
>
> I see a bit off overhead being added to the rendering process (since
> after_initialize hooks are a performance no-no), but since this should
> reduce the need for rendering by a huge amount, I'm hoping it'll balance
> out.
>
> I will probably put off an implementation of this until after I finish
> off my asset extension and get other things running, but I might pull
> this forward for asset caching as well... not sure yet.
>
> --
>
> Example Site layout:
>
> Pages:
> + Homepage ('main', 'sidebar')
> + Articles ('main', 'sidebar')
> - Article1 ('full', 'extract')
> - Article2 ('full', 'extract')
>
> Snippets:
> - Header
> - Footer
>
> Layouts
> - Default
>
>
> Homepage:
>
>
>
>
>
>
>
>
>
>
>
> 'default' layout:
>
>
>
>
>
> --
>
> In this example, the homepage needs to be re-rendered when:
> - homepage is modified
> - new article child is created
> - article1/2 is updated/removed
> - article1/2 has extract added/removed
> - default layout is modified
> - header snippet is modified
> - footer snippet is modified
> - (please tell me if I'm missing cases here)
>
> To know all those things, the following should be more than enough to
> keep track of:
>
> - any page which is read from db during the render
> - any snippet which is read from db during the render
> - any layout which is read from db during the render
>
>
>
> New Table:
>
> create_table 'cache_dependencies' do |t|
> t.column :page_id, :integer
> t.column :depends_on, :integer
> t.column :cache_type, :string
> end
>
> Since this is just a scratch table, perhaps this should use something
> like madeline or maybe just a tree of files that are locked on write
> instead of being in the main database file.
>
> Filesystem cache:
> pages/
> page.data
> page.cacheinfo
>
>
> An after_save is added to each snippet/layout:
>
> CacheDependencies.find_all_by_cache_type_and_depends_on('snippet',
> snippet.id) do |cd|
> if(File.exists("pages/#{cd.page_id}.cacheinfo"))
> File.rm("pages/#{cd.page_id}.cacheinfo")
> end
> end
>
> An after_save is added to each page to do the same, and also an
> after_create and after_destroy are added to page that will clear
> anything depending on the parent when a child is created or removed.
>
> ---
>
> A new class, CacheInfo is registered as an 'after_initialize' on Page,
> Layout and Snippet.
>
> When rendering begins, initialize the CacheInfo object:
> CacheInfo.reset
>
> When a page/layout/snippet is loaded, it's id is added to a hash in
> CacheInfo.
>
> When the rendering is complete, the cacheinfo is written to the
> cache_dependencies table, looking something like:
>
> CacheDependencies.transaction do
> CacheDependencies.delete_all(:conditions => ['page_id = ?',
> page.id])
> page_depends.each do |pd|
> CacheDependencies.create(:page_id => page.id, :depends_on =>
> pd, :cache_type => 'page')
> end
> snippet_depends.each do |pd|
> CacheDependencies.create(:page_id => page.id, :depends_on =>
> pd, :cache_type => 'snippet')
> end
> layout_depends.each do |pd|
> CacheDependencies.create(:page_id => page.id, :depends_on =>
> pd, :cache_type => 'layout')
> end
> end
>
>
> On each render, if the page.cacheinfo file exists, the page is loaded
> - if so, render the page from scratch
> - if not:
> - se
Re: [Radiant] [ANN] New site launched
Sean, Very nice, very no-nonsense. one question: which pages are truly dynamic? By that I mean not just HTML content statically stored in the DB, just for curiosiy? It's a good job considering it's for a public insitution and all the baggage that comes with. Commitee meeting, anyone? :) On 1/1/07, Sean Cribbs <[EMAIL PROTECTED]> wrote: > Colleagues and friends, > > I am happy to announce the new website for Kansas City Kansas Community > College, www.kckcc.edu. The site is the culmination of countless hours > of planning, testing, and toiling. I'm announcing here because the site > is powered by RadiantCMS, of course! I intend to make a detailed post > on my personal blog about the site and the process, but here's a few > stats to hold you over: > > 300+ Pages > ~12 snippets > 3-4 layouts > 6 extensions (yes, we're running mental!) > And much more... > > We are extremely happy with the ease-of-use and performance that Radiant > provides our team (along with a rock-solid server, Litespeed). As time > goes on, I intend to polish and release some of the extensions which > include LDAP integration and ports of the Mailer and Search behaviors -- > I'm sure you're itching for them! > > I submitted a proposal to RailsConf 2007 about our work. Wish me luck > on that! And not to toot my own horn too much, but my design was chosen > from 3 alternatives by the students, and thus I was responsible for the > majority of the CSS and Photoshop work. As you might be able to tell, I > take a lot of my design inspiration from John's work ;). > > Here's to a happy New Year, using Radiant! > > Sean Cribbs > seancribbs.com > > p.s. During the process of launching the website, the college also > changed ISPs. There may be intermittent connectivity problems until the > process is complete. > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Displaying a specific child's content
I suppose I misunderstood his question. I thought he wanted to know how to access the content of a child page, but in retrospect, I realize that he just wanted to show the actual content of a child page somewhere else. I think the tag definitely helps, but I don't know if it is able to bring specific parts of a child page or of it will retrieve the content of the whole page. I guess he could play with the DB and then do a ??? On 1/1/07, Andreas Semt <[EMAIL PROTECTED]> wrote: > @Clark, > > --- > > > > > --- > > This includes the content of the page 'about' into your actual > page. > Alternative you could write '', because per default > the body page part is shown (or you could include self defined > page parts). > > > Best regards, > Andreas Semt > > BJ Clark schrieb: > > Hello All, > > I'm trying to display the content of a specific child page. > > Is there anyway to do this via radius tags? > > > > I realize that I can do all children (or whatever) via > > r:children:each or :first but I need to do :specificpage and I'm not > > sure how that is done. > > > > Is there a way to do that? > > Thanks, > > BJ Clark > > ___ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Displaying a specific child's content
I don't really understand your question. You want to display the content of a specific child page, where? If you just want to show that page simply use http://yourURL.com/nameOfChildPage . If you could expound a little more what exactly are you trying to accomplish we should be able to help you a bit better. On 12/31/06, BJ Clark <[EMAIL PROTECTED]> wrote: > Hello All, > I'm trying to display the content of a specific child page. > Is there anyway to do this via radius tags? > > I realize that I can do all children (or whatever) via > r:children:each or :first but I need to do :specificpage and I'm not > sure how that is done. > > Is there a way to do that? > Thanks, > BJ Clark > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Deactivate page cache for development?
I agree with Sean. I have used both development and production modes
liberally and hitherto it has worked flawlessly and have not lost ANY
files and have not lost ANY DB records. I'm fairly sure it is not a
Radiant issue (at least not as direct consequence).
On 12/31/06, Sean Cribbs <[EMAIL PROTECTED]> wrote:
>
> Andreas,
>
> I have used Radiant in all its released versions and the mental branch, and
> I can assure you that it DOES NOT delete any files in public/ for any
> reason, whether in development or production mode. Check your system
> settings, make sure that some other process, cron job or system tool hasn't
> "cleaned" the folder. Rather than being inflammatory, it would help more if
> you could identify offending lines of code or trace the evidence of your
> problem and submit the results as a trouble ticket on the Trac. I'm sorry
> you are having difficulty with it, but we can help you better if you provide
> more information.
>
> Sean Cribbs
> seancribbs.com
>
>
> Andreas Semt wrote:
> @Ruben:
>
> Not good.
> I've created a new Radiant site 'test_site' and a mysql database
> 'test_site'. Then i filled the development tables with
> 'script/setup_database development'. I use the option 3, full
> featured blog. Starting: 'mongrel_rails start -e development'.
> I use the browser to see the new blog website, all fine.
> Then logging in to the admin interface of Radiant and change the
> blog title. Save that change ('Save changes') and BANG! All files in
> '/public' (except for 'styles.css', '.htaccess',
> 'index.yml') are gone ...
> In development mode Rails caching (thus Radiant caching) is
> general deactivated.
> I believe the caching of Radiant needs some improvements.
>
> So: *DON'T USE RADIANT IN DEVELOPMENT MODE FOR WEBSITE CONSTRUCTION!*
>
> From the presentation of the
> 'Denver Derailed meeting September 27, 2006' by Nathan Wright:
>
> "Please note that because Radiant is already a complete and tested
> application, we will NOT be running it in development mode; instead we
> will be using production mode.
> Radiant is significantly faster in production mode, and it is only in
> production mode that page caching takes place."
>
>
> Greetings,
> Andreas Semt
>
> Ruben D. Orduz schrieb:
>
>
> Andreas,
>
> Can you try ommiting the "-e production" flag when starting either
> Mongrel or WEBrick? Or try replacing it with "-e development"? Still I
> think it's REALLY weird that your files in public are gone...that's
> baffling.
>
> Happy new year to you too!
>
>
> On 12/31/06, Andreas Semt <[EMAIL PROTECTED]> wrote:
>
>
> Hi Ruben,
>
> same behavior with Webrick:
> My startup command (location: ''):
> 'sudo ruby script/server webrick -e production'.
> The only files still in '/public'
> (after 'Clear page cache') are 'index.yml' and
> '.htaccess'.
> Wanna try for yourself (i have no Apache-FCGI setup) ;-\ ?
>
> *A happy and healthy new year to all list members!*
>
>
> Best regards,
> Andreas Semt
>
>
> Ruben D. Orduz schrieb:
>
>
> Hi Andreas,
>
> I'm at a loss here, cause 1) am not sure why you're losing your files
> inside RAILS_ROOT/public and 2)am not too familiar with the
> ideocincracies of Mongrel. I run all my apps with Apache/FCGI and
> works pretty good--and it has never erased any of my files.
>
> It's a scary thought that a web server (Mongrel) can -- and does --
> delete physical files from the file system with a change of settings.
> I'd look into Mongrel documentation, instead of Radiant, IMO.
>
>
>
> On 12/31/06, Andreas Semt <[EMAIL PROTECTED]> wrote:
>
>
> @Ruben:
>
> I have to correct something:
> My start command for Radiant is:
> 'sudo mongrel_rails start -e production'.
> So I believe i use Radiant in 'production mode'
> (unlike 'development mode'), yet i developing
> the website (my meaning of 'during
> development'). That's not the preferred
> way of working with a Rails app, isn't it?
>
> However: If i deactivate the caching (in 'environment.rb')
> and then start Radiant with 'sudo mongrel_rails start -e production'
> and then click the 'Clear page cache' button in the admin interface
> and then loosing most files in '/public/' ... looks still
> like a malpractice to me.
>
>
> Best regards,
> Andreas Semt
>
>
> Ruben D. Orduz schrieb:
Re: [Radiant] Deactivate page cache for development?
Andreas, Can you try ommiting the "-e production" flag when starting either Mongrel or WEBrick? Or try replacing it with "-e development"? Still I think it's REALLY weird that your files in public are gone...that's baffling. Happy new year to you too! On 12/31/06, Andreas Semt <[EMAIL PROTECTED]> wrote: > Hi Ruben, > > same behavior with Webrick: > My startup command (location: ''): > 'sudo ruby script/server webrick -e production'. > The only files still in '/public' > (after 'Clear page cache') are 'index.yml' and > '.htaccess'. > Wanna try for yourself (i have no Apache-FCGI setup) ;-\ ? > > *A happy and healthy new year to all list members!* > > > Best regards, > Andreas Semt > > > Ruben D. Orduz schrieb: > > Hi Andreas, > > > > I'm at a loss here, cause 1) am not sure why you're losing your files > > inside RAILS_ROOT/public and 2)am not too familiar with the > > ideocincracies of Mongrel. I run all my apps with Apache/FCGI and > > works pretty good--and it has never erased any of my files. > > > > It's a scary thought that a web server (Mongrel) can -- and does -- > > delete physical files from the file system with a change of settings. > > I'd look into Mongrel documentation, instead of Radiant, IMO. > > > > > > > > On 12/31/06, Andreas Semt <[EMAIL PROTECTED]> wrote: > >> @Ruben: > >> > >> I have to correct something: > >> My start command for Radiant is: > >> 'sudo mongrel_rails start -e production'. > >> So I believe i use Radiant in 'production mode' > >> (unlike 'development mode'), yet i developing > >> the website (my meaning of 'during > >> development'). That's not the preferred > >> way of working with a Rails app, isn't it? > >> > >> However: If i deactivate the caching (in 'environment.rb') > >> and then start Radiant with 'sudo mongrel_rails start -e production' > >> and then click the 'Clear page cache' button in the admin interface > >> and then loosing most files in '/public/' ... looks still > >> like a malpractice to me. > >> > >> > >> Best regards, > >> Andreas Semt > >> > >> > >> Ruben D. Orduz schrieb: > >>> errr...being in development mode should do nothing to your file > >>> system. That is really, really, really weird. > >>> > >>> PS.: You all Radiantists have a happy and safe new year. > >>> > >>> On 12/30/06, Andreas Semt <[EMAIL PROTECTED]> wrote: > >>>> Thanks! > >>>> > >>>> it works ... > >>>> BUT: > >>>> After deactivation of the caching mechanism i clicked the > >>>> 'Clear page cache' button ... oh my! > >>>> Only the files '.htaccess' and 'index.yml' are still in > >>>> the 'public' directory under the radiant root dir. *All* > >>>> other files - inclusive the 'images' subdirectory - are > >>>> gone. Is that a feature??? > >>>> > >>>> > >>>> Best regards, > >>>> Andreas Semt > >>>> > >>>> > >>>> Ruben D. Orduz schrieb: > >>>>> Andreas, > >>>>> > >>>>> I believe if you comment line 8 of environment.rb and restart your web > >>>>> server it will, be default, not cache pages. > >>>>> > >>>>> > >>>>> > >>>>> On 12/29/06, Andreas Semt <[EMAIL PROTECTED]> wrote: > >>>>>> Hello list! > >>>>>> > >>>>>> Is it possible to disable the page caching mechanism > >>>>>> during development of a Radiant web site? > >>>>>> > >>>>>> Thanks in advance! > >>>>>> > >>>>>> > >>>>>> Best regards, > >>>>>> Andreas Semt > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Deactivate page cache for development?
Hi Andreas, I'm at a loss here, cause 1) am not sure why you're losing your files inside RAILS_ROOT/public and 2)am not too familiar with the ideocincracies of Mongrel. I run all my apps with Apache/FCGI and works pretty good--and it has never erased any of my files. It's a scary thought that a web server (Mongrel) can -- and does -- delete physical files from the file system with a change of settings. I'd look into Mongrel documentation, instead of Radiant, IMO. On 12/31/06, Andreas Semt <[EMAIL PROTECTED]> wrote: > @Ruben: > > I have to correct something: > My start command for Radiant is: > 'sudo mongrel_rails start -e production'. > So I believe i use Radiant in 'production mode' > (unlike 'development mode'), yet i developing > the website (my meaning of 'during > development'). That's not the preferred > way of working with a Rails app, isn't it? > > However: If i deactivate the caching (in 'environment.rb') > and then start Radiant with 'sudo mongrel_rails start -e production' > and then click the 'Clear page cache' button in the admin interface > and then loosing most files in '/public/' ... looks still > like a malpractice to me. > > > Best regards, > Andreas Semt > > > Ruben D. Orduz schrieb: > > errr...being in development mode should do nothing to your file > > system. That is really, really, really weird. > > > > PS.: You all Radiantists have a happy and safe new year. > > > > On 12/30/06, Andreas Semt <[EMAIL PROTECTED]> wrote: > >> Thanks! > >> > >> it works ... > >> BUT: > >> After deactivation of the caching mechanism i clicked the > >> 'Clear page cache' button ... oh my! > >> Only the files '.htaccess' and 'index.yml' are still in > >> the 'public' directory under the radiant root dir. *All* > >> other files - inclusive the 'images' subdirectory - are > >> gone. Is that a feature??? > >> > >> > >> Best regards, > >> Andreas Semt > >> > >> > >> Ruben D. Orduz schrieb: > >>> Andreas, > >>> > >>> I believe if you comment line 8 of environment.rb and restart your web > >>> server it will, be default, not cache pages. > >>> > >>> > >>> > >>> On 12/29/06, Andreas Semt <[EMAIL PROTECTED]> wrote: > >>>> Hello list! > >>>> > >>>> Is it possible to disable the page caching mechanism > >>>> during development of a Radiant web site? > >>>> > >>>> Thanks in advance! > >>>> > >>>> > >>>> Best regards, > >>>> Andreas Semt > >>>> ___ > >>>> Radiant mailing list > >>>> Post: Radiant@lists.radiantcms.org > >>>> Search: http://radiantcms.org/mailing-list/search/ > >>>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant > >>>> > >>> ___ > >>> Radiant mailing list > >>> Post: Radiant@lists.radiantcms.org > >>> Search: http://radiantcms.org/mailing-list/search/ > >>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant > >> ___ > >> Radiant mailing list > >> Post: Radiant@lists.radiantcms.org > >> Search: http://radiantcms.org/mailing-list/search/ > >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant > >> > > ___ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Deactivate page cache for development?
errr...being in development mode should do nothing to your file system. That is really, really, really weird. PS.: You all Radiantists have a happy and safe new year. On 12/30/06, Andreas Semt <[EMAIL PROTECTED]> wrote: > Thanks! > > it works ... > BUT: > After deactivation of the caching mechanism i clicked the > 'Clear page cache' button ... oh my! > Only the files '.htaccess' and 'index.yml' are still in > the 'public' directory under the radiant root dir. *All* > other files - inclusive the 'images' subdirectory - are > gone. Is that a feature??? > > > Best regards, > Andreas Semt > > > Ruben D. Orduz schrieb: > > Andreas, > > > > I believe if you comment line 8 of environment.rb and restart your web > > server it will, be default, not cache pages. > > > > > > > > On 12/29/06, Andreas Semt <[EMAIL PROTECTED]> wrote: > >> Hello list! > >> > >> Is it possible to disable the page caching mechanism > >> during development of a Radiant web site? > >> > >> Thanks in advance! > >> > >> > >> Best regards, > >> Andreas Semt > >> ___ > >> Radiant mailing list > >> Post: Radiant@lists.radiantcms.org > >> Search: http://radiantcms.org/mailing-list/search/ > >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant > >> > > ___ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] User Roles
Adam, I concur with much of what you say here. I think user/group permission/management is one of the weaker, if not the weakest points of Radiant at this point in time. I strongly believe it should be part of the core and not handled by a third party plug-in. Permissions should always be internal to the system, well encapsulated and with proper access right. For now Radiant works for me, but starting this spring I'm going to have my hands full as about 10 people will need some form of access to the back end and we'll make 3-4 groups each of which SHOULD have their permission set. Instead, we're gonna have to rely on personal principles and honesty. At any rate, I still think Radiant holds much more promise than Drupal or Typo3 in so far as simplicity and no-nonsense is concerned. On 12/30/06, Adam Salter <[EMAIL PROTECTED]> wrote: > > Why not have a "role group" which has predefined access to a page > (which is inherited by sub-pages) > Then you could make your own groups and allocate "normal" users as > you saw fit. > The only users able to change these role groups would be Developers > and Admin. > > I don't want users changing the "file not found" pages or the styles > pages etc, but the rest are ok. > > Adam > Ps I appreciate that: > a) it's only .52 version > b) it's intended for small groups > But I don't see how planning for growth is a bad thing... I'm using > Radiant as well because it best fits my purposes of all the CMS I've > tried, but that doesn't mean it can't be improved. On a similar note: > another lack for Radius is unfortunately handling forms, but I see > the new extensions in mental branch as taking care of this... > > On 31/12/2006, at 12:28 AM, Clayton Cafiero wrote: > > > Not a bad idea to have a "contributor" role -- edit but not add or > > delete pages, change status from draft to published, perhaps add > > snippets -- hmmm. Maybe. > > > > - Clayton > > > > On Dec 30, 2006, at 6:40 AM, Adam Salter wrote: > > > >> These roles are not really useful IMHO. > >> Admin and developer are too close in purpose. User has too much > >> access. > >> I'd like to have individual users with access to certain parts of the > >> site... and an Admin user(s) for control of this. > >> > >> Just my opinion of course. I'm not trying to start a flame war. > >> > >> Cheers, > >> Adam > >> > >> On 30/12/2006, at 2:24 AM, John W. Long wrote: > >> > >>> Joannou Ng wrote: > Can someone explain to me the differences between the user roles? > >>> > >>> admin - has access to everything, can create accounts, etc... > >>> developer - can create pages, snippets, and layouts > >>> default - can create pages and snippets > >>> > >>> -- > >>> John Long > >>> http://wiseheartdesign.com > >>> ___ > >>> Radiant mailing list > >>> Post: Radiant@lists.radiantcms.org > >>> Search: http://radiantcms.org/mailing-list/search/ > >>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant > >> ___ > >> Radiant mailing list > >> Post: Radiant@lists.radiantcms.org > >> Search: http://radiantcms.org/mailing-list/search/ > >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > > > ___ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Deactivate page cache for development?
Andreas, I believe if you comment line 8 of environment.rb and restart your web server it will, be default, not cache pages. On 12/29/06, Andreas Semt <[EMAIL PROTECTED]> wrote: > Hello list! > > Is it possible to disable the page caching mechanism > during development of a Radiant web site? > > Thanks in advance! > > > Best regards, > Andreas Semt > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to include date and time?
Hi Andreas, I believe so. If you want to have a context-insensitive date, you could either modify the date tag or simply write a new one. In either case, it should be fairly straight forward. Peace. On 12/25/06, Andreas Semt <[EMAIL PROTECTED]> wrote: Hi Ruben, thanks for your explenations. However is bound to the page object, isn't it? What if i just want to include the *actual* date and time somewhere on my pages? Greetings, Andreas Semt > Hi Andreas, > > That's trivial. Refer to line 315 of page_context.rb file. Just for > reference this is what it says: > 215 # > 316 # > 317 # Renders the date that a page was published (or in the event > that it has > 318 # not ben modified yet, the date that it was created). The > format attribute > 319 # uses the same formating codes used by the Ruby +strftime+ > function. By > 320 # default it's set to '%A, %B %d, %Y'. > 321 # > 322 define_tag 'date' do |tag| > 323 page = tag.locals.page > 324 format = tag_time_format(tag) > 325 if date = page.published_at || page.created_at > 326 date.strftime(format) > 327 end > 328 end > > > > On 12/24/06, Andreas Semt <[EMAIL PROTECTED]> wrote: > > Hello list, > > > > with the radius tag i can include the date and time > > in my pages. However, which way can i modify the output of that radius > tag? > > Or: Is it possible to include pure Ruby code in the page and layout > > definitions and then style that for an adapted date and time version? > > > > > > Best regards, > > Andreas Semt > > ___ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to include date and time?
Hi Andreas, That's trivial. Refer to line 315 of page_context.rb file. Just for reference this is what it says: 215 # 316 # 317 # Renders the date that a page was published (or in the event that it has 318 # not ben modified yet, the date that it was created). The format attribute 319 # uses the same formating codes used by the Ruby +strftime+ function. By 320 # default it's set to '%A, %B %d, %Y'. 321 # 322 define_tag 'date' do |tag| 323 page = tag.locals.page 324 format = tag_time_format(tag) 325 if date = page.published_at || page.created_at 326 date.strftime(format) 327 end 328 end On 12/24/06, Andreas Semt <[EMAIL PROTECTED]> wrote: > Hello list, > > with the radius tag i can include the date and time > in my pages. However, which way can i modify the output of that radius tag? > Or: Is it possible to include pure Ruby code in the page and layout > definitions and then style that for an adapted date and time version? > > > Best regards, > Andreas Semt > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Wiki page
John (W. Long), just to give you the heads up that I'm going to be working on the Radiant quickstart Wiki. Peace. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] modify CSS default
Javier, Si, todos los layouts estan en la carpeta "layouts." El CSS es una pagina. Es decir, tan pronto y tu log in en la interfaz administrativa, en la lista donde esta la pagina principal, los articulos, etc. hay una pagina llamada styles o stylesheet, has click en esta. Otra cosa, ya que esta es una lista en Ingles, por respeto, si deseas preguntar algo puedes enviarmelo directamente. On 12/19/06, javier barcena <[EMAIL PROTECTED]> wrote: > Hola podes indicarme donde estan esas partes ene l admin de radiant.. > supongo qeu el layout en la solapa de layouts y el css donde.. esta? > > > > 2006/12/18, Ruben D. Orduz <[EMAIL PROTECTED]>: > > Es muy facil. > > > > Lo unico que tienes que hacer es estar seguro que los nombres de las > > clases y de los ids corresponden con la convencion de Radiant. O, > > tambien puedes cambiar los nombres de las clases y ids en el layout > > general o en la pagina que quieres para que correspondan con aquellos > > de tu estilo. En realidad lo que tienes que entenderes que Radiant > > trata el layer visual en dos partes, el "layout" que digamos es el > > estilo fisico y estructural de la pagina y el CSS que son los detalles > > visuales. > > > > Entiendes? > > > > On 12/18/06, javier barcena <[EMAIL PROTECTED]> wrote: > > > Tengo el css ya listo.. solo que no se como implementarlo en radiant. > > > cual es la pagina css de radiant y como armo el home.esas son mis dudas > > > ruben. > > > un saludo. > > > > > > > > > > > > 2006/12/18, Ruben D. Orduz <[EMAIL PROTECTED]>: > > > > para CSS? Si es asi, te recomiendo que bajes Web Developer Bar para > > > > Firefox. Esta herramienta te ofrece una manera de arrglar el tu estilo > > > > CSS en vivo. Una vez que ya vez lo que te guste, puedes salvar el > > > > archivo CSS y lo puedes copiar a la pagina CSS de Radiant. > > > > > > > > On 12/18/06, javier barcena <[EMAIL PROTECTED]> wrote: > > > > > si > > > > > estoy armando un sitio basadao en radianntcms tengo la hoja de > > > estilo.. > > > > > pero no se los pasos a seguir .. es decir una manera ordenada de > > > desarrollo > > > > > > > > > > > > > > > > > > > > 2006/12/18, Ruben D. Orduz <[EMAIL PROTECTED]>: > > > > > > Que quieres saber de las etiquetas radius? Dependiendo quizas te > > puedo > > > > > ayudar. > > > > > > > > > > > > On 12/18/06, javier barcena <[EMAIL PROTECTED]> wrote: > > > > > > > si! > > > > > > > tb teng ootra duda y es trabajar bien y usar bien los tag de > > radius > > > > > > > gracais.. tenes data sobre esto. > > > > > > > saludos javier > > > > > > > > > > > > > > 2006/12/18, Ruben D. Orduz <[EMAIL PROTECTED]>: > > > > > > > > Javier, > > > > > > > > > > > > > > > > La mejor manera de cambiar el CSS es en la pagina admin, has > > click > > > en > > > > > > > > la pagina llamada style en la lista principal. Es a eso que te > > > > > > > > refieres? > > > > > > > > > > > > > > > > On 12/18/06, javier barcena < [EMAIL PROTECTED] > wrote: > > > > > > > > > hello ! > > > > > > > > > i want change the style CSS default of radiantcms X mi style > > > CSS > > > > > > > > > need the steep for one change easy > > > > > > > > > thanks > > > > > > > > > javier.! > > > > > > > > > > > > > > > > > > ___ > > > > > > > > > Radiant mailing list > > > > > > > > > Post: Radiant@lists.radiantcms.org > > > > > > > > > Search: > > > http://radiantcms.org/mailing-list/search/ > > > > > > > > > Site: > > > > > > > > > > > > > > http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > > > > > > > > > > > > > > > > > > > > > > ___ > > > > > > > > Radiant mailing list > > > > > >
Re: [Radiant] modify CSS default
Es muy facil. Lo unico que tienes que hacer es estar seguro que los nombres de las clases y de los ids corresponden con la convencion de Radiant. O, tambien puedes cambiar los nombres de las clases y ids en el layout general o en la pagina que quieres para que correspondan con aquellos de tu estilo. En realidad lo que tienes que entenderes que Radiant trata el layer visual en dos partes, el "layout" que digamos es el estilo fisico y estructural de la pagina y el CSS que son los detalles visuales. Entiendes? On 12/18/06, javier barcena <[EMAIL PROTECTED]> wrote: > Tengo el css ya listo.. solo que no se como implementarlo en radiant. > cual es la pagina css de radiant y como armo el home.esas son mis dudas > ruben. > un saludo. > > > > 2006/12/18, Ruben D. Orduz <[EMAIL PROTECTED]>: > > para CSS? Si es asi, te recomiendo que bajes Web Developer Bar para > > Firefox. Esta herramienta te ofrece una manera de arrglar el tu estilo > > CSS en vivo. Una vez que ya vez lo que te guste, puedes salvar el > > archivo CSS y lo puedes copiar a la pagina CSS de Radiant. > > > > On 12/18/06, javier barcena <[EMAIL PROTECTED]> wrote: > > > si > > > estoy armando un sitio basadao en radianntcms tengo la hoja de > estilo.. > > > pero no se los pasos a seguir .. es decir una manera ordenada de > desarrollo > > > > > > > > > > > > 2006/12/18, Ruben D. Orduz <[EMAIL PROTECTED]>: > > > > Que quieres saber de las etiquetas radius? Dependiendo quizas te puedo > > > ayudar. > > > > > > > > On 12/18/06, javier barcena <[EMAIL PROTECTED]> wrote: > > > > > si! > > > > > tb teng ootra duda y es trabajar bien y usar bien los tag de radius > > > > > gracais.. tenes data sobre esto. > > > > > saludos javier > > > > > > > > > > 2006/12/18, Ruben D. Orduz <[EMAIL PROTECTED]>: > > > > > > Javier, > > > > > > > > > > > > La mejor manera de cambiar el CSS es en la pagina admin, has click > en > > > > > > la pagina llamada style en la lista principal. Es a eso que te > > > > > > refieres? > > > > > > > > > > > > On 12/18/06, javier barcena < [EMAIL PROTECTED] > wrote: > > > > > > > hello ! > > > > > > > i want change the style CSS default of radiantcms X mi style > CSS > > > > > > > need the steep for one change easy > > > > > > > thanks > > > > > > > javier.! > > > > > > > > > > > > > > ___ > > > > > > > Radiant mailing list > > > > > > > Post: Radiant@lists.radiantcms.org > > > > > > > Search: > http://radiantcms.org/mailing-list/search/ > > > > > > > Site: > > > > > > > > > > http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > > > > > > > > > > > > > > > > ___ > > > > > > Radiant mailing list > > > > > > Post: Radiant@lists.radiantcms.org > > > > > > Search: > http://radiantcms.org/mailing-list/search/ > > > > > > Site: > > > > > > http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > > > > > > > > > > > > > > > > > ___ > > > > > Radiant mailing list > > > > > Post: Radiant@lists.radiantcms.org > > > > > Search: http://radiantcms.org/mailing-list/search/ > > > > > Site: > > > > > > http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > > > > > > > > > > ___ > > > > Radiant mailing list > > > > Post: Radiant@lists.radiantcms.org > > > > Search: http://radiantcms.org/mailing-list/search/ > > > > Site: > > > http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > > > > > > > > > ___ > > > Radiant mailing list > > > Post: Radiant@lists.radiantcms.org > > > Search: http://radiantcms.org/mailing-list/search/ > > > Site: > > > http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > > > > ___ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: > http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: > http://lists.radiantcms.org/mailman/listinfo/radiant > > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] modify CSS default
para CSS? Si es asi, te recomiendo que bajes Web Developer Bar para Firefox. Esta herramienta te ofrece una manera de arrglar el tu estilo CSS en vivo. Una vez que ya vez lo que te guste, puedes salvar el archivo CSS y lo puedes copiar a la pagina CSS de Radiant. On 12/18/06, javier barcena <[EMAIL PROTECTED]> wrote: > si > estoy armando un sitio basadao en radianntcms tengo la hoja de estilo.. > pero no se los pasos a seguir .. es decir una manera ordenada de desarrollo > > > > 2006/12/18, Ruben D. Orduz <[EMAIL PROTECTED]>: > > Que quieres saber de las etiquetas radius? Dependiendo quizas te puedo > ayudar. > > > > On 12/18/06, javier barcena <[EMAIL PROTECTED]> wrote: > > > si! > > > tb teng ootra duda y es trabajar bien y usar bien los tag de radius > > > gracais.. tenes data sobre esto. > > > saludos javier > > > > > > 2006/12/18, Ruben D. Orduz <[EMAIL PROTECTED]>: > > > > Javier, > > > > > > > > La mejor manera de cambiar el CSS es en la pagina admin, has click en > > > > la pagina llamada style en la lista principal. Es a eso que te > > > > refieres? > > > > > > > > On 12/18/06, javier barcena < [EMAIL PROTECTED] > wrote: > > > > > hello ! > > > > > i want change the style CSS default of radiantcms X mi style CSS > > > > > need the steep for one change easy > > > > > thanks > > > > > javier.! > > > > > > > > > > ___ > > > > > Radiant mailing list > > > > > Post: Radiant@lists.radiantcms.org > > > > > Search: http://radiantcms.org/mailing-list/search/ > > > > > Site: > > > > > > http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > > > > > > > > > > ___ > > > > Radiant mailing list > > > > Post: Radiant@lists.radiantcms.org > > > > Search: http://radiantcms.org/mailing-list/search/ > > > > Site: > > > http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > > > > > > > > > ___ > > > Radiant mailing list > > > Post: Radiant@lists.radiantcms.org > > > Search: http://radiantcms.org/mailing-list/search/ > > > Site: > > > http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > > > > ___ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: > http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: > http://lists.radiantcms.org/mailman/listinfo/radiant > > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] modify CSS default
Que quieres saber de las etiquetas radius? Dependiendo quizas te puedo ayudar. On 12/18/06, javier barcena <[EMAIL PROTECTED]> wrote: > si! > tb teng ootra duda y es trabajar bien y usar bien los tag de radius > gracais.. tenes data sobre esto. > saludos javier > > 2006/12/18, Ruben D. Orduz <[EMAIL PROTECTED]>: > > Javier, > > > > La mejor manera de cambiar el CSS es en la pagina admin, has click en > > la pagina llamada style en la lista principal. Es a eso que te > > refieres? > > > > On 12/18/06, javier barcena < [EMAIL PROTECTED]> wrote: > > > hello ! > > > i want change the style CSS default of radiantcms X mi style CSS > > > need the steep for one change easy > > > thanks > > > javier.! > > > > > > ___ > > > Radiant mailing list > > > Post: Radiant@lists.radiantcms.org > > > Search: http://radiantcms.org/mailing-list/search/ > > > Site: > > > http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > > > > ___ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: > http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: > http://lists.radiantcms.org/mailman/listinfo/radiant > > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] modify CSS default
Javier, La mejor manera de cambiar el CSS es en la pagina admin, has click en la pagina llamada style en la lista principal. Es a eso que te refieres? On 12/18/06, javier barcena <[EMAIL PROTECTED]> wrote: > hello ! > i want change the style CSS default of radiantcms X mi style CSS > need the steep for one change easy > thanks > javier.! > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: > http://lists.radiantcms.org/mailman/listinfo/radiant > > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Quickstart
John, I wouldn't mind taking a stab at it. Peace. On 12/14/06, John W. Long <[EMAIL PROTECTED]> wrote: > Does anyone have a moment to write up a nice quickstart for Radiant? The > one here is rather unfinished: > > http://dev.radiantcms.org/radiant/wiki/QuickStart > > Material for it could probably be pulled from here: > > http://dev.radiantcms.org/radiant/wiki/UsingRadiant > > (That section needs to be broken into a few pages anyway.) > > -- > John Long > http://wiseheartdesign.com > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Checking for an asset existence
coffee...yeah right! :) On 12/14/06, Sean Cribbs <[EMAIL PROTECTED]> wrote: > I apologize... File.expand() should be File.expand_path(). That's what I > get for drinking too much coffee!! > > Sean > > > On 12/14/06, Sean Cribbs < [EMAIL PROTECTED]> wrote: > > How about this: > > > > The Radius code: > > > > > > > > > > > > > > The tag definition: > > > > tag "if_public_file_exists" do |tag| > > tag.expand if File.exists?(File.expand(File.join(RAILS_ROOT, "public", > tag.attr['path']))) > > end > > > > Of course you could change the nomenclature however you like, and a few > unit tests wouldn't hurt, but that's the basic outline. > > > > Sean > > > > > > > > On 12/14/06, Brian Sam-Bodden < [EMAIL PROTECTED]> wrote: > > > > > > > > > Fellow Radiant users: > > >I have a site for which I have a "highlights" image for certain > pages. Sort of a branding/marketing image. I've put those images in a > /highlights directory and named them after the page they belong in, e.g. > home ==> home-highlight.jpg. Of course, for the pages that don't have an > image I get the always unpleasant image placeholder icon in Safari and IE. > If there a easy way to use something like a or > type of tag? So that I can only include that tag > for those pages that have one. I can do something with Javascript but > that's just not pretty. Any ideas? > > > > > > Thanks, > > > Brian > > > > > > > > > ___ > > > Radiant mailing list > > > Post: Radiant@lists.radiantcms.org > > > Search: http://radiantcms.org/mailing-list/search/ > > > Site: > http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > > > > > > > > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: > http://lists.radiantcms.org/mailman/listinfo/radiant > > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Best way to build a navigation bar with Radiant CMS?
Hello Andreas, I've found that a collection of open source (or closed-source but free) tools are needed. I've yet to find the "ultimate" CSS/XHMTL app. For structural layout I recommend N|vu (both windows and *IX), for CSS any text editor with syntax highlighting can do the job (I use PSPad for windows and vim and emacs on *IX systems. One tool that is invaluable is Firefox's Web Developer Tool Bar--the best in the biz, period. There are other FF extensions that help debugging code (i.e. FireBug, IE Tab, View Source Chart). On 12/11/06, Andreas Semt <[EMAIL PROTECTED]> wrote: > @Sean, > @Ruben, > > (sorry for the delay ...) > thanks for your help! I'm trying to build clean CSS code for the site. > Does anybody know if there are open source CSS builder tools? Perhaps > the can help me to develop the overall design for the site, so i could > adjust the resulting CSS code by hand later. > > Best regards, > Andreas Semt > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Stylesheet
Hello, I'm assuming that if I specify a CSS file in the layout it will use that instead of the one in the DB, correct? I just don't see the benefit of having the style sheet stored in DB to be quite honest. For one, it's one more query, for two fiddling and fine tunning the style sheet is a heck lot easier with a flat file. IMO. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Best way to build a navigation bar with Radiant CMS?
Andreas, Atop what Sean said, or rather, to reiterate: Radiant is no different than any other CMS/Blog tool insofar as presentation layer is concerned, perhaps a bit more flexible, if anything. I personally base my "designs" (I admit it, I'm not a web designer) on XHTML strict and CSS 2, after that I look at the current root-level page that comes with Radiant. And then substitute with radius tags any page parts that require iterating over a list (possibly in the DB). In a way it is not that different than writing an XSLT/XPath template. On 12/8/06, Sean Cribbs <[EMAIL PROTECTED]> wrote: > Andreas, > > 1) The short answer is that Radiant can do whatever you like visually; it > doesn't restrict you! So feel free to design your pages in whatever tool > you want, then break them into logical parts (focusing on structure and > reuse), then import them into Radiant. There are a lot of different > strategies to implementing your pages in Radiant, but that would be a > book-length topic! The typical practice is to have layouts that describe > the overall structure of pages, with various Radius tags to include pieces > of the rendered page; pages that have the actual content in multiple parts; > and snippets that are frequently reused pieces of HTML or Radius tags. > > 2) Look for information on the tag on the wiki, weblog, and > in the source code. While it's kind of inflexible (I'm working on a patch > for that issue), it does the job well enough in most cases. > > 3) The only "best practice" I can cite is to use standards-based HTML/CSS > (which nowadays means using lists for navigation menus), but that goes for > any website. > > Hope this helps, > > Sean Cribbs > seancribbs.com > > > On 12/8/06, Andreas Semt <[EMAIL PROTECTED]> wrote: > > Hello Radiants (is that the correct title?), > > > > i want to build a website for a client with Radiant. I started with the > > third install option of Radiant - the full featured blog layout of > > Radiant. However this site should be a 'classic' website, not a blog, so > > i want to include a navigation bar on the left side. My - annoying (?) > > newbie questions - are: > > 1.) Is it possible with Radiant to have a left side bar, too (together > > with the existing right side bar of the blog layout)? > > 2.) Can i use this new sidebar as a navigation bar or exists other > > Radiant specific constructs for this purpose? > > 3.) Are there other 'best practice' to follow or has anybody hints to > > consider for this task (building a simple navigation bar in Radiant)? > > > > Thanks in advance for some help! > > > > > > Greetings, > > Andreas Semt > > ___ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: > http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: > http://lists.radiantcms.org/mailman/listinfo/radiant > > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] doesnt' work with mine
For many people the configuration mailer behavior is just too cryptic and obfuscated. It only makes sense to have a page in the admin interface to configure the mailer behavior by just filling a form. This is a very important (if not the most important) feature to some people, I think we as a group should take a stab at it and have the project leader merge it into the source tree. Best. On 12/7/06, John Aneston <[EMAIL PROTECTED]> wrote: > Jose Jose wrote: > > Hi John, > > > > I don't have the mailer working. Can't figure it out yet. What I've done > > is 1) Installesd php form generator http://phpformgen.sourceforge.net/ > > 2) Generated my contact form. > > 3) Embedded the html form on a Radiant page. > > > > I'll use this solution on the meantime while I get the mailer working. > > > > Jose. > > Hi Jose, > > mailer_behavior works fine for me. i dont know about php much, but its > very simple to work with radiant_mailer_behvior, you can find the readme > file inside plugin folder with which its easy to configure the mailer, > 3 things you have to concentrate. >- body part of contact-us page, >- config part of contact-us page and >- certain changes has to be made with the "../config/environment.rb" > or "../config/environment/production.rb or development.rb". > > on modifying and configuring these 3 things, will enable the feature of > mailer_behavior for you website. > > cheers > john aneston > > -- > Posted via http://www.ruby-forum.com/. > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Any step by step configuration for Mailer Behaviour
I was wondering, what's the argument for not allowing Radiant to use unix's mail() facility? I understand if you're running your app in an OS other than standard *IX, you should use an SMTP, but given that most hosting companies use a flavor of *IX I don't see why not allow radiant to use of those mail facilities. Any light in this subject is much appreciated. Peace. On 12/5/06, John Aneston <[EMAIL PROTECTED]> wrote: > John Aneston wrote: > > Pete Burgess wrote: > >> What I have is one page named "Contact" with two parts. "Body" is the > >> first part and "config" the second. I have the this in the "Body" part: > >> > >> > >> > >> > >> Name: > >> > >> Message: > >> > >> > >> > >> > >> and this in the "config" part: > >> > >> mailers: > >>contact: > >> subject: Contact From Site > >> from: [EMAIL PROTECTED] > >> redirect_to: /contact/thanks > >> recipients: > >>- [EMAIL PROTECTED] > >> > >> I have the "mailer" behaviour set to the Contact page. > >> > >> I open the contact page in my browser and fill in the form and send it. > >> It bounces me back to the Contact page (not the "Thanks" page) and I do > >> not receive the email at the specified email address. > >> > >> Thanks again for the help. > > Pete, > > http://wiki.rubyonrails.org/rails/pages/HowToSendEmailsWithActionMailer > > check that link for environment.rb file's configuration. i hope this > might help you > > cheers > john aneston > > -- > Posted via http://www.ruby-forum.com/. > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant error at DreamHost
Hi Felipe, I've been developing Rails apps on DreamHost servers and am truly satisfied with both speed and features, and save for the month-long disastrous blackout, they've been pretty reliable and responsive. I just looked at your page and it's giving me a 404 error. Be sure your domain is pointing to the public directory inside the radiant app. On 11/30/06, Felipe Amaral <[EMAIL PROTECTED]> wrote: > Hi, > > I try install Radiant CMS in my DreamHost account, but it is fail with > "ActiveRecord::StatementInvalid". > > See this... > > http://www.ferreiradoamaral.com/ > > I'm new on the rails, can you help me > > > > > -- > Felipe Amaral > Vento Livre Internet > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: > http://lists.radiantcms.org/mailman/listinfo/radiant > > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Default Schema
I believe changing the nomenclature of tables would be tough. Rails relies heavily on naming conventions to generate models and objects, so even though you can change the table names, it would entagle things for you. If you don't have CREATE privileges in the DB server, I suggest having your ISP or DBA create a new DB for radiant purposes. On 11/29/06, Sean Cribbs <[EMAIL PROTECTED]> wrote: > You would set the database as "radiant" in your config/database.yml. Is > this what you're asking? > > Sean Cribbs > seancribbs.com > > > On 11/29/06, Jim Gay <[EMAIL PROTECTED]> wrote: > > I'm trying to keep all my Radiant content in a separate schema in my > > database. > > For instance, I'd like the layouts table to be 'radiant.layouts' > > > > Can anyone point me in the right direction? > > I've not yet tried anything in my development environment. > > > > -Jim > > ___ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: > http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: > http://lists.radiantcms.org/mailman/listinfo/radiant > > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] /admin problems
Yup. I usually use the recursive flag because I'm sure with all metaprogramming Rails does it probably uses tmp directories a lot. Not to mention session storage and management. So even though this time was easy to isolate to /tmp/sesh it's just better to chmod the whole folder and its children. On 11/29/06, Sean Cribbs <[EMAIL PROTECTED]> wrote: > > I usually get that problem with new Rails applications when the tmp/ > directory doesn't exist (especially if I checked them out of an SVN repo). > Go to the root of your Radiant installation and run `rake tmp:create` . If > it's already there, you may have to chmod -R. > > Sean Cribbs > seancribbs.com > > > Daniel Sheppard wrote: > Actually, it needs read/write access to tmp/sessions (actually, all of > tmp) > > > > -Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Ruben D. Orduz > Sent: Wednesday, 29 November 2006 2:23 PM > To: radiant@lists.radiantcms.org > Subject: Re: [Radiant] /admin problems > > It seems that you need to give Apache read/write access to the script > folder. sudo chmod -R 755 ./script should help. > > On 11/28/06, John Furfey <[EMAIL PROTECTED]> wrote: > > > Here it is: > > Permission denied - > script/../config/../tmp/sessions//ruby_sess.b794dd418e29357b > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: > http://lists.radiantcms.org/mailman/listinfo/radiant > > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Why is my radiant site running so slow?
It looks pretty responsive to me. Any DB-driven app will have a similar lag. The fact that you're using a shared server only makes matters worse, specially at peak times. On 11/28/06, Mike Moscow <[EMAIL PROTECTED]> wrote: > hello, I am developing the following website using Radiant: > > laaia.textdriven.com > > This is the first time I have used radiant on ANY project. I always noticed > that > this website was always a little slow loading up. I checked it in various > locations and there was always a certain lag. Today while meeting with the > client > and viewing the website from office the delay was VERY apparent (and a little > embarassing). I'm not sure what is going on since I'm a total noob at rails. > Could it be some issue with radiant caching system, or is there some sort of > issue with my radiant configuration causing the delay or something in my > code... > > Anthony > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] /admin problems
It seems that you need to give Apache read/write access to the script folder. sudo chmod -R 755 ./script should help. On 11/28/06, John Furfey <[EMAIL PROTECTED]> wrote: > Here it is: > > Permission denied - > script/../config/../tmp/sessions//ruby_sess.b794dd418e29357b > /usr/lib/ruby/1.8/pstore.rb:101:in `initialize' > /usr/lib/ruby/1.8/pstore.rb:101:in `open' > /usr/lib/ruby/1.8/pstore.rb:101:in `transaction' > /usr/lib/ruby/1.8/cgi/session/pstore.rb:71:in `initialize' > /usr/lib/ruby/1.8/cgi/session.rb:273:in `new' > /usr/lib/ruby/1.8/cgi/session.rb:273:in `initialize' > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/cgi_process.rb:112:in > `new' > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/cgi_process.rb:112:in > `session' > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/cgi_process.rb:108:in > `stale_session_check!' > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/cgi_process.rb:108:in > `session' > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:918:in > `assign_shortcuts_without_flash' > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/flash.rb:141:in > `assign_shortcuts' > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:402:in > `process_without_filters' > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/filters.rb:377:in > `process_without_session_management_support' > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/session_management.rb:117:in > `process' > /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/dispatcher.rb:38:in > `dispatch' > /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/webrick_server.rb:115:in > `handle_dispatch' > /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/webrick_server.rb:81:in > `service' > /usr/lib/ruby/1.8/webrick/httpserver.rb:104:in `service' > /usr/lib/ruby/1.8/webrick/httpserver.rb:65:in `run' > /usr/lib/ruby/1.8/webrick/server.rb:155:in `start_thread' > /usr/lib/ruby/1.8/webrick/server.rb:144:in `start' > /usr/lib/ruby/1.8/webrick/server.rb:144:in `start_thread' > /usr/lib/ruby/1.8/webrick/server.rb:94:in `start' > /usr/lib/ruby/1.8/webrick/server.rb:89:in `each' > /usr/lib/ruby/1.8/webrick/server.rb:89:in `start' > /usr/lib/ruby/1.8/webrick/server.rb:79:in `start' > /usr/lib/ruby/1.8/webrick/server.rb:79:in `start' > /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/webrick_server.rb:67:in > `dispatch' > /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/commands/servers/webrick.rb:59 > /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in > `gem_original_require' > /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in > `require' > /usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:147:in > `require' > /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/commands/server.rb:30 > /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in > `gem_original_require' > /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in > `require' > /usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:147:in > `require' > script/server:3 > > > > > > > On Tue, 28 Nov 2006 22:06:29 -0500 > "John W. Long" <[EMAIL PROTECTED]> wrote: > > John Furfey wrote: > >> Output is > >> > >> Application error (Apache) > >> > >> Change this error message for exceptions thrown outside > >>of > >> an action (like in Dispatcher setups or broken Ruby > >>code) > >> in public/500.html > >> > > > > We need to see the error from the logs. Look for the one > >that is > > relevant to the mode (production|development) that you > >are running in. > > > > -- > > John Long > > http://wiseheartdesign.com > > > > > > ___ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: > > http://lists.radiantcms.org/mailman/listinfo/radiant > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] /admin problems
That's an internal server error. Then you might have WebBrick and apache trying to listen to the same port or have the radiantDir/public/dispatcher.rb misconfigured. On 11/28/06, John Furfey <[EMAIL PROTECTED]> wrote: > Output is > > Application error (Apache) > > Change this error message for exceptions thrown outside of > an action (like in Dispatcher setups or broken Ruby code) > in public/500.html > > > > > > > > On Tue, 28 Nov 2006 21:40:09 -0500 > "Ruben D. Orduz" <[EMAIL PROTECTED]> wrote: > > Could you please post the exact error output text? > > > > > > > > On 11/28/06, John Furfey <[EMAIL PROTECTED]> wrote: > >> I've seen this one posted, but not the solution. > >> > >> I have Radiant installed and the site section is working > >> fine, but I get an application error when I try to go to > >> the admin section. Running it with webrick locally on > >>OS > >> X machine. > >> > >> Anyone have any ideas? > >> > >> Thanks. > >> ___ > >> Radiant mailing list > >> Post: Radiant@lists.radiantcms.org > >> Search: http://radiantcms.org/mailing-list/search/ > >> Site: > >> http://lists.radiantcms.org/mailman/listinfo/radiant > >> > > ___ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: > > http://lists.radiantcms.org/mailman/listinfo/radiant > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] /admin problems
Could you please post the exact error output text? On 11/28/06, John Furfey <[EMAIL PROTECTED]> wrote: > I've seen this one posted, but not the solution. > > I have Radiant installed and the site section is working > fine, but I get an application error when I try to go to > the admin section. Running it with webrick locally on OS > X machine. > > Anyone have any ideas? > > Thanks. > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Featured Post
Alright,Here's what I've done so far:* Migrated my DB so that the page_parts table has a boolean (and int, really) field called isfeatured, default to 0 (false).* Tried to add a "Featured" behavior (with little success). Need to do:* Add the "featured" bahavior.* Modify the the layout/page so that it shows posts as featured first.Any and all asistance in this regard is highly appreciated.Best, Ruben ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] please help: How do I set the default URL path with multiple installs?
Jose,That Rails ticket is exactly what I was talking about. I tried and it worked very well. The only problem I see if the URL requests collide with some controller/setting of Radiantif you have a development environment tried there first before deploying. On 11/13/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Ruben,Thanks for your help.I've changed routes.rb and nothing happens : ( Perhaps I'm not sure of what I'm doing.I've also found this ticket http://dev.rubyonrails.org/ticket/5420It says to add "ActionController::AbstractRequest.relative_url_root ='/subdir'" to both routes.rb and environment.rbHas anybody used this method?Jose.> Jose,>> I'd fiddle with the lines below (which correspond to lines > 56 in> routes.rb> ):>> # Site URLs>> map.with_options(:controller => 'site') do |site|>> site.homepage '', :action>> => 'show_page', :url ="" '/' >>>>>> site.not_found 'error/404', :action>> => 'not_found'>> site.error 'error/500', :action >> => 'error'>>>> # Everything else>> site.connect '*url', :action>> => 'show_page'>> end>> >>> On 11/13/06, Ruben D. Orduz <[EMAIL PROTECTED]> wrote:>>>> I think what you describe should be fairly easy to solve with>> routes.rbhacks . Else your COULD create an url filter in the front>> controller to add>> "/myApp/" in front of all incoming URLS. Sorry I can't be more specific>> at>> the moment...I'm at work and am supposed to be debugging some 2K lines >> of>> .Net code :(>>>>>> On 11/13/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> >>> > Ok, let me exaplin this as easily as I can.>> >>> > Radiant generates an html page with the following div>> >>> > >> > >> >>> > What I want to do is to force, in >> > >> > So I would get /myapp/recursos/>> >>> > and eveything will work fine : )>> >>> > Any ideas?>> >>> > > Thanks for the reply. >> > >>> > > Do you know where exactly do I have to make the changes?>> > >>> > > Perhaps # Site URLs ?>> > >>> > > Jose. >> > >>> > >>> > >> The easiest way is to set your DNS to point to your radiant sub>> dir.>> > >> Else>> > >> you could fiddle with the routes.rb file to fit your needs.>> > >>>> > >>>> > >> On 11/13/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote:>> > >>>>> > >>> Hi,>> > >>>>> > >>> I've managed to set two radiant sites using apache 1.3 and fcgi. >> Now>> > I>> > >>> can>> > >>> access them site at http://www.mydomain.org/radiant1 and>> > >>> http://www.mydomain.org/radiant2>> > >>>>> > >>> However, I can't navigate the sites because all the links are>> > generated >> > >>> using the default path />> > >>>>> > >>> So if I click the News section for example, the site refers me to>> > >>> http://www.mydomain.org/news instead of>> > >>> http://www.mydomain.org/radiant1/news.>> > >>>>> > >>> Where do I set the default url path for each of my radiant sites? >> > >>>>> > >>> Jose.>> > >>> ___>> > >>> Radiant mailing list>> > >>> Post: Radiant@lists.radiantcms.org>> > >>> Search: http://radiantcms.org/mailing-list/search/>> > >>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant>> > >>>>> > >> ___ >> > >> Radiant mailing list>> > >> Post: Radiant@lists.radiantcms.org>> > >> Search: http://radiantcms.org/mailing-list/search/>> > >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant>> > > >> > > ___>> > > Radiant mailing list>> > > Post: Radiant@lists.radiantcms.org >> > > Search: http://radiantcms.org/mailing-list/search/>> > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant>> > >>> >>> > ___>> > Radiant mailing list>> > Post: Radiant@lists.radiantcms.org>> > Search: http://radiantcms.org/mailing-list/search/>> > Site: http://lists.radiantcms.org/mailman/listinfo/radiant>> >>>>>> ___> Radiant mailing list > Post: Radiant@lists.radiantcms.org> Search: http://radiantcms.org/mailing-list/search/> Site: http://lists.radiantcms.org/mailman/listinfo/radiant___Radiant mailing listPost: Radiant@lists.radiantcms.orgSearch: http://radiantcms.org/mailing-list/search/Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] please help: How do I set the default URL path with multiple installs?
Jose,I'd fiddle with the lines below (which correspond to lines > 56 in routes.rb): # Site URLs map.with_options(:controller => 'site') do |site| site.homepage '', :action ="" 'show_page', :url ="" '/' site.not_found 'error/404', :action ="" 'not_found' site.error 'error/500', :action ="" 'error' # Everything else site.connect '*url', :action ="" 'show_page' end On 11/13/06, Ruben D. Orduz <[EMAIL PROTECTED]> wrote: I think what you describe should be fairly easy to solve with routes.rb hacks. Else your COULD create an url filter in the front controller to add "/myApp/" in front of all incoming URLS. Sorry I can't be more specific at the moment...I'm at work and am supposed to be debugging some 2K lines of .Net code :( On 11/13/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Ok, let me exaplin this as easily as I can.Radiant generates an html page with the following div What I want to do is to force, in So I would get /myapp/recursos/ and eveything will work fine : )Any ideas?> Thanks for the reply.>> Do you know where exactly do I have to make the changes?>> Perhaps # Site URLs ?>> Jose. >>>> The easiest way is to set your DNS to point to your radiant sub dir.>> Else>> you could fiddle with the routes.rb file to fit your needs.>>>>>> On 11/13/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote:>>>>>> Hi,>>>>>> I've managed to set two radiant sites using apache 1.3 and fcgi. Now I>>> can>>> access them site at http://www.mydomain.org/radiant1 and>>> http://www.mydomain.org/radiant2 >>>>>> However, I can't navigate the sites because all the links are generated>>> using the default path />>>>>> So if I click the News section for example, the site refers me to >>> http://www.mydomain.org/news instead of>>> http://www.mydomain.org/radiant1/news.>>> >>> Where do I set the default url path for each of my radiant sites?>>>>>> Jose.>>> ___>>> Radiant mailing list >>> Post: Radiant@lists.radiantcms.org>>> Search: http://radiantcms.org/mailing-list/search/ >>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant >>>>> ___ >> Radiant mailing list>> Post: Radiant@lists.radiantcms.org>> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant> > ___> Radiant mailing list > Post: Radiant@lists.radiantcms.org> Search: http://radiantcms.org/mailing-list/search/> Site: http://lists.radiantcms.org/mailman/listinfo/radiant>___ Radiant mailing listPost: Radiant@lists.radiantcms.orgSearch: http://radiantcms.org/mailing-list/search/Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Sticky Posts
Hey guys (I know...I should be debugging .Net code...I'm a bad employee),What's would be the most painless way to add a "sticky" behavior to posts? For example..something I wish to remain in the front page in spite of its publishing date. Any help is much appreciatedJose...if I can get a few more minutes off, I'll look into the routes.rb file and let you know which lines I'd be messing with :) ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] please help: How do I set the default URL path with multiple installs?
I think what you describe should be fairly easy to solve with routes.rb hacks. Else your COULD create an url filter in the front controller to add "/myApp/" in front of all incoming URLS. Sorry I can't be more specific at the moment...I'm at work and am supposed to be debugging some 2K lines of .Net code :( On 11/13/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Ok, let me exaplin this as easily as I can.Radiant generates an html page with the following div What I want to do is to force, in So I would get /myapp/recursos/ and eveything will work fine : )Any ideas?> Thanks for the reply.>> Do you know where exactly do I have to make the changes?>> Perhaps # Site URLs ?>> Jose. The easiest way is to set your DNS to point to your radiant sub dir.>> Else>> you could fiddle with the routes.rb file to fit your needs.>> On 11/13/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:>> Hi,>> I've managed to set two radiant sites using apache 1.3 and fcgi. Now I>>> can>>> access them site at http://www.mydomain.org/radiant1 and>>> http://www.mydomain.org/radiant2 >> However, I can't navigate the sites because all the links are generated>>> using the default path />> So if I click the News section for example, the site refers me to >>> http://www.mydomain.org/news instead of>>> http://www.mydomain.org/radiant1/news.>>> >>> Where do I set the default url path for each of my radiant sites?>> Jose.>>> ___>>> Radiant mailing list >>> Post: Radiant@lists.radiantcms.org>>> Search: http://radiantcms.org/mailing-list/search/ >>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant> ___ >> Radiant mailing list>> Post: Radiant@lists.radiantcms.org>> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant>> ___> Radiant mailing list > Post: Radiant@lists.radiantcms.org> Search: http://radiantcms.org/mailing-list/search/> Site: http://lists.radiantcms.org/mailman/listinfo/radiant>___Radiant mailing listPost: Radiant@lists.radiantcms.orgSearch: http://radiantcms.org/mailing-list/search/Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] please help: How do I set the default URL path with multiple installs?
The easiest way is to set your DNS to point to your radiant sub dir. Else you could fiddle with the routes.rb file to fit your needs.On 11/13/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Hi,I've managed to set two radiant sites using apache 1.3 and fcgi. Now I canaccess them site at http://www.mydomain.org/radiant1 and http://www.mydomain.org/radiant2However, I can't navigate the sites because all the links are generatedusing the default path /So if I click the News section for example, the site refers me to http://www.mydomain.org/news instead ofhttp://www.mydomain.org/radiant1/news.Where do I set the default url path for each of my radiant sites?Jose. ___Radiant mailing listPost: Radiant@lists.radiantcms.orgSearch: http://radiantcms.org/mailing-list/search/Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Table of contents snippet help
Can you just create a FAQ controller (and behaviour) and have the url encode the arguments? Even though your solution *works,* it violates DRYBIG TIME!On 11/12/06, Joseph Banks <[EMAIL PROTECTED]> wrote: This is what I came up with. Its not ideal because its less automatedthan I wanted. I have to add an extra if_url section for every categoryI create. h2. Table of Contents: "":: () h2. Table of Contents: "":: () "":# ""::() h2. Table of Contents: "":: () "":# "":: () h2. Table of Contents: "":: () "":# ""::() h2. Table of Contents: "":: () "":# ""::() Any ideas on how to have it automatically cycle through each of thecategories rather than my having to create it manually? --Posted via http://www.ruby-forum.com/.___Radiant mailing listPost: Radiant@lists.radiantcms.orgSearch: http://radiantcms.org/mailing-list/search/Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] RadiantCMS, Maple Leaf Web Project
Erik,I'm sorry I think I misunderstood Greg's needs and you might've misunderstood (or I didn't explain myself properly) a little.Radiant right now, in spite of all of its merits it still is in its infancy (performance-, feature- and support-wise). I wouldn't want Radiant to YAOCMS. It has its own place, use and personality, if you will. However, you must admit that much work still needs to be done to work out the features that it DOES have and some features that would definitely be helpful from the administrative perspective. No, I don't want Forums, XML aggregators, polls, classifieds, banner rotators, etc. I'd simply would like: * A more graphical (not necessarily WYSIWYG) editor so that those people who write content can enter it themselves w/o needing to know HTML, Textile, Markdown or any other mark-up language.* A roles based content entry...don't want a casual collaborator to have the same level of access than, say, a developer or an admin or a regular collaborator. * Comments/Feedback system. (which I beleive was mentioned in the presentation @ RubyCon).* Category management.I know some of this can be (relatively) easily implemented, but the fact is that they're as yet not there. I know the merits (and dismerits) of Drupal, Joomla! and Typo3...I simply suggested them based on my perception that this site was fairly large and highly dynamic. At any rate, the point is that there are already a quadrazillion (an actual number: a four followed by a bizillion zeros) very competnt CMS's that can even walk your dog and I wouldn't like Radiant become just one more. However, some added features would enhance the experience of what it does do and what it does best. JMO. Peace,RubenOn 10/27/06, Greg Farries <[EMAIL PROTECTED]> wrote: Erik Mallinson wrote:> I disagree with Ruben - the point of Radiant isn't to mature to be> like Drupal, Joomla! or Typo3; the point of Radiant is that it's> mature to exercise restraint. Radiant is for small groups of people > to manage a straight forward site.Well, in terms of Maple Leaf Web, we have a very small team ofwriters/editors. Including the followingAdmin (myself)Senior Editor (4)Managing Editor (1) Content Manager (2)Writers (4)The Senior editors, and writers won't even need access to the CMS, onlymyself, the managing editor and the content manager need to be able toadd/edit content. So I think this definitely falls into the small team/group class.> I think it depends on what you want. If you want to have the site> feature the articles, Radiant is great for a site like that, (imho)> better than Drupal. If you want to add polls, forums, and other > community features, you should probably go with Drupal.Essentially, all I need the CMS to do is manage the features we produce.The Weblog, Forum, sections will all be controlled by third party software. Weblog will use Wordpress, the forum will be PunBB.> Why? Because Drupal was overkill. I spent most of the time> turning off features and dealing with 'the way it is' than with the> content itself. I agree, and this is why I initally looked at using Wordpress. Wordpress isalmost what I need, as it doesn't complicate the process with a bunch offeatures almost no one uses.>> So if you're going to keep the forums and polls separate I don't see > why you couldn't use Radiant.> ___> Radiant mailing list> Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/> Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___Radiant mailing listPost: Radiant@lists.radiantcms.orgSearch: http://radiantcms.org/mailing-list/search/Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] RadiantCMS, Maple Leaf Web Project
Hello Greg,Radiant in my opinion is too young to handle a fully dynamic website with tons of content. I really like Rails and Radiant, but in all honesty Radiant still ways to go to even compete with full-featured CMSs such as Typo3 and Joomla! which are amazingly complete, robust, open source and free. I still find many more willing PHP developers than Ruby/Rails devs...so that's something you might want to keep in consideration. Also PHP is much, much, much more widely supported by web hosts than Rails is. At the end it's your decish; however, if I was in your shoes, I'd deploy a php-based CMS for the time being and later on (once Radiant or any other Rails-based CMS matures to such a level) you can make the move. Peace,RubenOn 10/27/06, Greg Farries <[EMAIL PROTECTED]> wrote: Hello all - I've cleared this request/email with John W. Long...I'm interested in possibly using Ruby on Rails for a political educationalproject that I currently manage. Currently the website (Maple Leaf Web - http://www.mapleleafweb.com) is completely static, and it is getting harderand harder to manage the content. I've gone through a redesign phase(designing just a few of the pages, so I could get an idea of how the navigation, and subpages would be laid out)[http://www.mapleleafweb.ca/redesign/index.html], and I am now looking toinstall a CMS to manage the content. I have extensive experience with WordPress - but I don't think even a modified version of WordPress wouldaccomplish all the requirements we need. I've have also inquired with acouple developers who work with Drupal. However, I'm not convinced that Drupal is up to the task - it's a powerful CMS, but more oriented towardsbuilding online communities that serving feature/backgrounders. I have alsobeen stung by a few Drupal developers who say they can deliver, only to disappoint.I've always been intrigued by Rails, particularly after Alistapart wasredesigned and employed Ruby on Rails as core of the CMS. I also useFeedDigest a lot, which from what I understand uses Ruby on Rails for some of its front-end. I became aware of RadiantCMS after I was searching for adecent (mature) CMS that used Ruby. However, there seems to be a large gapbetween existing Ruby on Rails websites and any mature Ruby on Rails CMS. RadiantCMS seems to be heads and shoulders above the other opensource Rubyon Rails CMS.I think Alistapart [http://alistapart.com] is fairly close to what we needfor Maple Leaf Web (and as far as I know, they use Ruby on Rails), and I'm interested in an opinions about whether this can be accomplished for anon-profit organization and or whether Ruby on Rails is the platform thatcan accomplish what we need done. I am also impressed at the implementation of RadiantCMS for the Ruby website, http://www.ruby-lang.org - which I thinkclosely resembles what we need for Maple Leaf Web; lots of content, withsidebars pointing the user to additional/related content. Unfortunately, budget is always a concern when dealing with an organizationthat lives through charity of others. Does developers on this mailing listprovide discounts for verifable non-profits looking for development? If not, do any of you know of anyone who would be interested in developing aRuby on Rails CMS in exchange for a "sponsorship" mention/links on the newdesign? In the past we've provided a link in the footer of each sub-page on the site.We have a great deal of traffic (44,575 Visits, 265,533 page views as ofOctober 25, 2006) and we're willing to provide some positive exposure tocompanies/individuals that help.If you require more details of our requirements, please contact me and I'll forward more information.Thanks in advance for any help that you can provide,Thanks,Greg Farries M.A.Project Managerhttp://mapleleafweb.comPhone: 403.329.2286Fax: 403.382.7148Email: [EMAIL PROTECTED]--Canada's Premier Political Education Website___ Radiant mailing listPost: Radiant@lists.radiantcms.orgSearch: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How do you manage blog items?
Yes, I alredy bumped into this problem. Once you have more than a few dozen posts, it becomes really clumsy to change/edit/delete any given post. Typo (which is also built on Rails) offers a better solution for blogs (strictly speaking), IMO. However, the great thing about Radiant is that it is fairly painless to extend/edit and if you wanted to, you could create a fancy Ajax-based Article child listing...it just takes siome work and sweat. Having worked with many enterprise-level CMS's I can say that Radiant is in its early infancy; however, I think it looks very promising from the extensibility and simplicity point of view. Those of us who want to extend it and "nurture" it need to be keen to these kind of details. Peace,RubenOn 10/27/06, Ollivier Robert <[EMAIL PROTECTED]> wrote: On 10/27/06, Sean Cribbs <[EMAIL PROTECTED]> wrote:> Are you speaking in terms of an administration interface or in terms of> organizing them? The archive behaviors automatically create I guess he is speaking in terms of the admin interface. As theentries are sorted alphabetically in the admin interface, it may getdifficult to manage hundreds of subpages.--Ollivier Robert -___ Radiant mailing listPost: Radiant@lists.radiantcms.orgSearch: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
