When the user is editing a web content from an asset publisher he doesn't see the same actions as in "back" edition

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: Master
• Fix Version/s: 7.0.0 DXP FP33, 7.0.0 DXP SP7, 7.0.5 CE GA6, 7.0.X, 7.1.X, Master
• Component/s: Content Display Widgets > Asset Publisher widget, WCM > Publication
• Labels:
  • QA-AUTOMATION
  • QA-NF
  • Training-Auto
  • backend_test
  • ee-ts
  • liferay-digital-enterprise-70-sp7
  • liferay-fixpack-de-33-7010
• Branch Version/s:
  7.0.x
• Backported to Branch:
  Committed
• Story Points: 1.25
• Fix Priority: 3
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/50597
• QA Test Name:
  • LocalFile.PGWebcontentsearch#SearchWebContentTag
  • LocalFile.WebcontentUsecase#AddLocalizedWebContentViaSourceEditor
  • LocalFile.WebcontentpublicationUsecase#ViewWebContentWithConfiguredDisplayPageViaAP
  • PGWebcontentsearch#SearchWebContentTag
  • WebcontentpublicationUsecase#ViewWebContentWithConfiguredDisplayPageViaAP
• QA Test Score: 25

The problem

Olaf Kock
WC Editor: Permissions, Preview no longer available in DXP, Folder choice
7/26/16 2:14 AM
Hi team,
a customer is heavily using permissions on Web Content. The "Permission" button as well as the "Preview" button, which were formerly available in the UI now moved to the "three-dots-menu" which is only available from ControlPanel/SiteAdministration, but not when editing/creating an article in a popup, like from AssetPublisher (which they also heavily used, as it sets the categories/tags correctly for that AP instance).
This looks like an oversight with the Lexicon UI design rules and they (as well as myself) would expect the options to be available from everywhere.
(see attached screenshots for popup-editor and SiteAdministration editor with popped-up-three-dots-menu (does it have a name?))
Also (sorry, forgot in first submission of this question):
The popup editor allows no choice of the folder in which to store the article. This makes it impossible to encourage users to use the low-friction option to "add article" from places like AssetPublisher and keep a good overview over the location of the articles: All of the articles created this way will end up in the root folder, rendering the "folder storage for web content" useless. Is this an oversight?