Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There are a couple of approaches:</p> <ol> <li>Rewrite the urls on the outbound response in CQ (as suggested by David)</li> <li>Rewrite the urls on the inbound request using mod_rewrite at dispatcher (assuming Apache)</li> </ol> <p>As David covered scenario 1, I'll describe the second scenario</p> <p>The "sticky" selector value can be returned in a cookie to the client</p> <pre><code>Set-Cookie: selector=stickyselector; </code></pre> <p>Each subsequent request to the site from the client will contain that cookie. You can then use that cookie to rewrite in the URL in apache before it gets presented to the dispatcher module (and eventually the publish instance:</p> <pre><code>RewriteCond %{HTTP:Cookie} selector=([^;]+) [NC] # If we have the selector cookie RewriteRule ^(.*)\.html$ /$1.%1.html [PT] # add it to the request url before extension </code></pre> <p>So a request that arrives at the dispatcher looking like this:</p> <pre><code>GET /content/mysite/mypage.html HTTP/1.1 Cookie: selector=stickyselector; </code></pre> <p>Would arrive at the publish instance rewritten as:</p> <pre><code>/content/mysite/mypage.stickyselector.html </code></pre> <p>If you are using this approach for device/channel specific renditions then you <em>could</em> alternatively use the user agent value instead of a cookie to drive selector addition. For example:</p> <pre><code>RewriteCond %{HTTP_USER_AGENT} "iphone|ipod|iemobile" [NC] RewriteRule ^(.*)\.html$ /$1.mobile.html [PT] # add channel selector to the request url </code></pre> <p>Positives of this approach are that all users are presented with the same URL (e.g./content/mysite/mypage.html) the selectors in URLs are only presented to CQ.</p> <p>Negatives are that it normally would require cookies and it depends on apache configuration.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow would you go about persisting selectors in links in CQ5 / AEM
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USdiffa
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow would you go about persisting selectors in links in CQ5 / AEM
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CONeat! Will definitely give this one a go. Thanks mate.
      singulars
      1. PO
      1. USBayani Portier
    2. COAwesome solution. Thanks so much.
      singulars
      1. PO
      1. USBayani Portier
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload