Fit namespaces of TYPO3 6.0
Currently many functions use the old deprecated class names of TYPO3 < 6.0. This leads to a problem i.e. when using gridelements2 with the extension fluidpages from fedext.net (paramater type hint is tx_cms_layout but fluidpages extends this class and due to the mapping to the old classes the inheritance isn't resolved).
Due to the reason that gridelemts is only for TYPO3 > 6.0 it should be adjusted to the new namespaces. I started to do this in drawitemhook and it's test to get it working together with fluidpages again. I could try to adjust the rest if my appraoch doesn't cause any problems or conflicts.
#2 Updated by Jo Hasenau over 6 years ago
- Status changed from New to Under Review
- Assignee changed from Stefan Froemken to Kevin Ulrich Moschallski
- PHP Version set to 5.3
We really appreciate your help, since this is one of the last things we have to tackle before we will be able to release 2.0.
I made you a member so you should be able to push your changes to the review system (branch 2-0)
#4 Updated by Jo Hasenau over 6 years ago
Since TYPO3/CMS is reserved for extensions that are already part of the official core package, I guess we will have to stick to our own namespace.
After all it's more likely that the core will not include more extensions but get rid of them to get lean and clean code base.
We could use Cybercraft as a vendor name, but maybe this is too prominently promoting the company and not the team.
#5 Updated by Kevin Ulrich Moschallski over 6 years ago
I would suggest choosing "GridElementsTeam" as vendor name, but as i'm not really in the development of the extension i leave this to you, as you also did the fundraise.
After refactoring all the class names i would proceed with the folder structure. My suggestion would be:
I left out the other folder which simply would be renamed to UpperCamelCase.
I'm not quite sure with some files as i don't know the whole structure yet, so please help me to form the structure well. We should get rid of the ext_autoload.php with this scheme, right?
I'll push my current state of refactoring ASAP.
#11 Updated by Kevin Ulrich Moschallski over 6 years ago
There is a small bug in the changeset. I fixed it and pushed it but it doesn't appear on gerrit.
Do i need to create a new issue because the path is already in 2-0?
Anyway here is the fix:
replace the line
return call_user_func_array(array(\TYPO3\CMS\Backend\Utility\BackendUtility, $methodName), $arguments);
return call_user_func_array(array(new \TYPO3\CMS\Backend\Utility\BackendUtility, $methodName), $arguments);
Sorry for the trouble.