Message-ID: <771410101.3062.1485851824422.JavaMail.confluence@ip-10-127-227-164> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3061_1055104356.1485851824422" ------=_Part_3061_1055104356.1485851824422 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
EZP Version >=3D 5.3
To have the regular Webin Toolbar, first add the proper CSS file to your=
head template : extension/ezwt/design/standard/stylesheets/websiteto=
olbar.css
<style type=3D"text/css"> @import url("{{ asset('extension/ezwt/design/standard/stylesheets/websi= tetoolbar.css') }}"); </style>=20
Then, in your template, you can add the Webin Toolbar by definining the =
display of the websiteToolbarAction
from the ezpublish_l=
egacy.website_toolbar.controller
Controller
{% if location is defined %} {{ render( controller( "ezpublish_legacy.website_toolbar.controller:web= siteToolbarAction", { 'locationId': location.id} ) ) }} {% endif %}=20
Versions: 5.3.4, 5.4.1.
In order to get properly redirected after publishing or discarding, over=
rides of legacy's content/edit.tpl
must include the =
content/edit_redirection.tpl
. It adds hidden fields required b=
y legacy for those redirections.
<form method=3D"POST" action=3D"content/edit/..."> <!--...--> {include uri=3D"design:content/edit_redirection.tpl"} </form>=20
The websiteToolbarAction renders the whole Webin Toolbar, and if the log= ged in user doesn't have the required permission, an empty response is retu= rned