4 / 4
Sep 2023

Hello,

We would like to design and run a template with a nextmatch in a tabbox… It used to work until the version 21 included. The same nextmatch in the same sub-template outside the tabbox works, but not inside a tabbox (no headers and no lines show up, as if the widget is simply not called). The nextmatch would be necessary because we have sometimes several hundreds of line to show and filter in an edit form… Would someone have a idea where to debug this ?

Another nice option seems gone, on the tabbox, align_tabs=“v”. It made the tabs collapsing in accordion, like this. The design was prettly cool. Is there still a way to do it ?

Thank you !

Thomas

  • created

    Sep '23
  • last reply

    Sep '23
  • 3

    replies

  • 571

    views

  • 3

    users

  • 1

    link

We have a customer using nextmatch in a tabbox, currently working on updating his code for 23.1, which has not reported a problem with NM.

@ngegw any idea?

This is now a separate widget, as it is only used (in EGroupware) as an automatic alternative for tabs on mobile phones. You can use it as <et2-tabbox_mobile:

Ralf

We have several nextmatches on tabs and it is working.

Make sure your nextmatch IDs are different, and that the tab templates & row templates are defined before they are needed (higher up in the file).

After that, I’d check to see if the widgets are being created using a breakpoint in the nextmatch constructor. That will help narrow down where things are going wrong.

Nathan

Hallo Ralf,

Many thanks, the et2-tabbox_mobile is working to display the accordion and the nextmatch is also working in it. Altogether, we have our nextmatch in our tabbox now !

Cheers,

Thomas