Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Issue with wcmmode=disabled

Avatar

Level 2

We have a requirement that when page is opened with query parameter wcmmode=(disabled | preview), then links on that page should also open in same mode.

Does anyone know how to achieve this?

Its working as expected for wcmmode=preview, but for wcmmode=disabled all the links on that page are opening in preview mode.

Any pointers would be helpful.

Thanks!

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

I think the below design should help you

You need to rewrite all href link on the page by appending wcmmode=disabled,

  • Create a Transformation class and extend it from the org.apache.cocoon.xml.sax.AbstractSAXPipe
  • In the startlement iterate all attributes of element
  • Find href link
  • Check if it contains query string with wcmmode=disabled
  • if so then rewrite url
  • finally assign back to href

Check below sample code :

   public void startElement(String uri, String loc, String raw, Attributes attributes) throws SAXException {

        AttributesImpl attrs = new AttributesImpl(attributes);

     

            for (int i = 0; i < attrs.getLength(); i++) {

                String name = attrs.getLocalName(i); 

                if(name.equals("href"))

                {

                    String url = attrs.getValue(i);

                    // write an if condition to check url endwith wcmmode or not

                    / if so then rewrite th url something like below

                    url = "http://keysandstrokes.info?wcmmode=disabled";

                    //finally set value back to the href attribute

                    attrs.setValue(i, url);                        

                }

            }

       

        super.startElement(uri, loc, raw, attrs);

       

    }

Example: you can use it as it is by applying your logic in the start element

http://keysandstrokes.info/apache-sling-rewriter-how-to-rewrite-urls-in-aemcq5/

Approach 2:

You can also do this using Jquery, but you must have knowledge of it. Using Jquery find out all href links and rewrite it, this is simple than approach 1 and it will not put any burden on the server as it is authoring environment so we can consider this. the Jquery should load at end of the page once the entire DOM is loaded.

You need to load Jquery only in author mode don't execute on publish mode.

Approach 3 :

Check is there any OOTB functionality available or not, if not then try above approaches.

View solution in original post

13 Replies

Avatar

Community Advisor

Why you need to do this ? In author if you want to simulate something similar, one quick way to do it is removing editor.html from your URL . Something like http://localhost:4502/content/website/en_US/home.html . This will open all the corresponding links in preview mode only

Avatar

Level 1

yes, thats right. But i believe this works for simple components like text image etc. But in case we have an accordion or other similar components the functionality wouldn't work well only by removing editor.html. we would also need to append ?wmcmode-disabled in the url. 

Avatar

Community Advisor

You can do this with customization but before that please check once is it really required? if so I can put a design for this.

Avatar

Correct answer by
Community Advisor

I think the below design should help you

You need to rewrite all href link on the page by appending wcmmode=disabled,

  • Create a Transformation class and extend it from the org.apache.cocoon.xml.sax.AbstractSAXPipe
  • In the startlement iterate all attributes of element
  • Find href link
  • Check if it contains query string with wcmmode=disabled
  • if so then rewrite url
  • finally assign back to href

Check below sample code :

   public void startElement(String uri, String loc, String raw, Attributes attributes) throws SAXException {

        AttributesImpl attrs = new AttributesImpl(attributes);

     

            for (int i = 0; i < attrs.getLength(); i++) {

                String name = attrs.getLocalName(i); 

                if(name.equals("href"))

                {

                    String url = attrs.getValue(i);

                    // write an if condition to check url endwith wcmmode or not

                    / if so then rewrite th url something like below

                    url = "http://keysandstrokes.info?wcmmode=disabled";

                    //finally set value back to the href attribute

                    attrs.setValue(i, url);                        

                }

            }

       

        super.startElement(uri, loc, raw, attrs);

       

    }

Example: you can use it as it is by applying your logic in the start element

http://keysandstrokes.info/apache-sling-rewriter-how-to-rewrite-urls-in-aemcq5/

Approach 2:

You can also do this using Jquery, but you must have knowledge of it. Using Jquery find out all href links and rewrite it, this is simple than approach 1 and it will not put any burden on the server as it is authoring environment so we can consider this. the Jquery should load at end of the page once the entire DOM is loaded.

You need to load Jquery only in author mode don't execute on publish mode.

Approach 3 :

Check is there any OOTB functionality available or not, if not then try above approaches.

Avatar

Community Advisor

You can try out Rajas approaches if its a real need. Recommend not to do such customization as you have a publish whose job is to render your final content . Its always best to verify content of any working page in preview mode and then publish it and verify the final content in your publish.

Avatar

Community Advisor

Actually, I feel this is also a good requirement without replicating to publish environment you can check it on author instance itself, this is very useful when you want to make authoring productivity high

Avatar

Level 1

Hi
Just wanted to know
is AEM 6.5 is unstable?
I am trying to create the form and integrate with the REST endpoint , via email, pdf, prefill adaptive forms.
Nothing is working out for some reason.
is 6.5 not stable?

Thanks