[Oscailt] features question..
terence010203 at yahoo.co.uk
Wed Feb 17 12:21:05 PST 2010
Actually it should work the way you describe.
When you upgrade a feature it should be creating a hidden copy which is a copy of the original. Then the idea is that you are supposed to edit the hidden copy, whilst the original version remains visible and can continue to receive comments.
Then when you are finished editing the hidden copy, when you do an unhide, it should transfer all the comments from the original to the newly unhidden copy and deletes the old one.
In terms of the code the key functions to look at during the feature upgrade are: makeTemporaryFeature() in story.inc called from itemaction.inc
And when the 'hidden' copy is unhidden this function mergeTemporaryFeatureIntoOringal() in story.inc is called from itemaction.inc
It is possible, you may not have noticed the generation of the hidden copies. Or maybe I have mis-understood what is happening on your system.
--- On Tue, 16/2/10, arclightfire at hushmail.com <arclightfire at hushmail.com> wrote:
> From: arclightfire at hushmail.com <arclightfire at hushmail.com>
> Subject: [Oscailt] features question..
> To: "Oscailt IMC List" <oscailt at lists.indymedia.org>
> Cc: "BIMC" <imc-bristol at lists.indymedia.org>
> Date: Tuesday, 16 February, 2010, 15:16
> Hi - I have an question about creating features. The way it seems
> to be done is by using the 'upgrade to feature' button, which is
> fine, however when we do this we often want to edit the orginal
> article that a user has posted to improve it, add information etc.
> However this changes the original. is there any way to upgrade to
> a feature that clones the article you are upgrading, so keeping a
> copy as the user intended, and giving a new one that we can edit?
> At the moment we do this by creating a new article and cut-n-
> pasting the content over, which is a slow process and not great to
> show new people not used to using HTML...
More information about the Oscailt