What I'm trying to say is so many Conditions could be controlled on the server, within nested repeats, Client side nest the repeats, and only show those with results.
Actually I already have the Server as a nested repeat
This page for example has 6 modules to publish. But I dont get how to pass only this modules in this order to the browser.
Now I use a repeat region Pointed to ProjectModulesPublish list and run all the list.
Inside that I have 9 conditional regions one for each module possible available.
But I dont feel this is the best approach. I like more what you are telling me that only pass to browser the needed modules but dont know how to. Thanks in advance for your orientation.
Read up on how to display the output from nested repeats in the documentation it will be a lot easier to understand. Grasp the basics of it, don't rush. You'll only make mistakes and confuse yourself. Once you understand those basics it is very simple and will make your life so much easier. It is a powerful feature when implemented. You will use it a lot once you get to grips with it, especially in this kind of scenario.
I improve the server but still struggling with the Conditional regions. I need one for each possible module??
Hey Juan,
From your conditional regions ids, It looks like you're trying to achieve a kind of CMS...
Can you please show us in your browser how is your page rendered when some of these conditional regions are true and other that the same conditional regions are false?
I hope you understand what I mean...
If you actually have a "Gallery" element in your page and it is not rendered what happens to the page layout? The same for all the others
I think that you could approach this in different way... Let me go at the office and think better and reply to you
I am not sure if there is any very satisfactory way to do this in Wappler. You mention 9 different conditional regions. Supposing over time this increases to 20 or 100 etc. You'll be forever updating the code (preferably server-side rather than on the front-end, using conditional regions etc.).
You would need a dynamic solution which doesn't involve any code updating.
It seems this was possible in Wappler, but, strangely, only due to a 'bug' - and the bug has been removed. It's a pity the bug can't be reinstated and integrated as a very useful new feature.