For my two cents: I would be pleased to see a snazzy little red star or
some-such beside a page or snippet (on the list pages/list snippets)
which is currently being edited by someone else. Maybe with the name of
the other user in a mouseover? That way I could decide to do something
else, or che
Don't know if this is a good idea, just throwing it out there...
Some CMSs use the concept of "checked out" and "checked in" content. As
soon as a user starts editing a page it becomes "checked out" and nobody
else can edit it. You can even save your changes without checking-in
the file. The
Jacob Burkhart wrote:
> Don't know if this is a good idea, just throwing it out there...
>
> Some CMSs use the concept of "checked out" and "checked in" content. As
> soon as a user starts editing a page it becomes "checked out" and nobody
> else can edit it. You can even save your changes wit
On 3/20/07, Jacob Burkhart <[EMAIL PROTECTED]> wrote:
Or, Maybe it's time to consider addding versioning and history tracking.
If we detect a simulatneous edit, we simply save both versions.. one of
those versions is the later version and one of them is the earlier
version. The User saving the
On Mar 20, 2007, at 8:13 AM, Jacob Burkhart wrote:
> Jacob Burkhart wrote:
>> Don't know if this is a good idea, just throwing it out there...
>>
>> Some CMSs use the concept of "checked out" and "checked in"
>> content. As
>> soon as a user starts editing a page it becomes "checked out" and
Yes, there will be issues with Extensions... that's why Version Control
would have to be a part of the core of Radiant, and there would need to
be hooks available for Extension authors so that they can decide how
their page additions should be versioned.
I agree, this is all very non-trivial...
I'm testing things out for our eventual rollout of 0.6 and I'm
receiving this error when running rake db:migrate (or rake db:migrate
production)
"undefinded local variable of method 'class_name' for #'
0.5.2 was installed and working OK on mysql (pulled the source, not
from the gem)
But the
Jim,
Can you list the error that happens on migration? It's usually
necessary to migrate if coming from a previous version.
Sean
Jim Gay wrote:
> I'm testing things out for our eventual rollout of 0.6 and I'm
> receiving this error when running rake db:migrate (or rake db:migrate
> product
I've pasted the full rake trace below
On Mar 20, 2007, at 5:28 PM, Sean Cribbs wrote:
> Jim,
>
> Can you list the error that happens on migration? It's usually
> necessary to migrate if coming from a previous version.
>
> Sean
>
> Jim Gay wrote:
>> I'm testing things out for our eventual rollou
I want to validate that I am deploying my 0.2 version of my extension
correctly. I need to rule out that it is a radiant issue.
I have a radiant 6.0 rc1 (application mode) installed and running on
my hosting site (RailsPlayground). I just recently updated my
extension and wanted to deploy that t
Jason,
My first suggestion is to switch your app into development mode and
see what the error your getting is. My hunch is a file permission
issue, but it's hard to say without a real error message.
Good Luck,
BJ Clark
On 3/20/07, jsmorris <[EMAIL PROTECTED]> wrote:
> I want to validate that I am
BJ...Thank you
Your reminder to up the log level to debug forced me to remember
something odd about my installation.
I develop my radiant extension on a mac os x 4.9 ruby 1.8.5 RoR 1.2.1
running on a mongrel 1.0.1 , but I have to add two things when I
deploy. First, I have to add Admin:: to each
12 matches
Mail list logo
