Hi,
I have the same problem. My (old) site with radiant 0.6.9 and sns is
working fine, but yesterday I installed a new one with radiant 0.7.0,
and got the same stack when trying to access /admin/css or /admin/js.
I think it's a problem with the haml plugin.
The weird thing is that there is no
I'm finally getting around to looking at the template that Sean uses for
blogging:
http://pastie.org/273417
(Hmm.. pastie seems broken at the moment.)
Some questions:
1. The root page (/) and the /Articles page are effectively identical. Is
there a reason one couldn't just render the other?
Nevermind I found the esoteric mailer config setting that enforces the
correct behavior. Is there any reason why the strange behavior described
above is the default one?
On Sun, Feb 8, 2009 at 10:32 PM, john muhl johnm...@gmail.com wrote:
I'm not sure if it has to do with 0.7.0 or the mailer
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
Jay Levitt wrote:
(Hmm.. pastie seems broken at the moment.)
Here's one that should be readable: http://pastie.org/384089
Some questions:
1. The root page (/) and the /Articles page are effectively identical. Is
there a reason one couldn't just render the other? I realize that the
Since this question is going to be asked a number of times as people
begin to move their sites to v0.7 I thought I would begin the thread.
What extensions are known not to work with v0.7?
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search:
Chaim Kirby wrote:
I am having trouble with the copy_move extension under 0.6.9. I now know
that I need to use an older version of the extension. How do I go about
uninstalling the extension that I have currently installed so I can
switch to the correct version?
You don't have to remove
roughly...
admin_tree_structure
concurrent_draft
dynamic_grouping
exception_notification
file_based_layout
jargon
legacy_path_handler
link_roll
location
page_attachments_xsendfile
page_event
page_group_rbac_migrator
page_meta
page_review_process
page_versioning
rbac_base
rbac_page_edit
Is there any way to break tags up so It can be made into a dropdown?
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Chaim Kirby wrote:
If I were to phrase the question more generically: How does one remove
an extension they are no longer interested in having installed? Is
there a process to do it? As a note, I have been using the git clone
_extension_ into vendor/extensions, migrate, update extension
Steven Southard wrote:
Is there any way to break tags up so It can be made into a dropdown?
I imagine it would be something like this:
r:find url=/something/
select
r:children:each
option value=r:slug /r:title //option
/r:children:each
/select
/r:find
// Nate
Ok, Thanks!
Chaim Kirby
chaim.ki...@childrens.harvard.edu
From: radiant-boun...@radiantcms.org [radiant-boun...@radiantcms.org] On Behalf
Of N. Turnage [pixeln...@gmail.com]
Sent: Monday, February 09, 2009 7:57 PM
To: radiant@radiantcms.org
Subject: Re:
Really? It looks like it would make a nice dropdown of something, yet
I don't see how that accesses tags at all.
On Feb 9, 2009, at 7:01 PM, N. Turnage wrote:
Steven Southard wrote:
Is there any way to break tags up so It can be made into a dropdown?
I imagine it would be something like
Two things -
1) You can typically use `script/extension uninstall extension_name` to
uninstall an extension - although it may need to be on the registry.
2) In 0.7, the 'extension_meta' table is no longer used. Once you have
migrated any extension, all extension migrations are recorded in the
Sean Cribbs wrote:
Two things -
1) You can typically use `script/extension uninstall extension_name`
to uninstall an extension - although it may need to be on the registry.
I have never done it that way, so I didn't want to recommend it. But,
thanks for the alternative method.
2) In 0.7, the
While trying to express what it was I was really after, I came up with
this and it works fine for what I wanted. Thank you for you assistance.
select
r:all_tags:eachoption value=/tags/?tag=r:name /r:name //
option/r:all_tags:each
/select
//Steven
On Feb 9, 2009, at 7:17 PM, N. Turnage
r:all_tags:each seems to list tags even if they're not currently
being used. Is there any way to list only tags that are being used?
Or is there any way to manage tag or at least remove unused tags?
//Steven
___
Radiant mailing list
Post:
N. Turnage wrote:
Since this question is going to be asked a number of times as people
begin to move their sites to v0.7 I thought I would begin the thread.
What extensions are known not to work with v0.7?
Could we make this a page on the wiki instead? May I request that
people who have
Mohit Sindhwani wrote:
N. Turnage wrote:
Since this question is going to be asked a number of times as people
begin to move their sites to v0.7 I thought I would begin the thread.
What extensions are known not to work with v0.7?
Could we make this a page on the wiki instead? May I request
Hi all,
I am working on an extension that needs to render pages as part of a
rake task. This works, but I have run into a problem when using r:url
in my content. Because there is no request object, the relative_url_for
method in standard_tags.rb throws an Exception. As a workaround, I've
20 matches
Mail list logo
