Daniel Sheppard wrote:
> Restrict the pages tab to users with the dev role:
>
> admin.tabs['Pages'].visibility = [:dev]
Well, not quite. That only hides the tab from the user's view. To be
secure you will need to use the only_allow_access_to class method inside
the body of the controller defini
It has actually been online since January, but had some teething
problems, but I thought it was time to announce a little site I did
for a friend. It is something a bit different from a blog, but lately
has merely been hosting his Video Blogs.
Right now, we are running Mental with a homebre
I'd love to... link?
Sean
Keith Bingman wrote:
It has actually been online since January, but had some teething
problems, but I thought it was time to announce a little site I did
for a friend. It is something a bit different from a blog, but lately
has merely been hosting his Video Blogs.
On Mar 18, 2007, at 11:29 PM, BJ Clark wrote:
> Just saw this,
> Yeah, I used the r:navigation, I can post the actual code I used if
> you need to see it.
> As for the blog, it's Mephisto, not radiant, because I really really
> like mephisto, and it's broken cause I'm a lazy ass and way to busy
>
No, Just cloned the layout across both platforms. I couldn't figure
anything cool out because Mephisto uses liquid.
BJ
On 3/19/07, Jamie M. Wilkinson <[EMAIL PROTECTED]> wrote:
> On Mar 18, 2007, at 11:29 PM, BJ Clark wrote:
>
> > Just saw this,
> > Yeah, I used the r:navigation, I can post the a
Hi,
I have some pages that generate XML and I'm looking to improve performance.
(Actually, I'm looking for any tips that will improve performance)
Here's one that is concerning-
http://pastie.caboo.se/47962
I don't think a page like this will be cached because of the
tags? right?
I'm using
Hi Todd,
That page should still get cached if you are using the standard radiant
system, are you finding that this isn't the case?
Best Regards,
Kevin
On 3/19/07, Todd McGrath <[EMAIL PROTECTED]> wrote:
Hi,
I have some pages that generate XML and I'm looking to improve
performance.
(Actuall
Asleep at the wheel, it's been a long day:
http://bitchkittyracing.com
Keith Bingman
Tel: +49-7731-79838380
[EMAIL PROTECTED]
Begin forwarded message:
From: Keith Bingman <[EMAIL PROTECTED]>
Date: March 19, 2007 2:32:01 PM GMT+01:00
To: radiant@lists.radiantcms.org
Subject: [Radiant] [Ann]
And they are upgrading (I hope) my server, so I picked a really
stupid day to tell you all about it. It should be up within the hour...
Keith Bingman
Tel: +49-7731-79838380
[EMAIL PROTECTED]
On Mar 19, 2007, at 5:14 PM, Keith Bingman wrote:
Asleep at the wheel, it's been a long day:
http
Hi Keith,
I haven't seen the site yet due to the problems you mentioned however I'd be
interested in what level of tag integration you managed to achieve. It's
high on my to-do list to getting a tagging extension put together but I've
noticed that others have had issues with naming conflicts and
Hi Kevin,
Thank you. My assumption was wrong - on further review, I do see the xml files
in the cache directory.
Well, I guess that one is crossed off the list then.
Todd
Quoting Kevin Ansfield <[EMAIL PROTECTED]>:
> Hi Todd,
>
> That page should still get cached if you are using the stand
I tried to do a tagging extension late last year with the
acts_as_taggable plugin. I think I am one of those people you may
have heard about with naming conflicts. Basically, you cannot use the
model name Tag, as it disables the Radius tagging system and you site
will not render. I got arou
Just had my first instance of conflicting updates - I edited a page while
somebody else was editing it too without realising it -
luckily in this instance we were both trying to do the same thing, but this
could lead to data loss without warning.
Time for some big red flashing warning lights.
I
Good idea Daniel, although this method may still run into
synchronisation issues - I think the best way would be to use
optimistic locking and defer it until you save in the database - that
way it's atomic. Then you'd throw the error to the user after you
tried to save and failed.
http://a
For the time being, using what you mentioned (via Rails' built-in
locking - lock_version is the column name IIRC) would probably be best.
Sean
Daniel Sheppard wrote:
> Just had my first instance of conflicting updates - I edited a page while
> somebody else was editing it too without realising
Daniel Sheppard wrote:
> "This page has been modified since you last loaded it. The last user to
> edit this page was . If you continue
> saving this page their changes may be lost".
>
> There will then by a checkbox with that option saying something like
> 'ignore 's changes and save my changes
Sean Cribbs wrote:
> For the time being, using what you mentioned (via Rails' built-in
> locking - lock_version is the column name IIRC) would probably be best.
Yes, please. Adding optimistic locking would be great.
--
John Long
http://wiseheartdesign.com
> 1.) User is notified of conflict. Must call/IM/email other user to
> discuss their changes to make a decision. User makes the
> choice to keep his or other user's work only.
>
> 3.) User is notified of conflict. The other user wins. The only
> option is to copy their work to somewhere a
On 20/03/2007, at 3:51 PM, Daniel Sheppard wrote:
>
>> All this assumes that we aren't going down the road of: User
>> can't even open the page because user B has that page locked
>> (opened).
>
> That's really not possible over http (well, possible, but not
> reliably so).
Well, it is possibl
> >> All this assumes that we aren't going down the road of: User
> >> can't even open the page because user B has that page locked
> >> (opened).
> >
> > That's really not possible over http (well, possible, but not
> > reliably so).
>
> Well, it is possible using pessimistic locking (HTTP's
20 matches
Mail list logo
