this is a good one. if i'm not wrong, object_id was used in the firsts versions of ezflow, but that was changed to node_id.
for me, it makes sense. when you browse for adding these elements to the blocks, you browse nodes and not objects.
if you use the browse thing and probably select and object with several locations, how to tell ezflow that the result should link to that node and not to the main_node of the object?
but i see your point. if you swap nodes probably you'll get some unwanted side effect, but ihmo that should be solved adding things to the swap operation. i mean 'if i swap this, look to ezflow blocks and change what is needed...'
Cheers.
SEBBANE Alexandre
Wednesday 08 June 2011 9:52:33 am
I agree with Carlos. besides when you choose a source in an dynamic blocs : which node had to be chose ...
Ezflow helps us to create pages in order to show the content tree in an another way : the content tree is for me a tree of nodes before a tree of object...
Alex
Paris, France
gilles guirand
Thursday 09 June 2011 3:14:57 am
No, i speak about the ezm_block table, and not the ezm_pool table. This table is storing the link between a "page" and its block, and not the link between a block and its related items (ezm_pool job)
oh i see... yep, didn't realize this... this is totally different question... btw, i wondering what will happen if you add a block to a object with several locations... will it create several entries in that ezm_pool table?
i will try and see... but if the answer is no... then why we need that node_id there?
SEBBANE Alexandre
Thursday 09 June 2011 10:07:20 am
yep same thing didn' see it at first time .
maybe something like cache you have the same in the all location so having the node_id avoid calculate cache many times ?
Alexandre
Paris, France
You must be logged in to post messages in this topic!
