Jan 2021
3 / 3
Jan 2021
Jan 2021
AlexS
Jan '21
1

Dear @ngegw

in my application I use different datastoreprefixes for the same nextmatch depending on the specific use I call the list. For example I have a Infolog index in the main window with the datastoreprefix infolog.infolog_ui and a filtered infolog list inside an iframe in a different app with the datastoreprefix ‘infolog.infolog_acclients’. This is very usefull because when columns setting are saved the datastoreprefix enables to have different settings for the columns in the first and the second scenario.

As we had noticed also together some time ago, the drag and drop linking and the right click menu for linking in my infolog application was not showing up. Today a figured out that is was due to the this line https://github.com/EGroupware/egroupware/blob/b892c547971e213db4789792fed246c7109d7cb3/api/js/etemplate/et2_extension_nextmatch_controller.ts#L3981 and @RalfBecker helped my add an entry to the registry

Now the problem it that the links are not created because Nextmatch still expects to find an application::id here

But instead finds my datastoreprefix. infolog.infolog_ui which EGroupware\Api\Etemplate\Widget\Link::ajax_link can’t handle.

Do you have an idea how this could be solved?

Thank you in advance!
Greetings
Alex

  • created

    Jan '21

  • last reply

    Jan '21
  • 2

    replies

  • 989

    views

  • 2

    users

  • 3

    links

ngegwEGroupware GmbH
Jan '21

If you just want different display preferences, changing columnselection_pref would be better.
We mess with it a bunch and apply some suffixes to it to store visible columns, column widths, letter search, etc. Infolog uses it for details / no-details, but it’s better just to set it once.

dataStorePrefix is used for client side caching, linking & push updates and should be an application registered in the link registry. If your rows are genuine infolog entries and your ID 4 = Infolog ID 4, you should leave it as ‘infolog’ so all nextmatch widgets that show infologs can share the same cache, and all the automatic stuff works. If you consider these different data, you need a different dataStorePrefix (which defaults to your application name).

It is possible that the projectmanager elements doesn’t work, because as you point out elsewhere they don’t match.

AlexS
Jan '21

Dear Nathan,
thank you so much for this clarification. I noticed that I was already using columnselection_pref in my apps, a had forgotten it over time… After your post and I looked again at my code and now it is clear to me.
Thanks again and best regards
Alex