Rufo Sanchez wrote:
On Sat, Apr 19, 2008 at 8:28 PM, Tom Cloyd [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
locate spewed out the files in
/var/lib/gems/1.8/doc/radiant-0.6.4/, of course. It also listed
/var/lib/gems/1.8/bin/radiant, so, I executed the
radiant --database
Tom Cloyd wrote:
[snip]
I realize that being rather new to Linux there is much I don't know,
but this latest piece of secret knowledge flabbergasts me. Why can't
radiant use the same path all the other gems seems to successfully
use? How could I ever have figured out this problem without your
Every extension that used shards has been rendered completely useless.
None of the Admin UI additions provided by extensions show up anymore.
Is there a way to fix this, has shards been integrated into core? I
need
help!
Arik,
This is a bug that snuck in to 0.6.5. Sean should be pushing a
Looks like it's time for another release of Radiant:
http://radiantcms.org/download/
Radiant 0.6.6 Chiseled corrects two showstopper bugs in yesterday's 0.6.5
release that affect upgrading existing installations and the proper
functioning of view templates in extensions. All users of 0.6.5
I may be daft, but I'm not finding any information on using Javascript
inside Radiant CMS sites.
Are there some guidelines on how to do this?
Thanks
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search:
If you mean on the public content, then use Javascript however you
would with any other system: link to the JS files on your server and go.
If you mean on the admin side, you can install the Shards extension
(read this http://wiki.radiantcms.org/Using_the_Shards_Extension)
On Apr 20,
Fixed everything right up, thanks Sean!
--
Posted via http://www.ruby-forum.com/.
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
On Apr 19, 2008, at 9:12 PM, Phi Sanders wrote:
After upgrading a site from 0.6.4 to 0.6.5, I can no longer
effectively use the Radiant admin interface.
Clicking on any of the Pages give the error below, and layouts just
present the unprocessed radius tag r:content / The site itself
