Re: [Radiant] Rendering parts from different pages.
Haha... Sean and John are in perfect sync! ___ 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] Relative Linking in Radiant
On 6/12/07, Chris Parrish [EMAIL PROTECTED] wrote: However, if in page A I have a relative link: a href=b, the target page depends on the address used. In the first case, I will be directed to http://root/b because the browser thinks I'm in the root/ folder. In the second case, I'm sent to http://root/a/b because it thinks I'm in the root/a/ folder. This is normal behavior and not something you can fix. Simply normalize your URLs - choose a convention for trailing slashes and stick to it. ___ 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] SEO in Radiant
I agree with everything Chris said just now. Stop worrying and simply use Radiant. Use hierarchies, nested menus, deep URLs and good, usable navigation patterns. Make your visitors happy. While doing that, simply code towards good SEO practices on the way. Spiders won't mind how you organized your site. Use description page parts for your pages and render the meta tag in the layout. Use nice titles and readable slugs. After you're done, you can also create a sitemap for your site. There is vanilla Radiant way and there is a plugin, if I'm not mistaken. Search the archives. ___ 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] sqlite3 NULL == chaos ?
On 6/11/07, Aitor Garay-Romero [EMAIL PROTECTED] wrote: After some debugging i found that in my sqlite3 database, fields of type string have a weird default value in the schema, and not a default NULL value. This is for all tables. Read this first: http://weblog.rubyonrails.com/2007/1/29/using-sqlite3-with-rails ___ 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] SEO in Radiant
On 6/8/07, Colin Nederkoorn [EMAIL PROTECTED] wrote: Can anyone recommend articles / resources relevant to a radiant powered site that I could read to learn how to optimize my site? No, they can not. Radiant is just a backend, and what you do with the HTML of your site is totally independent of it. So, there are no SEO articles/resources relevant to Radiant. While coding your layouts and pages, all regular articles still apply: http://del.icio.us/mislav/SEO Here is one tip that you can achieve through Radiant: keep your page titles and slugs descriptive and relevant. Both have much effect on search engine rankings. The rest is up to you. ___ 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] SEO in Radiant
On 6/11/07, dave4c03 [EMAIL PROTECTED] wrote: I am not certain about this but I think that from a SEO perspective, it would be better if the URL namespace was flat. A flat URL namespace means the navigation structure is not part of the page name. This means a page could participate in or be dropped out of several navigation/menu structures without affecting any local or external pages referencing them. It also means that pages could be dragged/dropped and reordered between directories. At first I was shocked at what you're suggesting, but now that you've explained it I see you have some valid points. But I'm still not convinced that you should go for flat structure just to please spiders and ease the building of some navigation menus. You should resolve your issues otherwise: for instance, set redirects for spiders from old URLs to the new paths when you move pages around. ___ 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] events calendar extension
On 6/8/07, John Furfey [EMAIL PROTECTED] wrote: Hello, I remember reading on this list that someone was working on an events calendar extension. That was 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
Re: [Radiant] site shows directory listing instead of radiant
On 6/7/07, John Muhl [EMAIL PROTECTED] wrote: I having a bit of trouble with radiant not starting, or something, and thus when browse my site I get a folder listing of /public/ instead of the site it's self. What server are you using? If Apache + FCGI: is your .htaccess in order? ___ 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] [ANN] Fuzzy Bears Example Extension
On 5/22/07, John W. Long [EMAIL PROTECTED] wrote: I typically create this example when I demo the extension system to others. It demonstrates creating a custom controller and model, and also how to expose that model to a page through custom tags. Is the functionality going to become core someday? It would be great to finally have a CMS for fuzzy bears tracking! ;P ___ 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] Page Attachments
On 5/9/07, Sean Cribbs [EMAIL PROTECTED] wrote: Updated! Sweet! * Now uses attachment_fu instead of acts_as_attachment. Interesting. I couldn't make attachment_fu work with Radiant (there were issues with resolving its internal dependencies). * Uses svn:externals to get the latest attachment_fu. Not sure if this will work with an export method (svn gurus please comment?) of installation. Why not? It's the same to Rails. It makes a difference depending on how you deploy. ___ 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] 404 error messages
# For better performance replace the dispatcher with the fastcgi one # # Example: RewriteRule ^(.*)$ dispatch.fcgi [QSA,L] RewriteEngine On Locate this block. The RewriteRule here isn't supposed to be active. Comment it out like the lines before: # RewriteRule ^(.*)$ dispatch.fcgi [QSA,L] Leave the RewriteEngine line as-is. ___ 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] Error when testing extensions
On 5/5/07, Andrew O'Brien [EMAIL PROTECTED] wrote: uninitialized constant ActionController::Assertions::ResponseAssertions (NameError) Radiant - by having its own initializer - somehow messes with Dependencies and its ability to do autoloading ninja magic. I discovered this when I realized attachment_fu cannot be used in Radiant without some manual requires, but I haven't discovered what exactly breaks in Dependencies code. ___ 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] Ajax responses
On 5/4/07, Benjamin Curtis [EMAIL PROTECTED] wrote: I'm doing a custom page, and I'd like to respond to some Ajax requests in my custom process method. I haven't been able to find an example of this yet, and I'm wondering if anyone who has done it would like to volunteer a snippet of code as a guide. A custom page means you are extending Radiant with a custom controller? If so, implementing Ajax in your site will be trivial. Do you need help on the server side, or help with JavaScript? I can show you how to leverage the Prototype framework real easy. ___ 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] Saving changes without publishing
On 4/29/07, Chris Parrish [EMAIL PROTECTED] wrote: acts_as_draftable? Never knew of it. Me neither. Apparently there is an acts_as_versioned by the same author and both look pretty cool. That must be Rick Olson. The latter plugin is well-known. Even better, anyone interested in crafting an extension to add versioning functionality to radiant? Would be cool, but doesn't solve the original poster's problem. ___ 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] About couldn't find HOME environment problem
On 4/27/07, keita [EMAIL PROTECTED] wrote: 3. It is radiant issue that Radiant's dispatcher loads rails/railties/lib/rails_generator.rb, and other rails applications' dispatchers don't load rails_generator.rb. 4. I believe dispatchers don't need to generate any code and must not. I must agree with you, Keita. Nice writeup ___ 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] Suggestion Textile rendering
On 4/19/07, Daniel Sheppard [EMAIL PROTECTED] wrote: Preformatted is different to line-broken in that preformatted text will not wrap (though perhaps a white-space css rule can change that without losing the line-breaking?) See: http://users.tkk.fi/~tkarvine/pre-wrap-css3-mozilla-opera-ie.html ___ 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] Spam
On 4/13/07, Gabriel Lamounier [EMAIL PROTECTED] wrote: Is there any way of stopping the recent spams? Spammers are already crying! Read the recent announcement on this ML. ___ Radiant mailing list Post: [EMAIL PROTECTED] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant as a news a bit more improved
On 3/26/07, Sylvestre Mergulhão [EMAIL PROTECTED] wrote: My news have a field for the source(where i found it) and a field for an url to the source. You can do what many people do with Radiant in such cases: use page parts. Simply create a new page part named source and put relevant information there. After that you can render this information where and when you see fit. ___ 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] newspaper
On 3/26/07, Alexy Khrabrov [EMAIL PROTECTED] wrote: So far most sites I've seen are like WordPress -- a single boring column of a single guy. That is because far most sites are blogs, not because their CMS is limited. With Radiant, your layout can be as complex as you make it. You can have as many authors as you wish and render their names above/below the articles appropriately. This is how I render the news column (3 most recent entries) on one of the sites I manage: div id=news r:find url=newsr:children:each order=desc limit=3 div class=entry h2r:title //h2 div class=bodyr:content //div r:if_content part=extendeddiv class=morer:linkRead more .../r:link/div/r:if_content /div /r:children:each/r:find /div So, this is a proof-of-concept that any category (simply a branch in the content tree) can be rendered wherever you need. The rest is all information architecture, design and project realization in HTML and CSS. ___ 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] ANN: radiant.vim v0.0.2
On 3/11/07, Raphael Bauduin [EMAIL PROTECTED] wrote: The home page having a slug of /, it must be accessed with the title. Hm. Why not: radiant/pages/ - gets Home :split radiant/pages/articles - gets articles child under Home ___ 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] Simple blog too complex: what does this code do?
On 3/8/07, Martin Olsson [EMAIL PROTECTED] wrote:
There is one piece of code in the Normal layout that I
don't quite understand:
r:if_url matches=^/articles/\d{4}/\d{2}/\d{2}/.+r:unless_url
matches=-archives/$p class=infoPosted by r:author / on
r:date //p/r:unless_url/r:if_url
It's simple really - you read it out like English :)
If the current URL starts with /articles//MM/DD (generic blog format),
print out Posted by [author] on [date] in a paragraph. However, the URL
must not end in -archives/. This is because archives are pages with that
URL format, too, but you don't want them to look like blog posts.
___
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] Simple blog too complex: what does this code do?
... or you could just use the regexp without the
first part: /\d{4}/\d{2}/\d{2}/
On 3/8/07, Sean Cribbs [EMAIL PROTECTED] wrote:
You could replace anything inside those parens with an appropriate
character class... probably [\w-]+ would work.
Sean
Thanks! I know how to write regular expressions. I was wondering if
there was a way to make this more automatic. The DRY-principles
should apply to layouts as well, no? Can anyone think of a way to
reduce the number of places I need to change when I add a new project
blog. Right now I do this:
Create a new child of the root, say food.
Copy the content from a previous blog, say cars.
Change some stuff in the page content.
Create an RSS-feed.
Change the Normal layout.
I'd like to find a smarter and less redundant way to do this.
/Martin
http://smpl.se
On 8 mar 2007, at 14.52, Sean Cribbs wrote:
Change the first part of the if_url to look like so:
Posted by on
You can keep chaining on other categories with the | character.
Sean
Martin Olsson wrote:
So what do I do to make it work with a multi-blog site? I need
something that matches /blog//MM/DD, /blog//MM/DD, /car/
/ MM/DD, and I don't really want to have to change it or add
to it every time I add a new project blog. Regards, Martin
Olsson http://smpl.se On 8 mar 2007, at 11.07, Mislav Marohnić
wrote:
On 3/8/07, Martin Olsson [EMAIL PROTECTED] wrote: There is one
piece of code in the Normal layout that I don't quite understand:
Posted by on
It's simple really - you read it out like English :) If the
current URL starts with /articles//MM/DD (generic blog
format), print out Posted by [author] on [date] in a paragraph.
However, the URL must not end in -archives/. This is because
archives are pages with that URL format, too, but you don't want
them to look like blog posts.
___ 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] Defining a category for articles
On 2/19/07, Ruby Admirer [EMAIL PROTECTED] wrote: But I tried to install mephisto without success (I use sqlite3 as the DB). Radiant works and I like it and I prefer not to change. You'd be better off with Mephisto in this case. Content management in Radiant is plain hierarchical (tree - based). However, it has a neat extension system now and, if you pull up your sleeves and have some experience, you could make a plugin for yourself that adds category select to the admin interface and a couple of handy Radius tags. You can also resort to some sort of a clever hack. With categories you're basically trying to make some content appear in multiple places, right? Well, if you could hack the Page model to have multiple parents instead of just one, you could easily achieve this goal. ___ 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] Defining a category for articles
On 2/19/07, Ruby Admirer [EMAIL PROTECTED] wrote: I'm just discovering Radiant and I'm a bit lost with behaviour, plugin and extension. I understand that behaviour will be deprecated with the 0.6 release. But what is the difference and relationship between an extension and a plugin ? Errm I interchanged the two terms in my sentence, which wasn't right. I meant extension. Plugins in Radiant are like general Rails plugin which can add functionality, monkeypatch existing stuff and so on. For instance, adding Radius tags is done with plugins, while admin interface hackery is in extensions. ___ 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] JS-free view ? (newcomer)
On 1/23/07, Sean Cribbs [EMAIL PROTECTED] wrote: Luckily JS is only required in the admin interface, so you might be able to enable JS just for that domain/url in your browser. He cannot. It is a text browser not supporting JS ___ 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
source / no / Would I mind?? Are you kidding? :) ___ 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] [ANN] Mailer extension
Nice! We'll try it out. Are you going to do the same with event calendar and LDAP stuff you mentioned? On 1/16/07, Sean Cribbs [EMAIL PROTECTED] wrote: I've teased you long enough! The Mailer extension has been added to the Radiant repository. ___ 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?
On 12/30/06, Andreas Semt [EMAIL PROTECTED] wrote: 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??? Gee, I hope not! :-/ -M ___ 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] Interest in a WYSIWYG plugin
WYSIWYG is a call for trouble. Less (Markdown, Textile) is more. Encourage people to think about content visually and you get instant mess. By using HTML or plaintext markup, content editors are forced (in a good way) to think about content semantically and to leave the styling, font sizes, image position and floating to the designer. However, that's just me. There still might be interest in the community. I just saw what WYSIWYG did to people (in MS Word, Dreamweaver, other CMS-s...) and decided giving control to content editor is not exaclty smart. On 10/6/06, Todd Baur [EMAIL PROTECTED] wrote: All,My team is researching the plugin architecture of Radiant and the plan is to develop a WYSIWYG editor for Radiant that is similar to what is used in Wordpress. I am willing to contribute the code we develop if there is an interest in the community for it. ~*~*~~*~*~*~*~*~*~*~*~*~Todd Baur[EMAIL PROTECTED]858-752-1459 11814 Westview ParkwayUnit #176San Diego, CA 92126 ___Radiant mailing listPost: 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] Interest in a WYSIWYG plugin
On 10/6/06, Justin Grammens [EMAIL PROTECTED] wrote: I think textile is awesomebut for the non-technical person they really need aWYSIWYG editor.No, for the non-technical person they really need to become more technical. This isn't 1999 when websites were toys - today we care something about semantics and accessibility. I think we should stop saying here is your text box, enter content in it the way it looks good to you. I've introduced Textile markup to many (Markdown, because of indenting semantics, is not my choice for textboxes) young people and they never had any trouble getting it. As for the ignorant older people who just want to put stuff online without caring about anything you tell them, I wouldn't even let them near textboxes. ___ 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] No entries in log files
Check the log levels for the production mode. The current level may be :warn-MOn 10/3/06, John Tsombakos [EMAIL PROTECTED] wrote:Ok, this is odd.I had switched Radiant to use production mode, and now I'm not seeing any access entries written to any log file - either Apache's log in/var/log/apache2/access.log, nor any of the rails log files in myradiant/log/*.log files.Why am I not seeing any entries? (It may help track down my header problem , thought I doubt it...)Thanks.___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] No entries in log files
Apache always logs - it really doesn't care (know) what production mode you are running your Rails app in.On 10/3/06, John Tsombakos [EMAIL PROTECTED] wrote:On 10/3/06, Mislav Marohnić [EMAIL PROTECTED] wrote: Check the log levels for the production mode. The current level may be :warn -MAh, true. Missed that one.But would that cause Apache not to make an entry in it's log file? ___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] Set-Cookie: appearing on page
On 9/30/06, John Tsombakos [EMAIL PROTECTED] wrote: It's Apache 2.0.55, standard setup with Ubuntu Linux.Yeah, but that's now complete info. You power Rails with mod_ruby, cgi, fastcgi, proxying to mongrel? ___ 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] Set-Cookie: appearing on page
On 9/29/06, John Tsombakos [EMAIL PROTECTED] wrote: So for some reason, half of the headers are not being interpreted as headers.That's what I thought. What kind of Apache setup do you have?It doesn't look like it originates from Apache... those are the headers set by the application ___ 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] Set-Cookie: appearing on page
Yeah it might be a weird Ajax thing. You can inspect xmlhttprequests easily, though: just install Firebug for Firefox, open it up (F12) when you enter the admin and go to options (last option, check it). When you click on the plus-es now you can see the requests in console. Inspect the server response by clicking on them.Your problem doesn't seem to me like a client-side problem because you can insert response headers into the page by an accident. It might be a server problem On 9/29/06, John Tsombakos [EMAIL PROTECTED] wrote: I was able to set up a virtual host, using Dyndns's wildcard capability.So my site is mostly working (thought I do have it still in development mode).One thing I'm still seeing, in the Admin pages, when I click the Plus next to the Articles page (in the default setup), the spinner wheelshows for a long time. Then the children appear, but below the lastchild is:Set-Cookie: _session_id=593f6ac8b238a85961a87259f6e59e87; path=/ Connection: closeTransfer-Encoding: chunkedContent-Type: text/html;charset=utf-80Not sure where to look for this. Looks like some weird RJS thing?Anyone have an idea?Thanks!___ 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] Set-Cookie: appearing on page
On 9/29/06, Mislav Marohnić [EMAIL PROTECTED] wrote: Your problem doesn't seem to me like a client-side problem because you can insert response headers into the page by an accident.Sorry. Here I meant to say you CAN'T insert response headers into the page by an accident ___ 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 add css styles to a website?
On 9/21/06, Jim Gay [EMAIL PROTECTED] wrote: One of the main benefits of using CSS in general is that its cached locally in the user's browser. On the first visit there is some overhead, but subsequently (if its is acting properly) the browser shouldn't request a new stylesheet if it has one of the same name in its local cache. This is true, when the file is served by the server. It sets the appropriate headers. Has anyone even inspected HTTP headers sent by a Radiant response? There is no Cache-Control header, no Expires, Last-modified or Etag, too. Yes, the browser will cache such kind of content, but not for long (depends on the browser). The result is all your users polling the stylesheets all the time because their browsers try to validate their internal cache, but don't have the means with (like an Etag). For the people not knowing what the hell I'm talking about, here is a good read: http://www.mnot.net/cache_docs/ People with big stylesheets and traffic running Radiant move their styles to a static file, anyway. Maybe they want to edit it with a proper editor - yeah I know TextMate can edit content from web textboxes, but not all people have fancy Mac boxes. Maybe they want it served (and cached) properly - by a web server. So you've moved your styles to external files, great. What now? Can you make quick changes to them inside the admin interface? Not really, you've sacrificed that. So, what I asked before was do we really need to sacrifice that, having such a flexible and powerful framework? ___ 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 add css styles to a website?
On 9/22/06, John W. Long [EMAIL PROTECTED] wrote: I'd appreciate a patch that addressed these issues.Deal! I kinda fell in love with Radiant in the past few days (evaluating it) so it will be a pleasure.Be patient, because I'm still studying hard for college. A week from now and I'll get to it. ___ 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 add css styles to a website?
On 9/20/06, John W. Long [EMAIL PROTECTED] wrote: Giovanni Intini wrote: Create a layout with content type text/css and paste your css code there.It's probably better to create a layout with a content type oftext/css and put just the tag r:content / in the layout. Then create a page, assign the layout, and paste your css in the body part.How fast can Radiant serve these? Does it cache them?It would rock if Radiant had an option to save the layout (stylesheet) into a file in public/stylesheets once you're done... ___ 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 CSS Layout quirk
On 9/20/06, Bryan [EMAIL PROTECTED] wrote: I found an article that suggests fixing the problem by forcing the vert.scroll bar in the css style sheet.It does the trick, but I am notreally satisfied with it.That is what the CSS gurus do with centered layouts - they force the scrollbar. No need for seeking complicated solutions--Mislav ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Radiant in a subdirectory
I have Radiant installed in a subdirectory, not the site root. I have set AbstractRequest.relative_url_root accordingly, which makes admin section work. Surprisingly, links generated by Radius tags on the site itself start from root (/) and don't get relative_url_root prepended to them... is having the application in a subdirectory unsupported? Did anybody have success setting it up like this? I've searched the archives and the web but it seems there never was a discussion about not having the app in site root.Thanks--Mislav ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
