Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Here are some answers:</p> <p>1) Here is a good article about different configs for different runmodes: <a href="http://helpx.adobe.com/cq/kb/RunModeSetUp.html" rel="nofollow">http://helpx.adobe.com/cq/kb/RunModeSetUp.html</a> you can create configs for pub and auth runmodes with certain flag your code will look for which will tell whether to execute import or not.</p> <p>2) It depends. CQ tends to have copies of content for mobile site so it may make sense to do copies of nodes for mobile site but only in case you those nodes are pages (cq:Page and cq:PageContent) you create based on imported data. Otherwise you just need to save imported data somewhere and obtain it at some moment (via JCR queries or methods like .getNode()). In this case of course it makes sense not to copy your data.</p> <p>3) It depends here as well. I would consider following forces you may have: should imported data be editable? how frequent are updates? how massive are updates? how critical is consistency across pubs? In case updates are not massive, not frequent and consistency matters import to auth followed by replication can work. Also it may be the case if you need to be able to edit imported data. In case updates are massive and/or frequent and consistency across pubs do not matter much (you can afford that some people may see different results from different pubs during import) I'd suggest run import on all pubs at the same time since massive replication of imported data may affect regular page/images replications.</p> <p>Thanks, Max.</p>
    singulars
    1. This table or related slice is empty.
    1. POImporting Product in Adobe CQ5
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMaksim Kviatkouski
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHi Max, Thank for the reply. Can I just clarify couple of things? I'm currently spiking a scenario where I import products and store them as cq:Pages, which works fine with exception of two things that I rather dislike - I have to make a copy of each product for each site; Content seems to be too coupled to the view. So if I did NOT use cq:Page, how else would I map URLs(keeping them SEO friendly) to my content, taking in account that CQ is very data-centric.
      singulars
      1. PO
      1. USKostya
    2. COHi Kostya, in case you have 1to1 product → page relation I'd stay with it. Instead of making copies of product data as a part of import process you could use rollout mechanism http://bit.ly/XXhUiL suggested by Adobe. If you want to decouple content and view you could use some kind of naming convention. Say, page /content/yourapp/catalogue/product1.html will look for node /var/import/products/product1. Also you could populate pages with reference to imported node. So page will contain a property which will point to node /var/import/products/product1.
      singulars
      1. PO
      1. USMaksim Kviatkouski
 

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