Details
-
Type:
Bug -
Priority:
3 - Medium -
Resolution: Unresolved
-
Affects Version/s: WCM 2.16
-
Fix Version/s: None
-
Component/s: Mars
-
Labels:None
-
Story Points:5
-
Epic Link:
-
Sprint:Mars Sprint 24
-
Issue Source:Quality Assurance
Description
NPE only: After running the app conversion scripts for articles, headlines or flex editor, if the content has unsupported legacy content, the warning message cannot be read when editing in the sidebar.
Example: The apps are located at http://usqaalpha.schoolwires.net/domain/295
The entire conversion message will show in the old experience, but is cutoff in the new experience.
Solution: See notes from Jason Coudriet.
Acceptance criteria:
- Message should continue to show when using the classic editing experience
- Message should be hidden in new sidebar editing until modifications are made in a future release.
- Apps affected: Article Library, Headlines and Flex Editor.
-----------------------------------
Tested on:
Mac:
Firefox - 47
Chrome - 54.0.2840.71
Safari - 10
PC:
Chrome - 54.0.2840.71
IE - 11.0.28
C2WebApp Assembly version: 2.16.0.1
Build Time: 11/3/2016 2:19 PM
C2BusinessLayer Assembly version: 2.16.0.1
Build Time: 11/3/2016 2:18 PM
Database Version: 2.16.110416
Activity
gregg pavlik Could you add a link to your app with the warning message?
The apps are located at http://usqaalpha.schoolwires.net/domain/295
Considering "fixing" would cause problems (i.e. more real-estate being taken up) and future plans to adjust the experience for large WYSIWYG instances, I suggest we hide the warning when in the sidebar for this release. Keeping it as is, will unnecessarily add a "broken windows" effect. Below is the code that will hide it from the sidebar, but not affect the other areas.
.sidebar-editing-detail .leagacyContent
{ display: none; }
Note: Hosting runs the conversion script. You can submit a request by using the form at http://hostingtasks.schoolwires.com/
Ivo Novosad - attaching app conversion sql script to the bug for reference in case you cannot access the Release folder. If any questions, let us know. Thanks.
Steps to reproduce:
1/ Create a classic app (Headlines classic, Articles classic, Flex editor)
2/ Run conversion script which will change classic app to the newer/dashboard stream capable version app ( \\10.181.0.41\d$\Releases\WCM\v2.15.x(C2.15 Fall 2016 Release)\Database Scripts\Scripts to be Merged\DONOTMERGE_NPE_ClassicAppsOff.sql )
3/ Check the message in changed app
4/ Check that Headlines from changed app are displayed in Stream
What should be the parameters of the script, I mean SWModuleID on lines 13 and 17? Did you run it with defaults or did you change it?
Jason Coudriet
I wanted to see how your team would like to handle this one, since I know you were considering other adjustments to the width of the sidebar for editing.