Blocks not showing fresh data, poor UX
Permalink
Hi
It can't just be me, I have been using 5.7 for a few months now since I was assured all the editing bugs were fixed however I still see nothing but problems using the content editing tools.
The main one for me is when using the HTML block, I can edit my HTML, save it and publish the changes. If I then edit the page again and go to edit the box, it shows the version of content from BEFORE I saved it the last time, meaning I have to re-do all the changes I just did, the only way to stop this is publishing, navigating away from the page and clearing the cache. But I cant keep doing that every time I need to edit a block more than once. Most blocks are ok, but a couple of them do this.
Also, if I click on the tab of an Area to add a new block and then close the popup instead of selecting a block type, I then can't click on the tab again to add a block without refreshing the page.
The usability for Concrete5 is a lot worse than it was in 5.6 for editing content, I can see the codebase has been improved to more modern standards which is good, but the UI is now also 'modern' but to an extent where is has become less usable - something developers suffer from is showing off new things and forgetting about UX - am I the only one thinking this and experiencing these problems?
I find 5.6 much quicker and easy to work with, and so do my client when they are editing content. I won't be suggesting to any clients to upgrade to 5.7 from 5.6 due to these issues as it will cost them for me to do it and all they get out of it is a harder time.
It can't just be me, I have been using 5.7 for a few months now since I was assured all the editing bugs were fixed however I still see nothing but problems using the content editing tools.
The main one for me is when using the HTML block, I can edit my HTML, save it and publish the changes. If I then edit the page again and go to edit the box, it shows the version of content from BEFORE I saved it the last time, meaning I have to re-do all the changes I just did, the only way to stop this is publishing, navigating away from the page and clearing the cache. But I cant keep doing that every time I need to edit a block more than once. Most blocks are ok, but a couple of them do this.
Also, if I click on the tab of an Area to add a new block and then close the popup instead of selecting a block type, I then can't click on the tab again to add a block without refreshing the page.
The usability for Concrete5 is a lot worse than it was in 5.6 for editing content, I can see the codebase has been improved to more modern standards which is good, but the UI is now also 'modern' but to an extent where is has become less usable - something developers suffer from is showing off new things and forgetting about UX - am I the only one thinking this and experiencing these problems?
I find 5.6 much quicker and easy to work with, and so do my client when they are editing content. I won't be suggesting to any clients to upgrade to 5.7 from 5.6 due to these issues as it will cost them for me to do it and all they get out of it is a harder time.
No, you're not the only one. There has been lots of discussion on these issues. I (for instance) have also experienced these problems with 5.7 UI but usually in a manner that is hard to replicate for a developer. I've just ended up reloading the page (as you have done as well) and then forget about it until the issue re-occurs (when I also usually don't have clear idea how to replicate it).
When you see/find a new bug, go to the bug tracker and report it there or if you're using the GitHub version, report it directly to the GitHub repository issues.
Describe clearly how to replicate the problem on a new instance. It seems you know the exact steps on how to replicate some of these problems.
Then after time, they will be hopefully fixed.
Recently there has been a lot of progress regarding the core code cleanup and refactoring which is very good from the developer's perspective.
I would think that fixing these problems would get prioritized with the core team. At least I would prioritize the end user experience over anything else if I were them because that's ultimately the first thing that new users see with the system. If it just does not work, they will go with some other platform
The UI has also progressed from where it was 1,5 years ago when the first 5.7 version became available. It now works much better already than in the beginning, although there are still quite a few problems left.