Comment to 'I think so.....Custom Modules Made Easy in UNA CMS – No Coding Required'
Comment to I think so.....Custom Modules Made Easy in UNA CMS – No Coding Required

  • Hello @Chris Andre Buys !

    Could you please explain what parts of the Developer app you want to see with more expanded explanation? And even Developer is a very nice module, but in some cases you need to create your own app anyway because some things are possible to do only there.

    • @LeonidS my friend, funny enough I was expecting you to respond.. and much appreciated 🙏

      For me, the exciting part is how the Developer app already gives us a “jump start” into module creation without needing to touch too much code. I’m especially curious about how the different sections — Settings, Polyglot, Forms, Navigation, and Pages — all tie together to form a complete custom module.

      A more expanded explanation (or even a walkthrough) of how those pieces interact would help a lot, especially for people like me who want to move from basic setup to real custom module building.

      I do understand that sometimes a fully custom app will still be necessary, but having a clearer map of what the Developer app can (and can’t) do would really help us get started.

      Thanks again, it means a lot to have your guidance.

      • Glad to know that my appearance was expected :-) About your question. The Developer app provides the advanced versions of the main UNA service apps like the Polyglot, Forms, Pages and Navigation for the already existing modules and Settings for the whole UNA. For example, you may create a new form via the Developer->Forms app with all possible settings, but for the start to work with it you need to use the following code like:

        bx_import('BxDolForm');
$oForm = BxDolForm::getObjectInstance('sample_form_objects', 'sample_form_objects_add'); // get form instance for specified form object and display
if (!$oForm)
    die('"sample_form_objects_add" form object or "sample_form_objects_add" display is not defined');
$oForm->initChecker(); // init form checker witout any data - adding new record
if ($oForm->isSubmittedAndValid())
    echo 'inserted id: ' . $oForm->insert (); // add new record to the database 
echo $oForm->getCode(); // display form

        So without own sample module described here and here you can't use this form. The sample module can be found here . But yes, the description of every page and field of the Developer app will be good anyway.

        • Thanks a lot for the detailed explanation @LeonidS — it really helps to see how the Developer app connects with the underlying service apps like Forms, Pages, and Navigation. The code example makes it clearer how something created in Developer actually comes to life once it’s tied into a sample or custom module.

          I understand now that the Developer app gives us the advanced tools to define things like forms or pages, but the real power comes when those are plugged into a module, one we create. That’s why I feel a step-by-step walkthrough (or documentation that shows the full flow from creating in Developer → wiring it into a custom module → seeing it work on the site) would be a game-changer for people like me who are just getting into UNA development, and trust me, I think the entire unacms community.

          Please man, maybe a video or so ...