Hi Daniel,
I don't fully understand what you mean by:
"The flip side of it is that everytime a a public node is node potentially it
introduces some discrepancy in the order, because in the meantime the client
may have changed the position on one node in the app"
Do you mean "everytime a public node is down"?
Some answers to your questions and some comments:
1) Maybe. If you don't provide an Order-By clause in your search, then the
node-order depends on two things:
a) the setting "respectDocumentOrder" in your Indexing configuration for
the workspace, see: http://wiki.apache.org/jackrabbit/Search.
b) the "Orderable Child Nodes" setting for the node-type in question, as
some NodeTypes may not actually support it (although I think this is not an
issue with Jackrabbit)
2) Yes, but potentially with high performance impact (if it is a large subtree).
3) No, I don't know of a better way
4) Why is this even an issue? When publishing to multiple nodes, publishing
will normally fail if one of the subscribers can't be reached. The activation
will then be rolled back on all the other subscribers. So activation state
should always be consistent, even if a public node is down. If you find this
not to be the case, then you should file a urgent high priority Bug with
Magnolia.
5) If you are activating content even when one of your public nodes is down
(i.e. not using the transactional activation), then you really need to run the
synchronization module for all workspaces that were changed in the meantime.
The synchronization module should bring your public node to the correct state,
including the node order (if not, file a bug with Magnolia!).
Regards from Vienna,
Richard
> -----Ursprüngliche Nachricht-----
> Von: user-list-ow...@magnolia-cms.com
> [mailto:user-list-owner@magnolia- cms.com] Im Auftrag von Daniele
> Biagi (via Magnolia Forums)
> Gesendet: Freitag, 16. Oktober 2015 12:31
> An: Magnolia User List
> Betreff: [magnolia-user] Show items on public instances keeping the
> same order as shown on browser subapp on author
>
> Hi,
> I have created product catalogue Magnolia app that is used by our
> client to create and update products.
> The client wants to see the products in the pages following the same
> order as they are shown in our Magnolia app.
> First thing I thought was to do a JCR query and assuming that the
> results are in the same order as shown in the JCR browser I can
> provide the results directly to the view
>
> (template script).
> However, considering that we have also 2 public instances (at least)
> everything becomes a bit more complicated because the order of the
> nodes in the public instance may vary,
>
> therefore I think the only way to ensure to have all the nodes in the
> same order in all instances is to unpublish all the nodes from author
> and then republish them all.
> The flip side of it is that everytime a a public node is node
> potentially it introduces some discrepancy in the order, because in
> the meantime the client may have changed the
>
> position on one node in the app, or had published something, therefore
> when the public node comes back a complete unpublish and publish of
> all nodes would be required.
>
> So the questions are:
> 1.Is correct to assume that a JCR query would retreive the node in the
> same order as they are shown on the Magnolia app (browser)?
> 2.Unpublish and publish all the nodes would guarantee that the order
> of the nodes is the same across all the servers?
> 3.Does anybody knows any better way (or authomatised/brainless way) to
> preserve the order of the nodes between author and several public
> instances?
>
> --
> Context is everything: http://forum.magnolia-
> cms.com/forum/thread.html?threadId=f81e17ec-9755-4257-a9ab-
> 999153dada3b
>
>
> ----------------------------------------------------------------
> For list details, see http://www.magnolia-cms.com/community/mailing-
> lists.html
> Alternatively, use our forums: http://forum.magnolia-cms.com/ To
> unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com>
> ----------------------------------------------------------------
----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------
