search

sheadawson / silverstripe-blocks

Flexible blocks/widgets module for SilverStripe 3
BSD 3-Clause "New" or "Revised" License
60 stars 60 forks source link

Question: does versioning only save 2 stages? #82

Open anselmdk opened 8 years ago

anselmdk commented 8 years ago

I'm considering to use this module on a new project to completely replace the content area, as I feel it get's more and more obsolete the more sophisticated blocks are getting, and feels a little redundant. The content area however has one important feature, which is the History tab, where you can see all previous versions and compare.

It seems to me that this module only supports 2 versions? I'm attaching a screenshot.

screenshot 2016-04-15 07 43 11

I'd love to have similar functionality to the History tab, but I could imagine this to be complicated. What are your thoughts on this topic?

sheadawson commented 8 years ago

This issue is a result of the history tab currently being coupled with the site tree part of the cms. I think I read somewhere that there are plans to make history tab work with versioned dataobjects in ss core. A quick google found this module, which seems like it could be a good start in the interim. https://github.com/bluehousegroup/silverstripe-data-object-version-viewer

Also this module might be a more suitable basis than blocks module - https://github.com/dnadesign/silverstripe-elemental/

anselmdk commented 8 years ago

Thanks for the clarification and those 2 references. You're right that elemental might fit better to my use case. However it doesn't support multiple block areas, so if I'd want to support that, I'd better stick with this one.

micschk commented 8 years ago

I often swap out $Content with blocks interface as well in the CMS (using this blocks module). You could even save blocks' content into the page Content area (along with in-text anchors per block) to make your pages searchable & deep-linkable.

The current versioning interface (buttons, really) gets added by the BetterButtons module if I'm not mistaken. The Versioned extension on itself adds full extra tables for historical versions to the DB, identical to pages. So the version-viewer module should work perfectly for that (nice find, Shea!) ​

On Mon, Apr 18, 2016 at 11:32 AM, Anselm Christophersen < notifications@github.com> wrote:

Thanks for the clarification and those 2 references. You're right that elemental might fit better to my use case. However it doesn't support multiple block areas, so if I'd want to support that, I'd better stick with this one.

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/sheadawson/silverstripe-blocks/issues/82#issuecomment-211294785

jeffwhitfield commented 8 years ago

Another problem, which one of my clients just ran into, is that there is no way to differentiate between Saved and Published. Basically, if the client makes a change to a block and clicks "Save" then both buttons are green and the client doesn't know that the "Saved" version isn't actually published. It's not till they click "Published" that the version that they are seeing in the CMS goes live. So...I would imagine the add-on needs to be updated so that the "Published" button is updated so that it reflects the actual published state of the current "version" that is being seen, right?

micschk commented 8 years ago

Hi Jeff,

You could take a lack at my block enhancements module for that kind of functionality.

Op 4 aug. 2016 4:44 a.m. schreef "Jeff Whitfield" <notifications@github.com

:

Another problem, which one of my clients just ran into, is that there is no way to differentiate between Saved and Published. Basically, if the client makes a change to a block and clicks "Save" then both buttons are green and the client doesn't know that the "Saved" version isn't actually published. It's not till they click "Published" that the version that they are seeing in the CMS goes live. So...I would imagine the add-on needs to be updated so that the "Published" button is updated so that it reflects the actual published state of the current "version" that is being seen, right?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/sheadawson/silverstripe-blocks/issues/82#issuecomment-237437452, or mute the thread https://github.com/notifications/unsubscribe-auth/AA9ZokL_Lp0l5gmcR_wYrpJvnA4ZtlXsks5qcVITgaJpZM4IIB8t .

jeffwhitfield commented 8 years ago

Thanks Michael! I'll definitely look into that! :)