A little comment about this, and another "we did that for Redken" story.
As Chris said, Radiant's design (visual and workflow) would need to be
rethought to accommodate this kind of change. Some kind of versioning
(undefined as of yet) is in the roadmap, so we'd appreciate any
contributions people can make to the mockups or prototype subprojects to
work out the flow.
We did this kind of thing for Redken, and I believe DP is still using
the extension I wrote. The extension was heavily based on Ticket #503
on Trac. However, as I got it to work, I realized the changes were
extremely systemic, similar to what Nick found when trying to scope
snippets and layouts in the multi_site extension. There comes a point
at which an extension is no longer appropriate. That said, I'd like to
see some alternatives to my hackish implementation that we might
consider for core down the road.
Also, I wrote a quickie extension for a client in December that allowed
him to maintain two different Radiant instances, one that's for staging,
another for production. We used a sqlite3 database because we could
easily copy the file into the production site and it would "just work".
Sean
Jamey Cribbs wrote:
I agree. I initially wanted to keep everything within one instance of
radiant by just modifying the way pages/page_parts were saved and making the
additional functionality available through the existing UI. Sean gave me
some pointers/lessons learned (including a mention of acts_as_draftable).
I still think it is do-able this way, but it would be tricky to incorporate
a full-featured draft functionality into the existing architecture and UI
without breaking anything in radiant. :)
I opted to go the "separate staging instance" route because it appeared more
straight forward and it met my clients needs, although the design is not as
elegant as being able to do everything in one environment.
On Mon, Jun 9, 2008 at 12:01 PM, Chris Parrish <
[EMAIL PROTECTED]> wrote:
This issue was brought up some time ago so it might be worth checking the
maillist history, but I'm not sure anything was ever implemented. One of
the interesting things brought up , if I remember correctly, was the mention
of Rick Olson's acts_as_draftable plugin. It might be worth looking into
(it can be found here:
http://svn.techno-weenie.net/projects/plugins/acts_as_draftable/).
Drafting functionality is something that Radiant could certainly benefit
from. Let us know if you plan to release something.
FWIW, I think the biggest challenge would be coming up with a clean,
Radiant-worthy UI that lets users perform these functions via an
easy-to-understand, concise design. Radiant's UI currently doesn't "think"
this way.
-Chris
Jamey Cribbs wrote:
I'm going to ask the client if they would give permission for me to
release
it. Right now, it only works for mysql, as I'm using mysqldump. Works
great for my specific needs, but I might try to genericize it using Sean's
export code and fixture loading before I release it.
On Mon, Jun 9, 2008 at 11:15 AM, Mohit Sindhwani <[EMAIL PROTECTED]> wrote:
Jamey Cribbs wrote:
Thanks, but as you said, the "dev" functionality does not do
everything we need. If you have an existing page that you want to
change, you have to set the status back to "draft" and then the page
does not show at all on the production site.
Anyway, after much investigation, I ended up going a totally different
route. I created a "staging" extension and setup an additional
radiant environment called "staging". The extension disables all
admin functions in the production environment and adds an admin tab in
the staging environment that allows you to click on a link, whereby it
copies relevant tables from the staging db to the production db. It
would have been great to not have to run a separate environment, but
so far it seems to be working well.
That's true. I just wanted to point out the obvious because it is easy
to
miss it some times (I didn't know about it for quite a while).
I remember Sean had a preview extension that would preview the page but
again it's not a staging environment. Your extension does sound
interesting. Do you have plans to release it?
Cheers,
Mohit.
6/9/2008 | 11:15 PM.
_______________________________________________
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
