Hello, when previewing pages in WEM we sometimes still need to add the parameter "&vgnextnoice=1" to the preview URL in order to display correctly.can some one look into it and advice.
Qutub,
You say "This view of page has been productized in preview of wem 8.5"
How is it productized? Is there a button or link in the preview tools that will give you this view? I have not found it. We really need this view for our customers.
Lori Dingman
Wells Fargo
Hi All,
Let me correct myself, functionality is not yet productized. I used a new option which is under gear icon of wem 8.5/10.5 called "Full Page View" (which sort of trying to do it by just deactivating css and some menu options).
But to get to real live view we need to get rid of any div generated for preview tooling as well. I used a technique described below.
For all templates
At top of template check if page is in edit mode
<%-- Page is not being previewed in full screen mode thus set value as true--%>
All regions have been wrapped in JSTL as
In html section where we include preview tooling activating javascripts.
And also above solution only works for customer using DSM. DPM will be bit more tricky.
I hope this clarified the idea, this is a common problem and this is a simple work around. This can even be applied to older WEM version where "Full Page View" doesn't exist by adding the link for "Full Page View" at top of the page or bottom of the page just outside the body tag.
something like
<a href="?vgnextnomenu=1" >Full Page View</a>
Best Regards
Hi,
You can also try by appending “vgnextbrowsemode=true” to the URL then ice tool bar and region divs will go away. If you want to see ice tool bar again then append “vgnextbrowsemode=false” to the URL.
Thanks & Regards,
Sreenivasa Rao Venepalli
9866121761
From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]Sent: Monday, June 22, 2015 11:40 PMTo: eLink RecipientSubject: RE WEM preview - adding "&vgnextnoice=1" to preview URL to display correctly
RE WEM preview - adding "&vgnextnoice=1" to preview URL to display correctly
Posted byqsaifudd@opentext.com (Saifuddin, Qutubuddin) On 06/22/2015 02:09 PM
<c:setvar="edit"value="false"scope="request"/>
<c:iftest="${inMgmtCDSeq'true' && (emptyparam['vgnextnomenu'] ||not(param['vgnextnomenu']eq'1'))}">
In html head section where we include preview css.
<c:setvar="edit"value="true"scope="request"/>
<templating:styleSheet/>
</c:if>
<c:choose>
<c:whentest="${editeq'true' }">
<templating:contentRegionname="Story Components"displayInContextEdit="true"/>
</c:when>
<c:otherwise>
<templating:contentRegionname="Story Components"displayInContextEdit="false"/>
</c:otherwise>
</c:choose>
<templating:in-context-edit/>
<templating:scripts/>
Qutubuddin SaifuddinArchitectOpen TextMobile : 732 397 7951Email : qsaifudd@opentext.comWebsite : www.opentext.com
From: eLink Entry: Discussion Group - Web Experience Management [v7webcontentmanagement@elinkkc.opentext.com]Sent: Monday, June 22, 2015 12:21 PMTo: eLink RecipientSubject: WEM preview - adding "&vgnextnoice=1" to preview URL to display correctly
WEM preview - adding "&vgnextnoice=1" to preview URL to display correctly
Posted bylori.g.dingman@wellsfargo.com (Dingman, Lori) On 06/22/2015 12:12 PM
[To post a comment, use the normal reply function]
Topic:
Forum:
Discussion Group - Web Experience Management
Content Server:
Knowledge Center
Sreenivasa,
Thanks for the input but this mode will still generate the wrapper divs, which will impact the layout.
It all comes down to how css is written by a typical designer. Defining default attributes on div or other tags is pretty common for them and very hard to live without, specially if they need to produce complex html layouts on small notice. So even if we clear all the display attributes in product css which will hide all the div's generated by product, still there will be site/page specific css which will add some gutter, padding, margin,font or some other attributes to divs by default, which product has no control over. This will result in layouts breaking and look & spacing issue still being present in preview.
To truly see a view in preview env which mimics the html produced in live stage we will need to get rid of all the wrapper html generated by product along with any css & js includes and that's what you can achieve via product tag lib or Java API as demonstrated below.
One thing which I did not get rid off was the wrapper div produced for inline editing. As they are still manageable and not that common. So I didn't invest time in dealing with them, but they can be eliminated if needed as well.
Once all product specific css/js and div wrappers are eliminated, what you see then is real view as would appear in production. And this is what a content editor/approver will like to see before they press the publish button.
Thanks
From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com] Sent: Monday, June 22, 2015 11:40 PMTo: eLink RecipientSubject: RE WEM preview - adding "&vgnextnoice=1" to preview URL to display correctly
