Bug #16762
closed
User Management: Modules maximum
Added by mback2k over 17 years ago.
Updated over 6 years ago.
Description
I have installed some backend extensions for TYPO3 and I have also coded some own backend extensions.
While administrating the user modules I found out, that there is a limitation, because the userMods field is limited to 255 bytes.
I am getting this error if I select too many modules:
These fields are not properly updated in database: (userMods) Probably value mismatch with fieldtype.
I have now fixed this problem, by reducing the length of the extension names.
(issue imported from #M4609)
Files
TYPO3 Ver. 4.3.2: I can confirm this problem.
Field userMods: varchar(255)
If there are some modules, that is easily to small.
added a patch for that issue
- Assignee set to TYPO3 Release Team
- Target version changed from 0 to 4.5.4
TYPO3 Ver. 4.5.3: The problem still remains.
Fielddefinition of userMods is varchar(255).
If there are some modules, that is easily to small.
The field has only to be changed to text. Is there anything to be said against it?
- Target version changed from 4.5.4 to 4.5.6
- Target version changed from 4.5.6 to 4.5.8
- Target version changed from 4.5.8 to 4.5.12
- Category set to Backend API
- Status changed from New to Accepted
- Assignee changed from TYPO3 Release Team to Philipp Gampe
- Priority changed from Should have to Must have
- PHP Version changed from 4 to 5.2
- Complexity set to no-brainer
Old one, but still valid ...
- Status changed from Accepted to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
The database schema was changed in order to fix this bug. This is unusual for a patch level release, but we decided to backport it anyway with the following rationale:
- New installations get the correct field definition from start (bug fixed).
- Old installations updating to the newest patch level by simply updading the TYPO3 Sources (usual procedure): No change of functionality, nothing breaks. But the bug won't be fixed.
- Old installations which need this bug fixed need to apply the TYPO3 Source Upgrade and do an one time "Database Compare" in the Install Tool afterwards.
So the last step is optional and only required if you are really hit by this bug.
As usually the ACL for available BE modules are configured at group level (and not at user level), most integrations won't be affected by this bug anyway.
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by