[jira] [Commented] (SLING-8226) Adding custom sightly bindings

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (SLING-8226) Adding custom sightly bindings

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SLING-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747834#comment-16747834 ]

Mahsum Demir commented on SLING-8226:
-------------------------------------

I created a PR at [https://github.com/apache/sling-org-apache-sling-app-cms/pull/5] for this issue

> Adding custom sightly bindings
> ------------------------------
>
>                 Key: SLING-8226
>                 URL: https://issues.apache.org/jira/browse/SLING-8226
>             Project: Sling
>          Issue Type: New Feature
>          Components: App CMS
>    Affects Versions: App CMS 0.11.2
>            Reporter: Mahsum Demir
>            Priority: Minor
>             Fix For: Version App CMS 0.11.4
>
>
> Hi,
> Currently when a page is opened in editor mode a variable called "cmsEditEnabled" gets added to the request to indicate rendition of the page in editor mode. This variable can be easly used on JSP scripts but it is not easy to use it on sightly scripts.
>  
> What I propose is adding custom sightly bindings related to apache sling cms for such cases so in sightly scripts we can use then easily. For example  to find out if the page is opened in editor mode we can use ${isEditor}. These custom bindings can be added by individual bundles but adding these feature out of the box makes more sense to me.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)