Bug #22669
closed
getExtensionKeyByPrefix() not working for user_-namespace
Added by Julian Hofmann over 14 years ago.
Updated over 8 years ago.
Sprint Focus:
Remote Sprint
Description
For extensions in the user-namespace (e.g. 'user_example'), the arraykey in $extensionKeyMap is the full extensionkey instead of only the non-prefixed part. As result, no real extensionkey is found.
Should be fixed with the following changes:
- $shortKey = str_replace('_', '', $extensionKey);
+ $shortKey = ? substr($extensionKey, 5) : str_replace('_', '', $extensionKey);
In combination with the scheduler and autoloader this occures "unable to autoload" exceptions for user_*-classes used as AdditionalFieldProvider
(issue imported from #M14409)
Little mistake in my fix:
- $shortKey = str_replace('_', '', $extensionKey);
+ $shortKey = substr($extensionKey, 0, 5)=='user_' ? substr($extensionKey, 5) : str_replace('_', '', $extensionKey);
- Status changed from New to Needs Feedback
- Target version deleted (
0)
The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 4.7)?
getExtensionKeyByPrefix() in version 6.1 is still the same code as it has been in 4.3.
So, I would expect the same behaviour.
- Status changed from Needs Feedback to New
- Assignee set to Mathias Schreiber
- Target version set to 7.1 (Cleanup)
- Is Regression set to No
- Sprint Focus set to Remote Sprint
- Target version changed from 7.1 (Cleanup) to 7.4 (Backend)
- Target version changed from 7.4 (Backend) to 7.5
- Target version changed from 7.5 to 7 LTS
- Status changed from New to Needs Feedback
- Target version deleted (
7 LTS)
Hey Julian,
could you recheck this in v7? I think we tackled the autoloading part as we reworked this area in the last months.
- Status changed from Needs Feedback to Closed
- Assignee deleted (
Mathias Schreiber)
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
Also available in: Atom
PDF