Persist GridField state between requests

[g4b0]

Hi all,
I would like to point your attention on this framework issue: https://github.com/silverstripe/silverstripe-framework/issues/3229
In other thread we are brainstorming about various aspect of CMS enhancement, but I think that the first question to to solve is the persistance of the Gridfield. How can I tell to my customer that the have to sort and filter the gridfield each time the edit a record?

What's your point of view?

g4b0

[Marcus Dalgren]

Ï of course think it's a pretty big usability issue since I reported it.
This can become pretty crippling on sites where alot of admin work needs to be done which is where I got the issue reported to me.
I also understand that the question about when/how/where/how long the state should be persisted is not a trivial issue.
List based repetetive tasks with big lists suck pretty much right now so just a basic version of this feature could be a big improvement.

[off...@netwerkstatt.at]

Is there a better way for repetitive tasks? E.g. update / edit multiple items at once?

 

--
You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to silverstripe-d...@googlegroups.com.
To post to this group, send email to silverst...@googlegroups.com.
Visit this group at http://groups.google.com/group/silverstripe-dev.
For more options, visit https://groups.google.com/d/optout.