Re: Fwd: [Radiant] Using Git with Radiant Extensions
> I guess the question is "is a submodule (the copy checked out into my > project) a full-fledged git repo that you can branch, change, etc (all from > within the project)?" Chris, I'd recommend you read this. http://git.or.cz/gitwiki/GitSubmoduleTutorial It helped me understand submodules. Cheers, Marty ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Using Git with Radiant Extensions
On Oct 17, 2008, at 11:28 PM, Chris Parrish wrote: Tim Gossett wrote: On Fri, Oct 17, 2008 at 11:03 AM, Chris Parrish < [EMAIL PROTECTED]> wrote: So, to make sure I understand... If I have an extension of mine in a submodule of a project, I can develop within that extension: * make changes in that copy of the extension (testing its behavior as part of the project) * commit those changes to the submodule's repo * manage branching (gitk, etc) from within that submodule If so, that helps me a lot. Everything I'd read made it sound like submodules don't behave like a working git repo which is why I thought you couldn't push changes back to the original -- that submodules only permitted data transfer one-way (from source to your local copy). The way I understand it, from a developing perspective, the extension is simply a git repo that happens to exist within another git repo. You can pull, develop, commit, and push with the extension just as you would any other project managed with git. The difference here is when you pull, develop, commit, and push from the master project (the Radiant install in your case), you'll need to consider what's happening with your extension. Do I understand it correctly? Hmm. Now I'm not sure that I've got git yet... I understand that if my submodule's repo changes, I need to go to the project's repo and 'git submodule update' as Sean mentioned. But what if I make a change in my project and that makes me think "hey, that means I need to change something in my extension too." Can I change the code directly in the extension (submodule) and somehow tell git to update the extension's source repo? Better still can I create a branch of my extension using the submodule to try out some ideas as they relate to my project and otherwise manage the submodule like any git repo? Or do I have to go to the extension's repo and work on my changes there (apart from the Radiant project), then go back to my project and update those changes into my submodule? I guess the question is "is a submodule (the copy checked out into my project) a full-fledged git repo that you can branch, change, etc (all from within the project)?" Yes. Just "cd vendor/extensions/whatever" and do your git stuff there, commit those changes from there to that repo, then "cd ../../.." and commit the altered submodule. I'm no pro with git, but I'm relatively confident that'll do it. -Jim ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: Fwd: [Radiant] Using Git with Radiant Extensions
Tim Gossett wrote: On Fri, Oct 17, 2008 at 11:03 AM, Chris Parrish < [EMAIL PROTECTED]> wrote: So, to make sure I understand... If I have an extension of mine in a submodule of a project, I can develop within that extension: * make changes in that copy of the extension (testing its behavior as part of the project) * commit those changes to the submodule's repo * manage branching (gitk, etc) from within that submodule If so, that helps me a lot. Everything I'd read made it sound like submodules don't behave like a working git repo which is why I thought you couldn't push changes back to the original -- that submodules only permitted data transfer one-way (from source to your local copy). The way I understand it, from a developing perspective, the extension is simply a git repo that happens to exist within another git repo. You can pull, develop, commit, and push with the extension just as you would any other project managed with git. The difference here is when you pull, develop, commit, and push from the master project (the Radiant install in your case), you'll need to consider what's happening with your extension. Do I understand it correctly? Hmm. Now I'm not sure that I've got git yet... I understand that if my submodule's repo changes, I need to go to the project's repo and 'git submodule update' as Sean mentioned. But what if I make a change in my project and that makes me think "hey, that means I need to change something in my extension too." Can I change the code directly in the extension (submodule) and somehow tell git to update the extension's source repo? Better still can I create a branch of my extension using the submodule to try out some ideas as they relate to my project and otherwise manage the submodule like any git repo? Or do I have to go to the extension's repo and work on my changes there (apart from the Radiant project), then go back to my project and update those changes into my submodule? I guess the question is "is a submodule (the copy checked out into my project) a full-fledged git repo that you can branch, change, etc (all from within the project)?" -Chris -- Tim ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: BIG problems after removing page_attachments
I was never able to get it to work. I guess I should try it again before I start spreading FUD, eh? ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant tag errors
On Oct 17, 2008, at 10:04 PM, Joe Van Dyk wrote: This is in production mode. I'm using the radiant exception notifier plugin, which lets you put up your own 500 page. I'm using Radiant to build a website that lets some non-technical people update it. I'm trying to make it as easy as possible. It doesn't seem right, if one person makes an error on a snippet that's being used by every page, to not show the rest of the page's content (and replace the snippet or tag with the error message). That would let them easily figure out where the error occurred and would give them clues to how to fix it. Joe From my past experience and this recent test, that is what *should* be happening. What does the 500 error say? -Jim ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: BIG problems after removing page_attachments
Why can't you use the images in a stylesheet? Just specify the image URL in the stylesheet. On Fri, Oct 17, 2008 at 6:36 PM, Nate Turnage <[EMAIL PROTECTED]> wrote: > On Fri, Oct 17, 2008 at 12:39 PM, Arik Jones <[EMAIL PROTECTED]> wrote: > >> Paperclipped doesn't use RMagick (thanks to the paperclip plugin), >> instead it directly accesses ImageMagick which does wonders for memory >> consumption. You can drag and drop assets into the edit page text area. >> ALL assets are accessible to all pages, unlike page attachments where it >> didn't give you access to any previously uploaded attachments (you'd >> have to re-upload it or access it via another page or it's parent page >> using additional radiant tags). >> > > > But unlike page_attachments, you cannot use the images in a stylesheet. You > can use paperclipped to manage PDFs and Flash files, though. And the bucket > metaphor is nice for attaching images to pages. > > > > ~Nate > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant tag errors
This is in production mode. I'm using the radiant exception notifier plugin, which lets you put up your own 500 page. I'm using Radiant to build a website that lets some non-technical people update it. I'm trying to make it as easy as possible. It doesn't seem right, if one person makes an error on a snippet that's being used by every page, to not show the rest of the page's content (and replace the snippet or tag with the error message). That would let them easily figure out where the error occurred and would give them clues to how to fix it. Joe On Fri, Oct 17, 2008 at 5:47 PM, Jim Gay <[EMAIL PROTECTED]> wrote: > In what environment are you testing this? > > When doing in development I get a StandardTags::TagError page > In production I just get a message "undefined tag 'asdf'" > > > On Oct 17, 2008, at 3:31 PM, Joe Van Dyk wrote: > >> Err, sure: >> >> On Fri, Oct 17, 2008 at 12:28 PM, Manuel Meurer <[EMAIL PROTECTED]> >> wrote: >>> >>> What exactly do you mean by "messes up a radiant tag"? >>> Do you have an example? > > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: BIG problems after removing page_attachments
On Fri, Oct 17, 2008 at 12:39 PM, Arik Jones <[EMAIL PROTECTED]> wrote: > Paperclipped doesn't use RMagick (thanks to the paperclip plugin), > instead it directly accesses ImageMagick which does wonders for memory > consumption. You can drag and drop assets into the edit page text area. > ALL assets are accessible to all pages, unlike page attachments where it > didn't give you access to any previously uploaded attachments (you'd > have to re-upload it or access it via another page or it's parent page > using additional radiant tags). > But unlike page_attachments, you cannot use the images in a stylesheet. You can use paperclipped to manage PDFs and Flash files, though. And the bucket metaphor is nice for attaching images to pages. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] serving public images
On Oct 17, 2008, at 8:07 PM, Michael Delaney wrote:
hi,
i'm a newbie on the radiant front. got a q on images. i've created a
stylesheet using a page with a content type of text/css with
/> as the body. its published and the css is working fine.
the only issue i have is where i want to use a tiled image for a faux
column layout. when i reference the image in the css it doesnt render.
#wrap
{
max-width: 1200px;
min-width: 750px;
background: url('/images/wrap-background.jpg') repeat-y 70% 0;
}
i've placed the image in the public/images folder.
when i try to get the image directly i get a 404, is there some way
for
me to get radiant to server the image directly. i saw in the admin for
example it uses /images/admin/image.png?12345.
at this stage i'm just trying to get up and running with something
simple.
any help is much appreciated.
regads.
Are you certain that this image exists on the server where you expect
it?
Judging by the fact that you get a 404 when trying to access it, I'd
guess that it does not exist where you expect.
Do other images work on your site where you might use ?
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant tag errors
With and no accompanying end tag, I get a
Radius::MissingEndTagError page in development. In production I get
the message "end tag not found for start tag `children:each'"
On Oct 17, 2008, at 6:52 PM, Joe Van Dyk wrote:
What if the user types in:
(forgets to close the tag)
(uses title instead of id)
(doesn't specify the name)
Instead of the exceptions bubbling up to the top and just seeing a 500
error page, wouldn't it be better to catch those errors and insert the
error message directly into page content?
Joe
On Fri, Oct 17, 2008 at 3:44 PM, Manuel Meurer <[EMAIL PROTECTED]
> wrote:
From radius.rb #284
# Like method_missing for objects, but fired when a tag is
undefined.
# Override in your own Context to change what happens when a tag is
# undefined. By default this method raises an UndefinedTagError.
def tag_missing(name, attributes, &block)
raise UndefinedTagError.new(name)
end
Guess it's just a preference thing.
I like strong validation.
Manuel
On Fri, Oct 17, 2008 at 11:54 PM, Joe Van Dyk <[EMAIL PROTECTED]>
wrote:
Makes sense -- why wouldn't that be that way by default?
Joe
On Fri, Oct 17, 2008 at 1:37 PM, Manuel Meurer <[EMAIL PROTECTED]
> wrote:
Change #28 in vendor/radiant/app/models/page_context.rb from
raise StandardTags::TagError.new(e.message)
to
"Radius error: #{e.message}"
Manuel
On Fri, Oct 17, 2008 at 9:31 PM, Joe Van Dyk <[EMAIL PROTECTED]>
wrote:
Err, sure:
On Fri, Oct 17, 2008 at 12:28 PM, Manuel Meurer <[EMAIL PROTECTED]
> wrote:
What exactly do you mean by "messes up a radiant tag"?
Do you have an example?
Manuel
On Fri, Oct 17, 2008 at 7:00 PM, Joe Van Dyk
<[EMAIL PROTECTED]> wrote:
Right now, when an editor messes up a radiant tag, a 500 page
gets rendered.
Would it be possible to display the page content, except for the
radiant tag that had the error, and show the error message in
place of
that tag?
Joe
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] serving public images
On Oct 17, 2008, at 8:07 PM, Michael Delaney wrote:
hi,
i'm a newbie on the radiant front. got a q on images. i've created a
stylesheet using a page with a content type of text/css with
/> as the body. its published and the css is working fine.
the only issue i have is where i want to use a tiled image for a faux
column layout. when i reference the image in the css it doesnt render.
#wrap
{
max-width: 1200px;
min-width: 750px;
background: url('/images/wrap-background.jpg') repeat-y 70% 0;
}
i've placed the image in the public/images folder.
when i try to get the image directly i get a 404, is there some way
for
me to get radiant to server the image directly. i saw in the admin for
example it uses /images/admin/image.png?12345.
at this stage i'm just trying to get up and running with something
simple.
any help is much appreciated.
regads.
Are you certain that this image exists on the server where you expect
it?
Judging by the fact that you get a 404 when trying to access it, I'd
guess that it does not exist where you expect.
Do other images work on your site where you might use ?
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant tag errors
In what environment are you testing this? When doing in development I get a StandardTags::TagError page In production I just get a message "undefined tag 'asdf'" On Oct 17, 2008, at 3:31 PM, Joe Van Dyk wrote: Err, sure: On Fri, Oct 17, 2008 at 12:28 PM, Manuel Meurer <[EMAIL PROTECTED] > wrote: What exactly do you mean by "messes up a radiant tag"? Do you have an example? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] serving public images
hi,
i'm a newbie on the radiant front. got a q on images. i've created a
stylesheet using a page with a content type of text/css with as the body. its published and the css is working fine.
the only issue i have is where i want to use a tiled image for a faux
column layout. when i reference the image in the css it doesnt render.
#wrap
{
max-width: 1200px;
min-width: 750px;
background: url('/images/wrap-background.jpg') repeat-y 70% 0;
}
i've placed the image in the public/images folder.
when i try to get the image directly i get a 404, is there some way for
me to get radiant to server the image directly. i saw in the admin for
example it uses /images/admin/image.png?12345.
at this stage i'm just trying to get up and running with something
simple.
any help is much appreciated.
regads.
--
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
Re: [Radiant] Radiant tag errors
As I said, I am pretty happy with Radius' tight validation, but I am
sure there is a way to fix this, probably as easy as defining your own
Radius Context and overwriting a couple of methods.
Poke around in radius.rb a bit, it's commented very well.
Manuel
On Sat, Oct 18, 2008 at 12:52 AM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
> What if the user types in:
>
> (forgets to close the tag)
>
> (uses title instead of id)
>
> (doesn't specify the name)
>
> Instead of the exceptions bubbling up to the top and just seeing a 500
> error page, wouldn't it be better to catch those errors and insert the
> error message directly into page content?
>
> Joe
>
> On Fri, Oct 17, 2008 at 3:44 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote:
>> >From radius.rb #284
>>
>># Like method_missing for objects, but fired when a tag is undefined.
>># Override in your own Context to change what happens when a tag is
>># undefined. By default this method raises an UndefinedTagError.
>>def tag_missing(name, attributes, &block)
>> raise UndefinedTagError.new(name)
>>end
>>
>> Guess it's just a preference thing.
>> I like strong validation.
>>
>> Manuel
>>
>> On Fri, Oct 17, 2008 at 11:54 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
>>> Makes sense -- why wouldn't that be that way by default?
>>>
>>> Joe
>>>
>>> On Fri, Oct 17, 2008 at 1:37 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote:
Change #28 in vendor/radiant/app/models/page_context.rb from
raise StandardTags::TagError.new(e.message)
to
"Radius error: #{e.message}"
Manuel
On Fri, Oct 17, 2008 at 9:31 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
> Err, sure:
>
> On Fri, Oct 17, 2008 at 12:28 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote:
>> What exactly do you mean by "messes up a radiant tag"?
>> Do you have an example?
>>
>> Manuel
>>
>> On Fri, Oct 17, 2008 at 7:00 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
>>> Right now, when an editor messes up a radiant tag, a 500 page gets
>>> rendered.
>>>
>>> Would it be possible to display the page content, except for the
>>> radiant tag that had the error, and show the error message in place of
>>> that tag?
>>>
>>> Joe
>>> ___
>>> Radiant mailing list
>>> Post: Radiant@radiantcms.org
>>> Search: http://radiantcms.org/mailing-list/search/
>>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>>
>> ___
>> Radiant mailing list
>> Post: Radiant@radiantcms.org
>> Search: http://radiantcms.org/mailing-list/search/
>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>
> ___
> Radiant mailing list
> Post: Radiant@radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>> ___
>>> Radiant mailing list
>>> Post: Radiant@radiantcms.org
>>> Search: http://radiantcms.org/mailing-list/search/
>>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>>
>> ___
>> Radiant mailing list
>> Post: Radiant@radiantcms.org
>> Search: http://radiantcms.org/mailing-list/search/
>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>
> ___
> Radiant mailing list
> Post: Radiant@radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Updated fork of radiant-mail-to-extension
Yep, I use in my parameterized snippets extension: http://github.com/manuelmeurer/radiant-parameterized-snippets-extension/ The idea originates from here, though: http://www.nabble.com/Snippets-with-Parameter(s)-td19772449.html > BTW, anyone heard anything about a Radius tag? Or anything about > setting arbitrary page variables? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant tag errors
What if the user types in:
(forgets to close the tag)
(uses title instead of id)
(doesn't specify the name)
Instead of the exceptions bubbling up to the top and just seeing a 500
error page, wouldn't it be better to catch those errors and insert the
error message directly into page content?
Joe
On Fri, Oct 17, 2008 at 3:44 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote:
> >From radius.rb #284
>
># Like method_missing for objects, but fired when a tag is undefined.
># Override in your own Context to change what happens when a tag is
># undefined. By default this method raises an UndefinedTagError.
>def tag_missing(name, attributes, &block)
> raise UndefinedTagError.new(name)
>end
>
> Guess it's just a preference thing.
> I like strong validation.
>
> Manuel
>
> On Fri, Oct 17, 2008 at 11:54 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
>> Makes sense -- why wouldn't that be that way by default?
>>
>> Joe
>>
>> On Fri, Oct 17, 2008 at 1:37 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote:
>>> Change #28 in vendor/radiant/app/models/page_context.rb from
>>>
>>> raise StandardTags::TagError.new(e.message)
>>>
>>> to
>>>
>>> "Radius error: #{e.message}"
>>>
>>> Manuel
>>>
>>> On Fri, Oct 17, 2008 at 9:31 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
Err, sure:
On Fri, Oct 17, 2008 at 12:28 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote:
> What exactly do you mean by "messes up a radiant tag"?
> Do you have an example?
>
> Manuel
>
> On Fri, Oct 17, 2008 at 7:00 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
>> Right now, when an editor messes up a radiant tag, a 500 page gets
>> rendered.
>>
>> Would it be possible to display the page content, except for the
>> radiant tag that had the error, and show the error message in place of
>> that tag?
>>
>> Joe
>> ___
>> Radiant mailing list
>> Post: Radiant@radiantcms.org
>> Search: http://radiantcms.org/mailing-list/search/
>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>
> ___
> Radiant mailing list
> Post: Radiant@radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>> ___
>>> Radiant mailing list
>>> Post: Radiant@radiantcms.org
>>> Search: http://radiantcms.org/mailing-list/search/
>>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>>
>> ___
>> Radiant mailing list
>> Post: Radiant@radiantcms.org
>> Search: http://radiantcms.org/mailing-list/search/
>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>
> ___
> Radiant mailing list
> Post: Radiant@radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant tag errors
>From radius.rb #284
# Like method_missing for objects, but fired when a tag is undefined.
# Override in your own Context to change what happens when a tag is
# undefined. By default this method raises an UndefinedTagError.
def tag_missing(name, attributes, &block)
raise UndefinedTagError.new(name)
end
Guess it's just a preference thing.
I like strong validation.
Manuel
On Fri, Oct 17, 2008 at 11:54 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
> Makes sense -- why wouldn't that be that way by default?
>
> Joe
>
> On Fri, Oct 17, 2008 at 1:37 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote:
>> Change #28 in vendor/radiant/app/models/page_context.rb from
>>
>> raise StandardTags::TagError.new(e.message)
>>
>> to
>>
>> "Radius error: #{e.message}"
>>
>> Manuel
>>
>> On Fri, Oct 17, 2008 at 9:31 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
>>> Err, sure:
>>>
>>> On Fri, Oct 17, 2008 at 12:28 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote:
What exactly do you mean by "messes up a radiant tag"?
Do you have an example?
Manuel
On Fri, Oct 17, 2008 at 7:00 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
> Right now, when an editor messes up a radiant tag, a 500 page gets
> rendered.
>
> Would it be possible to display the page content, except for the
> radiant tag that had the error, and show the error message in place of
> that tag?
>
> Joe
> ___
> Radiant mailing list
> Post: Radiant@radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>> ___
>>> Radiant mailing list
>>> Post: Radiant@radiantcms.org
>>> Search: http://radiantcms.org/mailing-list/search/
>>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>>
>> ___
>> Radiant mailing list
>> Post: Radiant@radiantcms.org
>> Search: http://radiantcms.org/mailing-list/search/
>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>
> ___
> Radiant mailing list
> Post: Radiant@radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant tag errors
Makes sense -- why wouldn't that be that way by default?
Joe
On Fri, Oct 17, 2008 at 1:37 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote:
> Change #28 in vendor/radiant/app/models/page_context.rb from
>
> raise StandardTags::TagError.new(e.message)
>
> to
>
> "Radius error: #{e.message}"
>
> Manuel
>
> On Fri, Oct 17, 2008 at 9:31 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
>> Err, sure:
>>
>> On Fri, Oct 17, 2008 at 12:28 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote:
>>> What exactly do you mean by "messes up a radiant tag"?
>>> Do you have an example?
>>>
>>> Manuel
>>>
>>> On Fri, Oct 17, 2008 at 7:00 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
Right now, when an editor messes up a radiant tag, a 500 page gets
rendered.
Would it be possible to display the page content, except for the
radiant tag that had the error, and show the error message in place of
that tag?
Joe
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>> ___
>>> Radiant mailing list
>>> Post: Radiant@radiantcms.org
>>> Search: http://radiantcms.org/mailing-list/search/
>>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>>
>> ___
>> Radiant mailing list
>> Post: Radiant@radiantcms.org
>> Search: http://radiantcms.org/mailing-list/search/
>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>
> ___
> Radiant mailing list
> Post: Radiant@radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Paperclipped extension: Default partial not found!
I just installed paperclipped: http://github.com/jomz/paperclipped/tree/master and everything went ok during installation. When I go into Admin I get the following message on the Edit page: `/assets/show_bucket_link' default partial not found! It also alerts of of missing templates when I clicked on the Assets tab. Not sure what I am missing ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Nested tags
Here you go: http://github.com/manuelmeurer/radius-improved/tree/master Manuel On Fri, Oct 17, 2008 at 10:15 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote: > On Sat, Oct 11, 2008 at 3:59 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote: >> I am using an extension that gives me parameterized snippets (like >> here: http://www.ruby-forum.com/topic/125007#601242). Now, if I pass a >> value into a snippet, I would like to be able to pass it on to a tag >> as a parameter, which isn't currently possible in Radius. >> E.g., I want to do this: >> >> Page: >> >> >> >> Snippet my_snippet: >> >> >> >> With a few changes in Radius this works for me now. >> I didn't test it a lot yet but at least for what I want to use it for >> it works fine. >> >> The changes were quite simple so I wonder why it wasn't done like that >> from the beginning. >> Did anyone else ever feel the need to do something like that? > > Yes, we do feel that need. Please release ur codez! > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant tag errors
Change #28 in vendor/radiant/app/models/page_context.rb from
raise StandardTags::TagError.new(e.message)
to
"Radius error: #{e.message}"
Manuel
On Fri, Oct 17, 2008 at 9:31 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
> Err, sure:
>
> On Fri, Oct 17, 2008 at 12:28 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote:
>> What exactly do you mean by "messes up a radiant tag"?
>> Do you have an example?
>>
>> Manuel
>>
>> On Fri, Oct 17, 2008 at 7:00 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
>>> Right now, when an editor messes up a radiant tag, a 500 page gets rendered.
>>>
>>> Would it be possible to display the page content, except for the
>>> radiant tag that had the error, and show the error message in place of
>>> that tag?
>>>
>>> Joe
>>> ___
>>> Radiant mailing list
>>> Post: Radiant@radiantcms.org
>>> Search: http://radiantcms.org/mailing-list/search/
>>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>>
>> ___
>> Radiant mailing list
>> Post: Radiant@radiantcms.org
>> Search: http://radiantcms.org/mailing-list/search/
>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>
> ___
> Radiant mailing list
> Post: Radiant@radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Nested tags
On Sat, Oct 11, 2008 at 3:59 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote: > I am using an extension that gives me parameterized snippets (like > here: http://www.ruby-forum.com/topic/125007#601242). Now, if I pass a > value into a snippet, I would like to be able to pass it on to a tag > as a parameter, which isn't currently possible in Radius. > E.g., I want to do this: > > Page: > > > > Snippet my_snippet: > > > > With a few changes in Radius this works for me now. > I didn't test it a lot yet but at least for what I want to use it for > it works fine. > > The changes were quite simple so I wonder why it wasn't done like that > from the beginning. > Did anyone else ever feel the need to do something like that? Yes, we do feel that need. Please release ur codez! ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] TinyMCE Editor + Adding Tabs/PageParts = Fail?
I installed this version of TinyMCE: http://github.com/nullset/radiant-tinymce/tree/master When I click the '+' icon for adding a new tab or page part to the page, this happens: http://img.skitch.com/20081017-e6fyfbp1fdybsxs3745quj9rif.jpg Looks like something javascript related, any ideas? Is there a better tinymce extension out there? Joe ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant tag errors
Err, sure: On Fri, Oct 17, 2008 at 12:28 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote: > What exactly do you mean by "messes up a radiant tag"? > Do you have an example? > > Manuel > > On Fri, Oct 17, 2008 at 7:00 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote: >> Right now, when an editor messes up a radiant tag, a 500 page gets rendered. >> >> Would it be possible to display the page content, except for the >> radiant tag that had the error, and show the error message in place of >> that tag? >> >> Joe >> ___ >> Radiant mailing list >> Post: Radiant@radiantcms.org >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant >> > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant tag errors
What exactly do you mean by "messes up a radiant tag"? Do you have an example? Manuel On Fri, Oct 17, 2008 at 7:00 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote: > Right now, when an editor messes up a radiant tag, a 500 page gets rendered. > > Would it be possible to display the page content, except for the > radiant tag that had the error, and show the error message in place of > that tag? > > Joe > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Something like TinyMce + Radiant tags?
I believe you can trick the TinyMCE filter extension into ignoring Radius tags, if it doesn't include that already. Sean Joe Van Dyk wrote: Is there an editor out there that works similarly to TinyMce, but lets you do radiant tags easily? Joe ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Something like TinyMce + Radiant tags?
Is there an editor out there that works similarly to TinyMce, but lets you do radiant tags easily? Joe ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: BIG problems after removing page_attachments
Joe Van Dyk wrote: > On Fri, Aug 29, 2008 at 9:18 PM, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: >> OK, guys. I gave in to the hype about paperclipped, about how it will >> make my whites whiter and make my food taste better and all that jazz. >> Weeel, I need to get rid of page_attachments first, so I did, and >> now my site won't start back up. > > How's paperclipped better than attachment_fu/page_attachments? Paperclipped doesn't use RMagick (thanks to the paperclip plugin), instead it directly accesses ImageMagick which does wonders for memory consumption. You can drag and drop assets into the edit page text area. ALL assets are accessible to all pages, unlike page attachments where it didn't give you access to any previously uploaded attachments (you'd have to re-upload it or access it via another page or it's parent page using additional radiant tags). Someone help me if I've missed any features. -- 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
Re: [Radiant] slug inside url_matches
I patched Radius so that you can use tags as attributes in other tags. (Posted to this list five days ago) Extremely useful and only a couple of lines have to be changed actually. If anyone is interested I can make a patch. Manuel On Thu, Oct 16, 2008 at 7:12 PM, Chris Parrish <[EMAIL PROTECTED]> wrote: > For sure Radiant's parser won't permit tags within tags but this sounds like > a job for... > an extension I built and need to re-release. > > I have some pretty lofty goals for this weekend involving Radiant. And > getting my conditionals extension back online is one of them. So maybe > I'll have something for you next week (fingers crossed). > > Just FYI, using my extension you'd do something like: >your stuff here > > -Chris > > > Jeffrey Jones wrote: >> >> Hoi all, >> >> Does anyone know how I could get the following working? >> >> > ignore_case="true"> style="display: none;" > >> >> Basically, if the page's slug is in the url somewhere I want the css style >> display to be none. I have tried with double and single quotes but this >> doesn't appear to be working. Using a hard-coded value instead works. I am >> assuming the isn't being translated to the actual slug value >> before being matched in the regexp. >> >> Thanks >> >> Jeff >> >> >> ___ >> Radiant mailing list >> Post: Radiant@radiantcms.org >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] BIG problems after removing page_attachments
On Fri, Aug 29, 2008 at 9:18 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > OK, guys. I gave in to the hype about paperclipped, about how it will > make my whites whiter and make my food taste better and all that jazz. > Weeel, I need to get rid of page_attachments first, so I did, and > now my site won't start back up. How's paperclipped better than attachment_fu/page_attachments? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] navigation tag question
Sure. Have a look at standard_tags.rb #667 and hack away. Better yet, create a better_navigation extension and publish it on Github so everybody else can use it as well. Manuel On Fri, Oct 17, 2008 at 6:58 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote: > Wow -- that's craziness. Wonder if it would be possible or advisable > to modify the navigation tag to be smarter as to what it highlights as > being the active link? > > On Fri, Oct 17, 2008 at 8:44 AM, Manuel Meurer <[EMAIL PROTECTED]> wrote: >> I found the r:navigation tag become too limited to do that kind of stuff. >> See below for an example of how to do your navigation "by hand". >> >> >> >>active> matches="^/$">inactive">Home >> >> >>> class="activeinactive"> >> >> >> >> >> >> > class="activeinactive"> >> >> >> >> >> >> >> >> >> >> >> On Thu, Oct 16, 2008 at 9:56 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote: >>> In the below case, I would want the About link to be highlighted, >>> since that's the closest match to the current page. Is there a good >>> way to do that? >>> >>> Joe >>> >>> On Thu, Oct 16, 2008 at 12:39 PM, Sean Cribbs <[EMAIL PROTECTED]> wrote: Yes. Use if you want exact matches. However, often I just break out the navigation special cases (Home is a typical one). Sean Joe Van Dyk wrote: > > > > > /> > > > > Say I'm on the page /about/page. Won't both the Home and the About > links have the 'selected' class specified? Since /about/page is a > child of both those pages? > > Joe > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant >>> ___ >>> Radiant mailing list >>> Post: Radiant@radiantcms.org >>> Search: http://radiantcms.org/mailing-list/search/ >>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant >>> >> ___ >> Radiant mailing list >> Post: Radiant@radiantcms.org >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant >> > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] slug inside url_matches [SOLVED]
Thank you all, ancestor_or_self works nicely. Jeff Sean Cribbs wrote: An alternative is or , which will do close to what you want. Sean Jeffrey Jones wrote: Hoi all, Does anyone know how I could get the following working? ignore_case="true"> style="display: none;" > Basically, if the page's slug is in the url somewhere I want the css style display to be none. I have tried with double and single quotes but this doesn't appear to be working. Using a hard-coded value instead works. I am assuming the isn't being translated to the actual slug value before being matched in the regexp. Thanks Jeff ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Radiant tag errors
Right now, when an editor messes up a radiant tag, a 500 page gets rendered. Would it be possible to display the page content, except for the radiant tag that had the error, and show the error message in place of that tag? Joe ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] navigation tag question
Wow -- that's craziness. Wonder if it would be possible or advisable to modify the navigation tag to be smarter as to what it highlights as being the active link? On Fri, Oct 17, 2008 at 8:44 AM, Manuel Meurer <[EMAIL PROTECTED]> wrote: > I found the r:navigation tag become too limited to do that kind of stuff. > See below for an example of how to do your navigation "by hand". > > > >active matches="^/$">inactive">Home > > > class="activeinactive"> > > > > > > class="activeinactive"> > > > > > > > > > > > On Thu, Oct 16, 2008 at 9:56 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote: >> In the below case, I would want the About link to be highlighted, >> since that's the closest match to the current page. Is there a good >> way to do that? >> >> Joe >> >> On Thu, Oct 16, 2008 at 12:39 PM, Sean Cribbs <[EMAIL PROTECTED]> wrote: >>> Yes. Use if you want exact matches. However, often I just break >>> out the navigation special cases (Home is a typical one). >>> >>> Sean >>> >>> Joe Van Dyk wrote: >>> /> Say I'm on the page /about/page. Won't both the Home and the About links have the 'selected' class specified? Since /about/page is a child of both those pages? Joe ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant >>> >>> ___ >>> Radiant mailing list >>> Post: Radiant@radiantcms.org >>> Search: http://radiantcms.org/mailing-list/search/ >>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant >>> >> ___ >> Radiant mailing list >> Post: Radiant@radiantcms.org >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant >> > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Fwd: [Radiant] Using Git with Radiant Extensions
On Fri, Oct 17, 2008 at 11:03 AM, Chris Parrish < [EMAIL PROTECTED]> wrote: > So, to make sure I understand... > > If I have an extension of mine in a submodule of a project, I can develop > within that extension: > > * make changes in that copy of the extension (testing its behavior > as part of the project) > * commit those changes to the submodule's repo > * manage branching (gitk, etc) from within that submodule > > If so, that helps me a lot. Everything I'd read made it sound like > submodules don't behave like a working git repo which is why I thought you > couldn't push changes back to the original -- that submodules only permitted > data transfer one-way (from source to your local copy). > The way I understand it, from a developing perspective, the extension is simply a git repo that happens to exist within another git repo. You can pull, develop, commit, and push with the extension just as you would any other project managed with git. The difference here is when you pull, develop, commit, and push from the master project (the Radiant install in your case), you'll need to consider what's happening with your extension. Do I understand it correctly? -- Tim ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Audio extension
On Thu, Oct 16, 2008 at 6:26 PM, Andrew Neil <[EMAIL PROTECTED]>wrote: > Hi folks, > > I'm thinking of writing a Radiant extension to add a flash audio player to > your site. My plan is to use the Audio Player Wordpress plugin: > >http://www.1pixelout.net/code/audio-player-wordpress-plugin/ > > in a similar fashion to the plugin for Textpattern: > >http://www.textpatternmania.com/2006/04/29/plugin-jnmaudio > > Before I get started, I just want to check if anyone else has already done > this? > I'm not sure an extension is needed here. I think this is straightforward enough to implement with a snippet. Here's what I did on one of my Radiant sites: http://gist.github.com/17467 Download MP3 To download, right-click and choose “Save Target As..” -- Tim ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Using Git with Radiant Extensions
Chris, You may want to have a look at the ray extension. It enables you to manage your extension also as git submodules. I just discovered this extension and enhanced my fork to accept a 'remote' variable either on the command line or within the bundles extensions.yml (to install a bunch of extension), so you can add git remotes automatically with the installation of the extension. There is also a new rake task ray:pull that pulls all remote sources to the submodule. This comes handy when you're developing an extension that you have forked. Michi On 17 Oct 2008, at 5:03 PM, Chris Parrish wrote: So, to make sure I understand... If I have an extension of mine in a submodule of a project, I can develop within that extension: * make changes in that copy of the extension (testing its behavior as part of the project) * commit those changes to the submodule's repo * manage branching (gitk, etc) from within that submodule If so, that helps me a lot. Everything I'd read made it sound like submodules don't behave like a working git repo which is why I thought you couldn't push changes back to the original -- that submodules only permitted data transfer one-way (from source to your local copy). -Chris Sean Cribbs wrote: Like svn:externals, you can maintain a submodule in a project, commit to it and push it while maintaining the parent project. However, whenever you've changed something in the submodule, it's necessary to go back up to the parent project, commit the submodule directory, and possibly do `git submodule init` and `git submodule update` (I don't know if that's strictly necessary, but I like to do it to be certain). That will make sure that the next time your parent project is checked out, it will get the latest submodule version. Sean Chris Parrish wrote: Trying to get up to speed with a Git workflow and I have some questions about working with extensions. If I have a radiant project A that uses someone else's extensions B, C, and D. I understand that I can create a repo for radiant project A set up all the extensions as submodules (if they're all in git repos). If, on the other hand, I'm developing extension B, I could set up a dummy project A (no repo), and set up B, C, and D as independent, parallel repos. No submodules. With B being the one I'm working on, managing, branching, etc. of course. But what if I'm developing extension B along with project A? If you edit code within a submodule B, there's no way to send those changes back to the original B repo (or use branching, or other git tools) on B is there? Git isn't really tracking your changes on B is it? Is there some way to handle this development situation or am I just going about this wrong? Is piston or braid an option here and if so, is anyone using it successfully? Thanks, -Chris Parrish ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] navigation tag question
I found the r:navigation tag become too limited to do that kind of stuff. See below for an example of how to do your navigation "by hand". activeinactive">Home On Thu, Oct 16, 2008 at 9:56 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote: > In the below case, I would want the About link to be highlighted, > since that's the closest match to the current page. Is there a good > way to do that? > > Joe > > On Thu, Oct 16, 2008 at 12:39 PM, Sean Cribbs <[EMAIL PROTECTED]> wrote: >> Yes. Use if you want exact matches. However, often I just break >> out the navigation special cases (Home is a typical one). >> >> Sean >> >> Joe Van Dyk wrote: >>> >>> >>> >>> >>> >> /> >>> >>> >>> >>> Say I'm on the page /about/page. Won't both the Home and the About >>> links have the 'selected' class specified? Since /about/page is a >>> child of both those pages? >>> >>> Joe >>> ___ >>> Radiant mailing list >>> Post: Radiant@radiantcms.org >>> Search: http://radiantcms.org/mailing-list/search/ >>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant >>> >>> >> >> ___ >> Radiant mailing list >> Post: Radiant@radiantcms.org >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant >> > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Using Git with Radiant Extensions
So, to make sure I understand... If I have an extension of mine in a submodule of a project, I can develop within that extension: * make changes in that copy of the extension (testing its behavior as part of the project) * commit those changes to the submodule's repo * manage branching (gitk, etc) from within that submodule If so, that helps me a lot. Everything I'd read made it sound like submodules don't behave like a working git repo which is why I thought you couldn't push changes back to the original -- that submodules only permitted data transfer one-way (from source to your local copy). -Chris Sean Cribbs wrote: Like svn:externals, you can maintain a submodule in a project, commit to it and push it while maintaining the parent project. However, whenever you've changed something in the submodule, it's necessary to go back up to the parent project, commit the submodule directory, and possibly do `git submodule init` and `git submodule update` (I don't know if that's strictly necessary, but I like to do it to be certain). That will make sure that the next time your parent project is checked out, it will get the latest submodule version. Sean Chris Parrish wrote: Trying to get up to speed with a Git workflow and I have some questions about working with extensions. If I have a radiant project A that uses someone else's extensions B, C, and D. I understand that I can create a repo for radiant project A set up all the extensions as submodules (if they're all in git repos). If, on the other hand, I'm developing extension B, I could set up a dummy project A (no repo), and set up B, C, and D as independent, parallel repos. No submodules. With B being the one I'm working on, managing, branching, etc. of course. But what if I'm developing extension B along with project A? If you edit code within a submodule B, there's no way to send those changes back to the original B repo (or use branching, or other git tools) on B is there? Git isn't really tracking your changes on B is it? Is there some way to handle this development situation or am I just going about this wrong? Is piston or braid an option here and if so, is anyone using it successfully? Thanks, -Chris Parrish ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Disabling extensions/filters
In config/environment.rb, find the line that says 'config.extensions' and change the right hand side of the expression to an array of which extensions you want to have enabled. Obviously you would exclude the :textile_filter and :markdown_filter extensions. Sean Farrel Lifson wrote: I'm busy putting together a site that will be edited by some nontechnical folk. I've included the WYMEditor extension in so far and I'd like to make it the default way to edit. I would also like to remove the options for the Textile/Markdown/etc filters. Is there an easy way to do this or do I have to go spelunking into the Radiant codebase? Farrel ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Audio extension
I have never done this, but it sounds like a cool project. Good luck ~Nate Yeah, that's right. I top-posted. On Thu, Oct 16, 2008 at 5:26 PM, Andrew Neil <[EMAIL PROTECTED]>wrote: > Hi folks, > > I'm thinking of writing a Radiant extension to add a flash audio player to > your site. My plan is to use the Audio Player Wordpress plugin: > >http://www.1pixelout.net/code/audio-player-wordpress-plugin/ > > in a similar fashion to the plugin for Textpattern: > >http://www.textpatternmania.com/2006/04/29/plugin-jnmaudio > > Before I get started, I just want to check if anyone else has already done > this? > > Cheers, > Drew > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Disabling extensions/filters
I'm busy putting together a site that will be edited by some nontechnical folk. I've included the WYMEditor extension in so far and I'd like to make it the default way to edit. I would also like to remove the options for the Textile/Markdown/etc filters. Is there an easy way to do this or do I have to go spelunking into the Radiant codebase? Farrel -- Aimred - Ruby Development and Consulting http://www.aimred.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Using Git with Radiant Extensions
Like svn:externals, you can maintain a submodule in a project, commit to it and push it while maintaining the parent project. However, whenever you've changed something in the submodule, it's necessary to go back up to the parent project, commit the submodule directory, and possibly do `git submodule init` and `git submodule update` (I don't know if that's strictly necessary, but I like to do it to be certain). That will make sure that the next time your parent project is checked out, it will get the latest submodule version. Sean Chris Parrish wrote: Trying to get up to speed with a Git workflow and I have some questions about working with extensions. If I have a radiant project A that uses someone else's extensions B, C, and D. I understand that I can create a repo for radiant project A set up all the extensions as submodules (if they're all in git repos). If, on the other hand, I'm developing extension B, I could set up a dummy project A (no repo), and set up B, C, and D as independent, parallel repos. No submodules. With B being the one I'm working on, managing, branching, etc. of course. But what if I'm developing extension B along with project A? If you edit code within a submodule B, there's no way to send those changes back to the original B repo (or use branching, or other git tools) on B is there? Git isn't really tracking your changes on B is it? Is there some way to handle this development situation or am I just going about this wrong? Is piston or braid an option here and if so, is anyone using it successfully? Thanks, -Chris Parrish ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
