SilverStripe 3 is looking great on the surface, but I just wanted to flag up a few bugs/issues with the CMS that are stopping me from using v3 on any live sites. These issues have the potential to confuse & annoy my clients, and as one of main reasons I chose to use the SilverStripe CMS was due to its user-friendliness, it would be great if we could get these squashed ASAP. Some I've added to the bug tracker myself, whereas others had already been logged by other users. If you could just scan through the list and chip in on the tickets of any you have further comments on.
I've put them in the order that I feel will benefit my clients most, with the one at the top causing most frustration.
*2- BUG: GridField columns do not wrap, causing horizontal scrolling. http://open.silverstripe.org/ticket/7581* This also causes the Add New button to be hidden off screen.
*3- ENHANCEMENT: When uploading an image via the Insert Image popup there is no progress indicator, or even any indication that something is happening. http://open.silverstripe.org/ticket/7709 *
When uploading a file, clients are getting confused as to whether the upload is actually happening or not.
*5- FEATURE: When clicking Save in the GridField DetailForm, it should go back to the GridField. http://open.silverstripe.org/ticket/7710* This will easily simplify the addition of new items to GridField, it just doesn't make sense to have to click Back after Create *every** *time.
*7- ENHANCEMENT: GridField DetailForm should automatically save upon the upload of an attached image, to avoid the need to Save first. http://open.silverstripe.org/ticket/7767* Avoids the need for the "Files can be attached once you have saved the record for the first time" message, and should help with number 5 above.
*9- BUG: Clicking the Pages sidebar icon when in Preview mode doesn't work, and removes Edit button, breaking CMS. http://open.silverstripe.org/ticket/7630* The expected result is to go to /admin/pages/
*10- ENHANCEMENT: Insert Image Popup - Button should say Insert, not Update.
*
*11- BUG: Security > CMS Access > Access to all… Checkboxes don't become enabled upon unchecking all. Also on Full Admin Rights http://open.silverstripe.org/ticket/7070*
I'd love to help fix these myself if I could, but my PHP skills just aren't good enough. I'd even be happy to pay someone to implement numbers 1 and 5 for me.
#5 is very high on my list. I would love if we had an API to those buttons and could create "Save and Add" or "Save and done" buttons.
Going back to the GridField every time is unfortunately in direct conflict with #7.
The way I handled it with DOM was pretty cheesy, but effective -- sniff the FieldSet for file upload fields, and if found, offer a "save and add file" button, otherwise, if add, show a new form to add another, and if edit, refresh with a success message.
Speaking of which, where are the success messages on GridField? Very confusing!
On Thursday, August 9, 2012 6:56:51 AM UTC-4, James Cocker wrote:
> Hi Guys,
> SilverStripe 3 is looking great on the surface, but I just wanted to flag > up a few bugs/issues with the CMS that are stopping me from using v3 on any > live sites. These issues have the potential to confuse & annoy my clients, > and as one of main reasons I chose to use the SilverStripe CMS was due to > its user-friendliness, it would be great if we could get these squashed > ASAP. Some I've added to the bug tracker myself, whereas others had already > been logged by other users. If you could just scan through the list and > chip in on the tickets of any you have further comments on.
> I've put them in the order that I feel will benefit my clients most, with > the one at the top causing most frustration.
> *2- BUG: GridField columns do not wrap, causing horizontal scrolling. > http://open.silverstripe.org/ticket/7581* > This also causes the Add New button to be hidden off screen.
> *3- ENHANCEMENT: When uploading an image via the Insert Image popup there > is no progress indicator, or even any indication that something is > happening. http://open.silverstripe.org/ticket/7709 *
> When uploading a file, clients are getting confused as to whether the > upload is actually happening or not.
> *5- FEATURE: When clicking Save in the GridField DetailForm, it should go > back to the GridField. http://open.silverstripe.org/ticket/7710* > This will easily simplify the addition of new items to GridField, it just > doesn't make sense to have to click Back after Create *every** *time.
> *7- ENHANCEMENT: GridField DetailForm should automatically save upon the > upload of an attached image, to avoid the need to Save first. > http://open.silverstripe.org/ticket/7767* > Avoids the need for the "Files can be attached once you have saved the > record for the first time" message, and should help with number 5 above.
> *9- BUG: Clicking the Pages sidebar icon when in Preview mode doesn't > work, and removes Edit button, breaking CMS. > http://open.silverstripe.org/ticket/7630* > The expected result is to go to /admin/pages/
> *10- ENHANCEMENT: Insert Image Popup - Button should say Insert, not > Update.*
> *11- BUG: Security > CMS Access > Access to all… Checkboxes don't become > enabled upon unchecking all. Also on Full Admin Rights > http://open.silverstripe.org/ticket/7070*
> I'd love to help fix these myself if I could, but my PHP skills just > aren't good enough. I'd even be happy to pay someone to implement numbers 1 > and 5 for me.
James, thanks very much for raising your thoughts on this. I feel the
feedback we get like this is less frequent than it should be.
There's a lot of work to be done, and the core team is doing a lot - see
how long the list was at
doc.silverstripe.org/framework/en/3.0/changelogs/3.0.1/ as that's pretty
much just the month of July.
My hope is that we can get some high quality pull requests around some of
these items. If the core team works solely on these items, there'll be an
email from someone else wanting other work done instead. Hopefully we can
work together on them :)
> James, thanks very much for raising your thoughts on this. I feel the
> feedback we get like this is less frequent than it should be.
> There's a lot of work to be done, and the core team is doing a lot - see
> how long the list was at
> doc.silverstripe.org/framework/en/3.0/changelogs/3.0.1/ as that's pretty
> much just the month of July.
> My hope is that we can get some high quality pull requests around some of
> these items. If the core team works solely on these items, there'll be an
> email from someone else wanting other work done instead. Hopefully we can
> work together on them :)
> Cheers,
> Sigurd.
> --
> You received this message because you are subscribed to the Google Groups
> "SilverStripe Core Development" group.
> To post to this group, send email to silverstripe-dev@googlegroups.com.
> To unsubscribe from this group, send email to
> silverstripe-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/silverstripe-dev?hl=en.
We have already found a solution for James issue #7. The enhancement is part of SilverCart 1.3 which works with SilverStripe 2.4. I described it in a blog post <http://www.silvercart.org/blog/saving-mouse-klicks/>. I could bring this enhancement to SS3 and implement it on the framework.
> We have already found a solution for James issue #7. The enhancement is
> part of SilverCart 1.3 which works with SilverStripe 2.4. I described it in
> a blog post <http://www.silvercart.org/blog/saving-mouse-klicks/>.
> I could bring this enhancement to SS3 and implement it on the framework.
> To post to this group, send email to silverstripe-dev@googlegroups.com.
> To unsubscribe from this group, send email to
> silverstripe-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/silverstripe-dev?hl=en.
Personally, I don't think this a good solution. What happens if the object was deliberately left empty? What happens if a decorator adds an update field which has the required ID as a value?
I think a better way to solve this is to have UplaodField have a hidden field that stores the id/ids of the images uploaded, then set them on save. This also gets around the problem of someone uploading more images then clicking the cancel button, thinking the images wouldn't have changed.
On 15/08/2012, at 8:35 PM, James Cocker <j...@purplespider.co.uk> wrote:
> On 15 August 2012 05:00, baba-papa <rol...@musik-lehmann.de> wrote:
>> We have already found a solution for James issue #7. The enhancement is
>> part of SilverCart 1.3 which works with SilverStripe 2.4. I described it in
>> a blog post <http://www.silvercart.org/blog/saving-mouse-klicks/>.
>> I could bring this enhancement to SS3 and implement it on the framework.
>> To post to this group, send email to silverstripe-dev@googlegroups.com.
>> To unsubscribe from this group, send email to
>> silverstripe-dev+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/silverstripe-dev?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
> To post to this group, send email to silverstripe-dev@googlegroups.com.
> To unsubscribe from this group, send email to silverstripe-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/silverstripe-dev?hl=en.
> Personally, I don't think this a good solution. What happens if the object
> was deliberately left empty? What happens if a decorator adds an update
> field which has the required ID as a value?
> I think a better way to solve this is to have UplaodField have a hidden
> field that stores the id/ids of the images uploaded, then set them on save.
> This also gets around the problem of someone uploading more images then
> clicking the cancel button, thinking the images wouldn't have changed.
> On 15/08/2012, at 8:35 PM, James Cocker <j...@purplespider.co.uk> wrote:
> > Ah, looks good! It'd be really great if this could be brought to SS3!
> > Thanks!
> > On 15 August 2012 05:00, baba-papa <rol...@musik-lehmann.de> wrote:
> >> We have already found a solution for James issue #7. The enhancement is
> >> part of SilverCart 1.3 which works with SilverStripe 2.4. I described
> it in
> >> a blog post <http://www.silvercart.org/blog/saving-mouse-klicks/>.
> >> I could bring this enhancement to SS3 and implement it on the framework.
> >> To post to this group, send email to silverstripe-dev@googlegroups.com.
> >> To unsubscribe from this group, send email to
> >> silverstripe-dev+unsubscribe@googlegroups.com.
> >> For more options, visit this group at
> >> http://groups.google.com/group/silverstripe-dev?hl=en.
> > --
> > You received this message because you are subscribed to the Google
> Groups "SilverStripe Core Development" group.
> > To post to this group, send email to silverstripe-dev@googlegroups.com.
> > To unsubscribe from this group, send email to
> silverstripe-dev+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> http://groups.google.com/group/silverstripe-dev?hl=en.
> --
> You received this message because you are subscribed to the Google Groups
> "SilverStripe Core Development" group.
> To post to this group, send email to silverstripe-dev@googlegroups.com.
> To unsubscribe from this group, send email to
> silverstripe-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/silverstripe-dev?hl=en.
@Simon: In what case should someone leave a DataObject empty and expect it to be there? What ID are you talking about a Decorator should update? The object ID's are set by the framework and an unsaved DataObject has no ID.
This is a major can of worms, and it really depends on the user, I think. I dealt with this issue with my Uploadify module and found that some users consider the act of uploading a manipulative action, and others consider it a temporary placeholder until the save button is pressed.
In the end, Uploadify used the hidden input approach, and waited for the save. I thought it skirted nicely around all of the issues with new records. Plus, you don't have to make a request to the server to delete or unattach a file. You just manipulate the DOM, and everything happens on save.
That said, you still get those cranky phone calls from clients who say they attached an image and "it didn't stick."
Maybe there's a compromise somewhere, where the upload field dirties the form to the point that you at least get some feedback that you need to save.
On Wednesday, August 15, 2012 12:17:28 PM UTC-4, baba-papa wrote:
> @Simon: In what case should someone leave a DataObject empty and expect it > to be there? What ID are you talking about a Decorator should update? The > object ID's are set by the framework and an unsaved DataObject has no ID.
