Issue Task Closed

#35698Big usability problem @ new Extensionmanager

Gernot Ploiner 04/04/12, 22:07 updated 03/06/13, 21:34

Description

The new Extension Manager is very difficult to understand.
I have installed and documented the installation of Templavoila with one dependency (static_info_tables).
Look at the attached screenshots in guide.zip

There are 18 steps neccessary to install the two Extensions:
Step 01: Search Extension and click on import
Step 02: Close window (=Lightbox) after import
Step 03: Install first Extension
Step 04: Import dependent (second) Extension
Step 05: Close Popup (not Lightbox?) and recheck dependencies
Step 06: Recheck won’t be done
Step 07: Search first Extension again
Step 08: Install dependent (second) Extension
Step 09: Make Updates on Database for second Extension
Step 10: Click on Make updates to see the Extension-Settings-Form
Step 11: Click Update to set the Extension-Settings-Form
Step 12: Close Window
Step 13: Try again (remember this, don’t click on ‘Install now’ – this don’t bring you an errormessage)
Step 14: Make updates on Database for first Extension. Note: The Lightbox is too small. You have to scroll horizontal.
Step 15: Click on Make updates to see the Extension-Settings-Form
Step 16a: Bug: Duplicate Statusmessage in Lightbox
Step 16b: Search for the Update Button in the small Lightbox and click it to set the Extension-Settings-Form. If you forget this Step the Form Settings will not be set and an Errormessage in the Templavoila Backendmodule appears.
Step 17: Close the Lightbox. Ther is no close-link like before. Use the X in the top-right of the Lightbox. Now no Statusmessage appears. You have to know that you are ready now.
Step 18: Finished – we are ready to use the Extension

This is not reproduceable or understandable for a non-expert or TYPO3-beginner.

I would prefer a Guide (Step 1 of x), consequent Items (always use the Lightbox, always show statusmessages, always use the same next or close links on same positions.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.