Re: [Radiant] updated_at is not touched on content changes?
$ radiant --version Radiant 0.8.0 $ ls vendor/extensions/ navigation_tags paperclipped ray reorder settings sns /Jørn Sean Cribbs wrote: Jorn, On which version of Radiant are you experiencing this problem? Sean ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Caching problem with SNS extension?
I have a site running Radiant 0.8 with the head revision of the SNS extension from the radiant hub, and I am experiencing a problem with assets only being deliveried correctly to every second request. When I navigate directly to my main stylesheet[1] in my browser, I get the stylesheet or a completely blank screen (with Content-Length: 0 in the HTTP headers). Pressing F5 to redo the request, I get the opposite. Every second request gives my the stylesheet, every other a blank response. Does anyone know whats going on? How I done something wrong in my setup? /Jørn Schou-Rode [1]: http://215-221.dk/css/screen.css ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] updated_at is not touched on content changes?
Using the r:date for=updated_at / tag, it should AFAIK be possible to print the date where the current page was last updated. The value is drawn from the updated_at field in the pages table, which is updated automagically by Rails whenever a row changes. However, most of the updates I am doing only involves changing the contents of the body part of a page. Such changes does not cause any change on the pages table, as the parts are stored in page_parts. Thus, the updated_at field is not updated with such changes. Is this the expected behaviour, or is it a bug? If it is by design, how would I go about getting a last modified dd/mm/ in the bottom of my pages? Any extensions? Thanks in advance. /Jørn ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Simple graphical charts
Another approach would be to do everything on the client side, using a JavaScript charting library like Flot[1]. You would still need some code to facilitate the transfer of raw data from server to client. This could be done using simple radius tags, but it could also (should) be done as a nice reusable extension :-) [1]: http://code.google.com/p/flot/ -- Jørn Schou-Rode http://malamute.dk/ On Mon, 13 Jul 2009 09:00 -0400, radiant-requ...@radiantcms.org wrote: On Jul 12, 2009, at 2:04 PM, Rafael Souza raf...@maisweb.org wrote: Take a look in Scruffy: http://scruffy.rubyforge.org/ If you need, you could make a extension with this... =) Wow! That is a very nice plugin. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
