Response Time
24 — 48 hours
I have a suggestion that is a best practice solution, when it comes to how StackIdeas handles the Administration Process within your software. You already DO this on many of your software brands' variables, but it is NOT consistent. My suggestion: Allow the Admin to remain on the same URL he/she was on, when attempting changes of content, save-without-closing, toggling variables, or in the normal course of receiving ERROR or other ADMIN-related messages. In EasySocial, I will make the suggestion in Voices, so consider this a suggestion for EasyBlog, since it doesn't use Voices for suggestions.
Here is a for instance (below). I have two screencaptures, to illustrate what happens, when I click on an activity that is not yet enabled on the back-end of EasyBlog yet. This example function happens to be the LinkedIn Integration. Again, to clarify, the problem is NOT with my LinkedIn integration (I can fix that). The issue I am reporting here is my suggestion on how to BETTER HANDLE EasyBlog's real-time Error report, back to the Administrator or User. My suggestion: KEEP THE ERROR MESSAGE ON THE SAME PAGE/URL THE ADMIN IS ALREADY ON, RATHER THAN FWD-ing HIM TO ANOTHER PAGE (either with a pop-up error message, or ajax, or at MINIMUM, don't change URLs).
Example:
Screencap 1 of 2 shows the initial url Admin is on, and what he is doing:
http://awesomescreenshot.com/0551zhsa91
Screencap 2 of 2 shows the url the Admin gets forwarded to, to get the realtime error message:
http://awesomescreenshot.com/0111zhw889
(Note: I blocked out some sensitive info in these screencaps, hope that's not too distracting)
Here is a for instance (below). I have two screencaptures, to illustrate what happens, when I click on an activity that is not yet enabled on the back-end of EasyBlog yet. This example function happens to be the LinkedIn Integration. Again, to clarify, the problem is NOT with my LinkedIn integration (I can fix that). The issue I am reporting here is my suggestion on how to BETTER HANDLE EasyBlog's real-time Error report, back to the Administrator or User. My suggestion: KEEP THE ERROR MESSAGE ON THE SAME PAGE/URL THE ADMIN IS ALREADY ON, RATHER THAN FWD-ing HIM TO ANOTHER PAGE (either with a pop-up error message, or ajax, or at MINIMUM, don't change URLs).
Example:
Screencap 1 of 2 shows the initial url Admin is on, and what he is doing:
http://awesomescreenshot.com/0551zhsa91
Screencap 2 of 2 shows the url the Admin gets forwarded to, to get the realtime error message:
http://awesomescreenshot.com/0111zhw889
(Note: I blocked out some sensitive info in these screencaps, hope that's not too distracting)
3 Replies
The replies under this section are restricted to logged in users or users with an active subscription with us
