For anyone who missed Sean's blog post, Radiant 0.7.0 is now available.
http://radiantcms.org/blog/archives/2009/02/07/radiant-0-7-0---intaglio-release-final/
Thank you to everyone who contributed to this and previous releases of
Radiant. Your hard work is making a lot of developers (and our clie
Chris -- any idea why I can't use the h() method in my partials?
NoMethodError in SiteController#show_page
undefined method `h' for #
- Dave
Chris Parrish wrote:
> David, I still use that code in my extensions today (though I'd be
> interested to hear if anyone out there has come up with somet
Chris Parrish's solution to rendering partials within a Radius tag works
great. It's been almost a year since he posted it though, and I was
wondering if this functionality should be done a different way now --
i.e. does Radiant has a built-in way to handle this now?
Thanks,
- Dave
Chris Parris
Sean Cribbs wrote:
> http://radiantcms.org/blog/archives/2008/09/18/announcing-the-radiant-template-contest/
What about the idea of setting up naming conventions to standardize
page, snippet, and HTML section names? Is this something that will be
standardized afterwards across the winning templa
Sean Cribbs wrote:
> A long time ago, John solicited contributions of "templates" with the
> opportunity for people to get them included in the main Radiant
> distribution. I think this is a fabulous idea and I'd like to
> reinitiate it. I'm going to up the ante some and say that the top
> submis
Mohit Sindhwani wrote:
> 3. I think there was a mention once about using the aggregation
> extension. It would be good to just mention that.
>
> Oh, and we need to link to this one from the Summer Reboot page
Thanks for the feedback Mohit. I've linked my article on the main Summer
Reboot page a
Arik Jones wrote:
> Paperclipped is wy easier and a little more flexible. You can access
> all attachments from anywhere using the radiant tags. Where as in Page
> Attachments, you normally have to re-upload or remember what page a
> certain asset is attached to. The interface is much cleane
Mohit -- Thanks for taking the lead on this project. You've done a great
job, as has everyone who has contributed so far.
I finally had the chance to sit down and start my end of the
documentation. Here's my first page:
http://wiki.radiantcms.org/Simple_RSS_Feeds
If you have any comments on my
Sean Cribbs wrote:
> This is a known issue, and has more to do with Rails than Shards. It
> will not be resolved, but should be documented because the workaround is
> simple. I would suggest naming the partials something that refers back
> to your extension, like _aaa_css_overrides.rhtml for exam
Hi all,
I just ran into an issue with Shards, and wanted to know if what I
experienced is normal or a bug. I'm using Radiant 0.6.6 gem and Shards
from the 0.6.6 SVN tag.
I have two extensions that use Shards, both of which have a similarly
named file:
vendor/extensions/AAA/app/views/admin/page/_c
Chris Parrish wrote:
> Would anyone be left out if Radiant failed to support IE 6?
I vote to drop IE6 to coincide with the new Radiant UI release and move
IE6 support to an extension.
- Dave
--
Posted via http://www.ruby-forum.com/.
___
Radiant mail
Oli Studholme wrote:
> I just can’t seem to get redirects going in
> Radiant’s .htaccess. Can someone enlighten me?
Could it be that the Apache VirtualHost for the site isn't allowing
.htaccess overrides? Your httpd.conf file should have a VirtualHost
looking something like this:
Oli Studholme wrote:
> Has anyone added the WMD markdown editor to the admin interface yet?
> Or any WYSIWIG editor? I’m looking for some advice on the
> recommended way to do so.
I've used WYMeditor. I like the interface a lot, and my clients like it
too. It was a real pain to figure out
Mohit Sindhwani wrote:
> Just a brief update on the Summer Reboot Documentation project. I just
> spent a couple of hours copying and moving stuff to the site from a
> couple of places to pull things into the project :)
My schedule hasn't gone according to plan so far this summer, but I hope
to
David Piehler wrote:
> Jan frederik Poulsen wrote:
>> Any help? I'm getting a bit desperate? :-(
>
> The newest Search Extension code is in GitHub:
> http://github.com/radiant/radiant-search-extension/tree/master
>
> However, it removes the live search functionality.
Jan frederik Poulsen wrote:
> Any help? I'm getting a bit desperate? :-(
The newest Search Extension code is in GitHub:
http://github.com/radiant/radiant-search-extension/tree/master
However, it removes the live search functionality. You might want to use
the download link and try it out anyways
Alex Wayne wrote:
> I have whipped up a quick and simple patch to allow you set a default
> filter for pages. On a freshly bootsrapped intance, you will see a new
> value on the config table named "defaults.page.filter".
+1
--
Posted via http://www.ruby-forum.com/.
__
john muhl wrote:
> Apparently the Phusion guys have backported the security fixes to
> 1.8.6-p111 in their Ruby Enterprise edition. Might be worth checking
> out if you're stuck between security issues and a broken ruby.
>
> http://blog.phusion.nl/2008/06/23/ruby-186-p230187-broke-your-app-ruby-en
John W. Long wrote:
> On Jun 22, 2008, at 8:00 AM, Mohit Sindhwani wrote:
>> 1. How can I add pictures to the wiki? I want to add screenshots to
>> the Summer Reboot documentation.
>
> You will need to post the screenshots on another Web site to do this.
> A tool like Flickr or Skitch could be
Mohit Sindhwani wrote:
> We have been in discussion about starting up another effort to write up
> Radiant documentation. I had earlier posted out something like a Table
> of Contents that we could use as a preliminary outline. I've created
> this on the wiki as 'Summer Reboot' (in honour of the
Sean Cribbs wrote:
> The Radiant git repository has been refactored! All of the existing
> code has been added to a new, neutral, 'radiant' user on github. Please
> update your watches and remove your forks of
> github.com/seancribbs/radiant -- it will be disappearing soon. I will
> do my best t
Mohit Sindhwani wrote:
> I would like to
> initially treat this as a separate 'handbook' called 'Documentation -
> Summer Reboot' rather than into the main handbook. Hopefully, it will
> be easy to move pages around later?
I prefer this idea, as long as renaming the main section once we are
done
Casper Fabricius wrote:
> I've always found building the navigation system in Radiant quite a
> hassle, so I have recently added an to my fork of radiant
> (http://github.com/RSpace/radiant/tree/master
> ) and submitted a pull request to Sean. I have no idea if it will make
> it into Radiant 0.6.
Ben Morrow wrote:
> David Piehler wrote:
>
>> Silly question -- when working with the wiki, how do you create new
>> pages? Do you just make a link to them and it recognizes a new page has
>> been made... or something?
>
> It took me a while to figure this ou
Mohit Sindhwani wrote:
> But, it seems that there's something in editing a page that
> accesses radiantcms.org. I'm sure it's not malicious, but it does
> sometimes prevent me from getting on and editing the page because my
> browser shows 'loading...' for quite a while.
>
> I've done some lookin
Casper Fabricius wrote:
> Very nice, Mohit. If everyone can approve of this as starting outline
> for Radiant documentation, I suggest you put into a page in the wiki.
> Then we can add our names to the sections we would to like write, and
> add further sections we think is needed.
I totally misse
Mohit Sindhwani wrote:
> Sorry for the delay in pushing this out. This is roughly the first
> draft of the plan that I had. This is not split up into the sections
> that I had mentioned. I think some of these can be mixed and matched
> into the different sections. In general, this targets a per
David Piehler wrote:
> I think the core goals for the documentation are...
>
> * easily update-able
> * allow for screenshots inline with text and code samples
> * clean printouts
> * packaged with Radiant itself and each extension that wants to hook
> into it
> *
Chris Parrish wrote:
>1. Using Radiant - This section covers all the stuff users do from
> within the Radiant Admin Interface
>2. Installing Radiant - This section covers getting the source
> (including extensions) and getting it to run
>3. Extending Radiant - This section c
Mohit Sindhwani wrote:
> OK, I admit it. It's me. I'm the evil one! I really need to find the
> time to get back to the mini-project for Radiant documentation. I have
> been completely missing in action, working on an unrelated work
> project. But, I hope to get back to the Radiant documentati
I'd like to begin my work on extending the Radiant documentation, but
before that I'd like to get an idea of what others on this mailing list
are specifically planning to do so we don't duplicate effort.
Overall Goals:
* Make Radiant easier to setup for beginners via better wiki
documentation
*
Keith Bingman wrote:
> This is now on Github at
> http://github.com/kbingman/admin_tree_structure/tree/master
> It would be great if someone could chekc it out and see if it works
> for them. I have it working under the 0.6.6 Gem.
If anyone is still using the old drag-and-drop page Reorder extens
Casper Fabricius wrote:
> Okay, the wiki entry is updated:
> http://wiki.radiantcms.org/How_To_Deploy_on_Dreamhost
>
> While writing, I realized that I make quite a lot of assumptions about
> the user's knowledge in the field of Rails. I assume that the user
> know about Subversion, Capistrano, Ra
John W. Long wrote:
> We've been playing with some ideas on github. Have a look at the new
> "pages" mockups:
>
> http://github.com/jlong/radiant/tree/master/mockups/blade
Those are looking nice! I like these styles the best because they keep
all of the mouse actions on the left side of the scre
Sean Cribbs wrote:
> Looks like it's time for another release of Radiant:
> Radiant 0.6.7 "Mordant" ...
Excellent! I'm glad to see Shards integrated into the core. Question
about the switch to Haml...
Does this affect extensions that utilize Shards and ERb files (either as
.rhtml or .html.erb)
Benny Degezelle wrote:
> I just moved the extension to github
> (http://github.com/jomz/radiant-tags-extension), and will probably not
> be synchronizing the subversion repos. I only did a tiny README update
> since the svn-version. Can somebody please confirm that the version as
> found on git
Benny Degezelle wrote:
> I updated the extension with David and Tim's patches. The extension is
> now also hosted on github; http://github.com/jomz/wymeditor-for-radiant
Thanks Benny!
- Dave
--
Posted via http://www.ruby-forum.com/.
___
Radiant mail
David Piehler wrote:
> It looks like fixing Snippets compatibility with WYMeditor is a bigger
> issue, so I need to leave that alone for now, sorry.
Tim Blair has handled fixing Snippets in WYMeditor. Check out the
following for his patch:
http://gorilla-webdesign.be/artikel/48-WYM+on+R
Benny (or anyone else who might know), I came across the Tags extension
via a Google search:
http://www.nabble.com/using-acts_as_taggable-td16390502.html
This seems like it will meet my page tagging needs. I just wanted to
make sure the version made available via SVN is the newest one:
svn://zuu
Oli Studholme wrote:
> * Finally I'd love if someone could post some articles on how they set
> up a site with Radiant and the clever things they did, complete with
> template code. Something like the Art of Mission Radiant Intro[5] for
> a more complicated site, how you implemented a specific func
Daniel Collis-puro wrote:
> I've been doing a bunch of work on the Page Attachments plugin - I've
> fixed it to not require the Geometry class if the class has already been
> loaded. On my install, this has fixed the warnings.
Thanks for your work on this, Daniel.
--
Posted via http://www.ruby-
Quick question: The default Radiant 0.6.6 environment.rb file no longer
contains the "RADIANT_GEM_VERSION = '0.6.6'" flag. Is this flag still
usable, or will Radiant default to using the newest gem regardless?
Thanks,
- Dave
--
Posted via http://www.ruby-forum.com/.
__
Luigi Rizzo wrote:
> I'm using shards 0.1, and it is loaded as first extension.
Shards is up to at least 0.3 -- could the old Shards extension code be
the problem?
- Dave
--
Posted via http://www.ruby-forum.com/.
___
Radiant mailing list
Post: Radi
Alex Wayne wrote:
> Or what about ordering in general? I want to do an
> loop but I want the admin to be able to choose the order. The admin
> seems to lack any sort of page sorting functionality.
>
> So, manual or automatic, how is this done?
The following will let you determine the page or
Arik Jones wrote:
> In this case you'd honestly be better off creating a press page at the
> root-level and then calling in the children of newsroom/press. Its
> really difficult to avoid long urls when it comes to news, blog or
> chronologically added pages. I'd consider this a fringe case simp
Andrea Franz wrote:
> Yes, CopyMove copies just the page attributes and no other attributes or
> tables created by other extensions.
That makes sense. There's no reason CopyMove should account for data or
files attached with another extension (and in this case, you'd have to
duplicate the files
David Piehler wrote:
> Luigi Rizzo wrote:
>> Hi. Is there anyone on the list who has got a successful installation
>> of the copy_move extension with the latest radiant release?
>
> I did. I got the code from the SVN repository and used the following
> rake command to
Luigi Rizzo wrote:
> Hi. Is there anyone on the list who has got a successful installation
> of the copy_move extension with the latest radiant release?
I did. I got the code from the SVN repository and used the following
rake command to install:
sudo rake development radiant:extensions:copy_mov
Sean Cribbs wrote:
> You could create a special Page type that acts like a rewrite rule,
> redefining find_by_url so that it scopes to your "buried" page. If you
> want to go the simple route, you could rewrite the URL in your webserver
> before it gets to Radiant, but that would be uneditable fro
Hello,
I have a few sections in a client project that are buried a bit deep,
which creates longer-than-desired URLs...
home
- about
-- newsroom
--- press
--- announcements
--- events
The Press section URLs looks like this...
/about/newsroom/press/
/about/newsroom/press/article-name/
Is there an
Mark Gallop wrote:
> Thanks for the updates. They don't seem to be working yet but I will
> need to double check my changes.
>
> Also, you are still using .rhtml. I thought that as Radiant 0.6.6 used
> Rails 2 that you would need to use .html.erb.
I grabbed the newest version of WYMeditor and the
David Piehler wrote:
> I found a few issues relating to the admin JavaScript file move in
> Radiant 0.6.6.
>
> This problem prevents the +/- icons along the page tree from working.
> Adding back the old (or new) sitemap.js file to public/javascripts/
> solves this problem.
An
David Piehler wrote:
> It looks like the issue is 0.6.6 is outputting filter select tags with
> id="part_0_filter_id" while WYMeditor is looking for the old style of
> id="part[0][filter_id]". I've fixed this for Pages and am working on
> Snippets. I
Mark Gallop wrote:
> I am getting the same. See the comments at the bottom of the maintainers
> post - http://gorilla-webdesign.be/artikel/48-WYM+on+Radiant.
It looks like the issue is 0.6.6 is outputting filter select tags with
id="part_0_filter_id" while WYMeditor is looking for the old style o
Sean Cribbs wrote:
> Are you using shards? The sitemap issue has not been resolved yet in
> shards, IIRC.
Yes I am, so that makes sense. Thanks for clearing that up Sean.
--
Posted via http://www.ruby-forum.com/.
___
Radiant mailing list
Post: Radian
I found a few issues relating to the admin JavaScript file move in
Radiant 0.6.6.
When upgrading an existing project, the new JS files are added to
public/javascripts/admin/ as expected, but their old equivalents inside
public/javascripts/ are not removed.
Removing these files OR creating a new p
Is anyone else having trouble with Radiant 0.6.6 and WYMeditor? I'm
getting JavaScript errors on page load that are preventing the WYMeditor
Filter from loading.
My setup...
* running in development mode on 0.6.6 gem
* tested in both existing and new app (new app setup is as follows)
* environmen
Sean Cribbs wrote:
> Radiant 0.6.5 "Chisel" represents a major leap forward for Radiant.
Wow, what a mammoth changelog. Great work guys!
--
Posted via http://www.ruby-forum.com/.
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://ra
Nice work on the podcast!
The Digital Pulp team talks about how their clients love the Radiant
admin interface -- I've experienced similar feedback from my clients.
They feel empowered by Radiant, not overwhelmed. I've gotten a lot of
comments like "Wait, that's all I have to do to change the t
Sean Cribbs wrote:
> ResponseCache.instance should do the trick.
Earlier today I tried:
cache = ResponseCache.instance
cache.clear
... and also ...
ResponseCache.instance.clear
Both deleted all the files from my /public directory instead of my
/cache directory. What seemed to be happening was
This is kind of a weird question, but is there a way to access the
current ResponseCache instance during the activation method of an
extension?
I'd like to be able to call its clear method to empty the cache when I
start up a specific extension, so I don't have to manually empty it.
Thanks!
- Dav
Andrea Franz wrote:
> On Thu, Apr 17, 2008 at 5:18 PM, David Piehler <[EMAIL PROTECTED]>
> wrote:
>>
>> I guess what I am really asking is if I can take advantage of these
>> existing plug-ins, or if I need to use attachment_fu and wymeditor on
>> their own in
David Piehler wrote:
> Chris Barnes wrote:
>> How do you get the new page type to show as an option under page types
>> in the radiant admin?
>
> The way I've done it in the past is (example from my Schools extension):
>
> In .../schools/schools_extension.rb
>
Chris Barnes wrote:
> How do you get the new page type to show as an option under page types
> in the radiant admin?
The way I've done it in the past is (example from my Schools extension):
In .../schools/schools_extension.rb
def activate
admin.tabs.add "Schools", "/manage/schools", :after =>
David Piehler wrote:
> I'm building a few extensions for a client project and would like to tie
> Page_Attachments and WYMeditor into the new/edit screens of my
> extensions. Currently Shards allows these two extensions to integrate
> with Radiant's page editing tools, but h
I'm building a few extensions for a client project and would like to tie
Page_Attachments and WYMeditor into the new/edit screens of my
extensions. Currently Shards allows these two extensions to integrate
with Radiant's page editing tools, but how would I get them to play nice
with my custom admin
Sean Cribbs wrote:
> Soon, you won't have to. It's ambitious, but I intend to have
> "accents", the extension registry up by RailsConf. With it will be a
> command-line tool to install and remove extensions that, provided the
> author correctly assigns them, will run all of the necessary rake tas
Sean Cribbs wrote:
> Thanks to "Radiant Day", we're ready for another release candidate.
> http://radiantcms.org/blog/archives/2008/04/05/radiant-0-6-5-release-candidate-2/
Great work guys! I haven't had the opportunity to test out the 0.6.5 RCs
yet, but I was curious as to whether Radiant sites
J Aaron Farr wrote:
> David Piehler <[EMAIL PROTECTED]> writes:
>
>> J Aaron Farr wrote:
>>> - An extension for adding arbitrary fields to pages (like meta, but
>>>without having to write code)
>>
>> This one sounds really helpful to me.
>
J Aaron Farr wrote:
> - An extension for adding arbitrary fields to pages (like meta, but
>without having to write code)
This one sounds really helpful to me.
- Dave
--
Posted via http://www.ruby-forum.com/.
___
Radiant mailing list
Post: Radi
70 matches
Mail list logo
