Created Extension deletes Class-Folder in dependency
Trying to create an extension to extend gridelements the whole Class-Folder in gridelements is deleted on installation.
In the model I extended tt_content with 3 fields (select, string, string), added gridelements as dependency - that's all.
Installing the extension then without any further adjustments shows
Fatal error: require_once(): Failed opening required '.../typo3conf/ext/gridelements/Classes/Hooks/PreHeaderRenderHook.php' (include_path='.../syriansabroad.de/typo3/contrib/pear/;.;\xampp-win32-1.8.2-0-VC9\php\PEAR') in ...\typo3_src-6.2.12\typo3\sysext\core\Classes\Core\ClassLoader.php on line 197
Having looked up then for the missing file I remarked that the whole class-folder is missing.
Before gridelements worked.
#1 Updated by Nico de Haen over 4 years ago
- Status changed from New to Needs Feedback
I can hardly imagine, that the ExtensionBuilder deletes a folder in another extension. The only use case, where class files are deleted is, if a Model is deleted in the UI and that happens always relative to the current extension directory.
Could you reproduce that behaviour?
#2 Updated by David Bruchmann over 4 years ago
- File gecewrapper.zip added
Yes, I could hardly imagine too.
I could reproduce the behavior and deleted the classes of gridelements 3 or 4 times.
I don't know exactly if the extension builder deleted the classes but I don't think so.
Probably the produced extension did it when activated, but I don't know why and how to track it down.
Finally I changed the file-rights of gridelements and set them to read-only.
One problem is, when the files are deleted the backend is not working anymore.
I attache the extension but already in a further state. To reproduce just use the extension-builder to overwrite my changes.
#3 Updated by Nico de Haen over 4 years ago
Sorry, can't reproduce it. So you have to debug that yourself and if you find an error in the ExtensionBuilder report it.
A good start would be: uncomment the \EBT\ExtensionBuilder\Service\RoundTrip::cleanUp function. That's the only function that unlinks files.
If that changes the behavior the error is most in ExtensionBuilder...