Sean Cribbs wrote:
> For reference, just as before the switch, not every pull request is
> accepted to the Radiant core. However, the overarching difference
> seems to me that anyone can take their own fork and run with it,
> without needing 'permission'.
>
> Sean
Exactly.
--
Posted via http://
For reference, just as before the switch, not every pull request is
accepted to the Radiant core. However, the overarching difference
seems to me that anyone can take their own fork and run with it,
without needing 'permission'.
Sean
On Wed, Aug 6, 2008 at 11:53 AM, Marty Haught <[EMAIL PROTECTE
> I'm not saying to not manage your extension's development. But in Git
> the culture of open source collaboration is mildly different. But then
> again, I see your point. I can't wait to see what page_event becomes
> though. Could easily be a core extension once it reaches maturity!
I'm not offen
[EMAIL PROTECTED] wrote:
> On Wed, 2008-08-06 at 18:03 +0200, Arik Jones wrote:
>> There really is no reason to be a prude about it though. It's open
>> source and we should expect no less. I say instead of complaining,
>> re-factor the code and release it. That'd seem easier than trying to
>> m
On Wed, 2008-08-06 at 18:03 +0200, Arik Jones wrote:
> There really is no reason to be a prude about it though. It's open
> source and we should expect no less. I say instead of complaining,
> re-factor the code and release it. That'd seem easier than trying to
> micro-manage each pull request.
Marty Haught wrote:
>> I extended Marty's extension to handle multi-day events:
>>
>> http://github.com/MrGossett/radiant-page-event/tree/master
>>
>> Marty didn't like the fact that I didn't ask him before do that work, so he
>> denied my pull request. Oh well.
>
> Tim's mods will give you multi-
> I extended Marty's extension to handle multi-day events:
>
> http://github.com/MrGossett/radiant-page-event/tree/master
>
> Marty didn't like the fact that I didn't ask him before do that work, so he
> denied my pull request. Oh well.
Tim's mods will give you multi-day support however Tim's desi
On Tue, 2008-08-05 at 22:27 -0600, Marty Haught wrote:
> > It looks great but, I do need to list multi-day events. Everything else
> > looks like it will work. I'll look into this one again if the others
> > don't do multi-day events. Thanks.
>
> Multi-day and reoccurring events are both in the fu
On Wed, Aug 6, 2008 at 12:27 AM, Marty Haught <[EMAIL PROTECTED]> wrote:
> > It looks great but, I do need to list multi-day events. Everything else
> > looks like it will work. I'll look into this one again if the others
> > don't do multi-day events. Thanks.
>
> Multi-day and reoccurring events
I just went with Translator and really liked it. I had built several
pages with Language Redirect, which was one of the first Radiant
behaviours.
I think that the page part solution is the best, both for building the
site and maintaining it. It also makes switching the language, but
keepi
Hi Oli,
Three extensions, three different approaches to translation:
Language Redirect: Separate site trees for each language.
Translator: Separate page parts for each language, but a single site
tree.
Language Switch: All translations in the same page and part, separated
by tags that indica
I'm feeling very stuck this "rake aborted! / no such file to load --
openssl" problem I've been having (last post 30 hours ago). I've done
everything (I think) that Mohit and Bjorn suggested, to no avail.
Without further help I'm not going to get off the ground, I'm afraid.
[for full details, see
Casper,
I'll definitely do that and post back when I do. Probably by next week.
Rails Edge I18n bits won't solve the problem, but it'll be a step in
the right direction.
On Aug 6, 2008, at 3:51 AM, Casper Fabricius wrote:
Hi Jim,
Definitely a great initiative to get Radiant on 2.1. If you
Jim Gay wrote:
> I thought we fixed that in 0.6.9
> That was a bug in 0.6.8 and we quickly put out the current release.
> http://radiantcms.org/blog/archives/2008/07/28/minor-bug-and-workaround-for-0-6-8-upgrades/
>
>
> Is it possible that you actually have the 0.6.8 gem installed?
I don't think so
I thought we fixed that in 0.6.9
That was a bug in 0.6.8 and we quickly put out the current release.
http://radiantcms.org/blog/archives/2008/07/28/minor-bug-and-workaround-for-0-6-8-upgrades/
Is it possible that you actually have the 0.6.8 gem installed?
On Aug 6, 2008, at 7:08 AM, danny q. wro
Wait, just figured it out.
Had to add:
Page.load_subclasses
to the very last line of config/environment.rb. Now everything works
fine. Dug through the list a bit and found this as an error in the gem
version (but apparently fixed in git). As for ruby 1.8.7, so far so good.
Thanks, hopefully
On Aug 6, 2008, at 6:35 AM, danny q. wrote:
Hi list,
So I've been trying to upgrade from 0.6.7-svn to the 0.6.9 gem using a
Site5 account, and something's blocking me. I am running gems 1.1.0,
ruby 1.8.7
That might be the problem. Radiant is not yet compatible with ruby 1.8.7
http://radiant
Hi list,
So I've been trying to upgrade from 0.6.7-svn to the 0.6.9 gem using a
Site5 account, and something's blocking me. I am running gems 1.1.0,
ruby 1.8.7 and have the radiant 0.6.9 gem installed locally with the
binary in my $PATH. Everything runs out of my home directory, including
the ru
Hi
Thanks for your answers.
It would be definitely great if we can assign user to a group.
For now I'm using multi_site and page_group extension together to
restrict the access.
Marc
--
Posted via http://www.ruby-forum.com/.
___
Radiant mailing list
P
There is a branch that starts down this road. You can tie specific
users to each site, though Admins and Devs see all sites, normal usere
do not.
Layouts can also be limited. It is not perfect, but a huge step in the
right direction.
http://github.com/zapnap/radiant-multi-site-extension/t
Hi Marc,
The multi_site extension has those limitations you mention. I
especially think #2 is a show stopper in many cases - all users sees
all sites. It would take some work to tie logins to a specific site,
but it would greatly enhance the value of the extension.
Cheers,
Casper
On 04/
Hi Jim,
Definitely a great initiative to get Radiant on 2.1. If you could add
some kind of status and list of bugs and stuff to do perhaps on the
Github wiki, I'd like to contribute.
However, I don't think the i18n stuff in edge will be of much help
when it comes to translating Radiant pa
22 matches
Mail list logo
