Bug #30168

Suggest wizard list differs from group selector

Added by Francois Suter almost 8 years ago. Updated about 4 years ago.

Should have
FormEngine aka TCEforms
Target version:
Start date:
Due date:
% Done:


TYPO3 Version:
PHP Version:
Is Regression:
Sprint Focus:


When the suggest wizard is used for a group-type field, the list of items inside which the suggest wizard searches may be different than the list of items displayed in the selector itself, because permissions are not checked the same way. In particular the suggest wizard takes mount points into account while the selector's list doesn't.

We must make sure that the same selection criteria apply to both lists.


#1 Updated by Andreas Wolf almost 8 years ago

  • Category changed from Backend User Interface to FormEngine aka TCEforms
  • Status changed from New to Accepted
  • Complexity set to medium

Yeah, true. The group list is filled by t3lib_loadDBgroup if I'm not mistaken - I'm not too sure if we can use this for the suggest wizard, too.

Anyways, I intended the suggest wizard to be used for data sets where a normal selector box does not make sense - what is your use case for having both? Maybe you would be better of with a filter box above the selector? Or is this just a general remark because you noticed it while developing?

#2 Updated by Francois Suter almost 8 years ago

What do you mean "having both"? Is there a way to hide the normal selector box? I always have both.

My use case is mostly group-type fields related to tables with lots of entries, where it's really not possible to make choices in the selector.

Yes, a filter box above the selector would be better, but that doesn't exist in the Core AFAIK. Or did I miss something?

#3 Updated by Francois Suter almost 8 years ago

OK, sorry about the "both" thing. I now see in another project quite a few fields with just the wizard. I can't access the other project right now, but I think there's some customization done on the selectors, so that's maybe why we have the selector and the wizard.

Anyway the problem remains that the suggest wizard does not work like the selector and IMO the suggest wizard is wrong. It should not be necessary to have access to some records to be able to make relations to them. Of course, this is debatable. Maybe it should be a configuration option.

#4 Updated by Chris topher almost 8 years ago

  • Target version changed from 4.5.7 to 4.5.8

#5 Updated by Ernesto Baschny over 7 years ago

  • Target version changed from 4.5.8 to 4.5.12

#6 Updated by Alexander Opitz almost 5 years ago

  • Status changed from Accepted to Needs Feedback
  • Target version deleted (4.5.12)
  • Is Regression set to No


does the problem still exists within newer versions of TYPO3 CMS (6.2.9)?

#7 Updated by Francois Suter over 4 years ago

I would guess there's a fair chance that the problem still exists, but I can't remember what was my use case anymore, so I can't check. I think this can be closed for now, although I wouldn't consider it as resolved.

#8 Updated by Alexander Opitz over 4 years ago

  • Status changed from Needs Feedback to Closed

#9 Updated by Roman Ott about 4 years ago

I know the problem always exists, also in TYPO3 7.2


Extension X provides Person Data like employees
Extension Y is for Joboffers, here i have a mm-relation to select an employee for a joboffer as contact person.

Both Extension-Data are stored in different sys_folders

Content Manager for Joboffers have access only to sys_folder with joboffer-data.
In the mm-selectboxes he can see als employees and select some employees as contact.
This field also has the suggest wizard, but if the content-manager type in a search, he got no results.

So i think suggest and select should have the same access rights.
It would be great to have a switch (respect access rights or no) for both

Best Regards Roman

#10 Updated by Nicole Cordes about 4 years ago

  • Status changed from Closed to New
  • TYPO3 Version changed from 4.5 to 7
  • PHP Version deleted (5.3)

Also available in: Atom PDF