Can i force "card view" when sharing a link to the sites console? | Community
Skip to main content
F
fourthWaII
June 27, 2022
Solved

Can i force "card view" when sharing a link to the sites console?

  • June 27, 2022
  • 3 replies
  • 1007 views

I believe column view is the default for users viewing on desktop... but for certain 'decentralized' authors responsible for very specific items, I would prefer they land on the page in card view to keep things as straightforward as possible. 

 

Is there a URL parameter or something I can include in the URL to determine what view option is selected? e.g: http://localhost:4502/sites.html/content/brand/product/internal-resources?view=card

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SantoshSai

Hi @fourthwaii ,

You have to extend collectionpage

/libs/granite/ui/components/shell/collectionpage/collectionpage.jsp

This is the default code that sets the view (column view) of the page when it loads:

String targetViewName = getTargetViewName(slingRequest, consoleId);

List viewCache = new ArrayList();
Resource currentView = null;

int i = 0;
for (Iterator it = resource.getChild("views").listChildren(); it.hasNext(); i++) {
	Resource item = it.next();

	if (i == 0 || item.getName().equals(targetViewName)) {
    	currentView = item;
	}

	viewCache.add(item);
}

For more details please visit this article: http://aem-podcast.com/2017/aem-interface/default-views-aem-sites-content-tree/#.Yrm3KOzMJb8
Hope that helps!

Regards,

Santosh

3 replies

SantoshSai
Community Advisor
SantoshSaiCommunity AdvisorAccepted solution
Community Advisor
June 27, 2022

Hi @fourthwaii ,

You have to extend collectionpage

/libs/granite/ui/components/shell/collectionpage/collectionpage.jsp

This is the default code that sets the view (column view) of the page when it loads:

String targetViewName = getTargetViewName(slingRequest, consoleId);

List viewCache = new ArrayList();
Resource currentView = null;

int i = 0;
for (Iterator it = resource.getChild("views").listChildren(); it.hasNext(); i++) {
	Resource item = it.next();

	if (i == 0 || item.getName().equals(targetViewName)) {
    	currentView = item;
	}

	viewCache.add(item);
}

For more details please visit this article: http://aem-podcast.com/2017/aem-interface/default-views-aem-sites-content-tree/#.Yrm3KOzMJb8
Hope that helps!

Regards,

Santosh

Santosh Sai
    Himanshu_Jain
    Community Advisor
    Himanshu_JainCommunity Advisor
    Community Advisor
    June 27, 2022

    1. Overlay the /libs/dam/gui/content/assets/jcr:content/views/card and under /apps/dam/gui/content/assets/jcr:content/views/card

    2. Add a property sling:orderBefore to the list node , something like below

    name: sling:orderBefore String card

    3. The XML looks something like this

    <views jcr:primaryType=”nt:unstructured”>

    <card

    jcr:primaryType=”nt:unstructured”

    sling:orderBefore=”card”/>

    </views>

     

    Refer : https://www.nextrow.com/blog/adobe-experience-manager/make-list-view-as-default-view-in-aem-assets (This is for list view) 

    You can do the same for card view.

     

    Thanks

    Himanshu

     

    Himanshu Jain
      SantoshSai
      Community Advisor
      SantoshSaiCommunity Advisor
      Community Advisor
      June 27, 2022

      @himanshu_jain That is for dam asset view not for content tree.

      Santosh Sai
        Himanshu_Jain
        Community Advisor
        Himanshu_JainCommunity Advisor
        Community Advisor
        June 27, 2022

        Thanks @santoshsai  for highlighting.

        Himanshu Jain
          arunpatidar
          Community Advisor
          arunpatidarCommunity Advisor
          Community Advisor
          June 27, 2022

          Hi,

          There is a cookie, which is responsible for showing card layout, if someone you can inject this cookie from dispatcher/slingFilter based on the IP or usergroup then you will be fine

           

          cq-sitescard
          Arun Patidar
            Terms & ConditionsAccessibility statement

            Loading footer...