[TYPO3-english] Remove extension manually (Typo3 6.2)

[joel zimmerli]

Just after I installed yag_gallery 3.2.7 on Typo3 6.2 almost all the "admin" menus in BE (extension manager, languages, install, etc.) are not available anymore. When I click on the menu, I received the following error:

Oops, an error occurred!
Class Tx_PtExtbase_Utility_FeBeModeDetector does not exist

As I canot use the Extension manager menu, I'm wondering how I can delete(uninstall) this extension?

I already tried to delete the entry "yag" in LocalConfiguration.php and deleted all files under typo3temp but I still get this error.

If I just rename the "yag" directory under typo3conf/ext, the whole BE access is not available (blank screen!).

What is the right way to delete this extension manually?
Thank you in advance for your help.
Regards,
Joel

[bernd wilke]

Post by joel zimmerli
Oops, an error occurred!
Class Tx_PtExtbase_Utility_FeBeModeDetector does not exist
As I canot use the Extension manager menu, I'm wondering how I can delete(uninstall) this extension?
I already tried to delete the entry "yag" in LocalConfiguration.php and deleted all files under typo3temp but I still get this error.
If I just rename the "yag" directory under typo3conf/ext, the whole BE access is not available (blank screen!).
What is the right way to delete this extension manually?

since 6.2 you can call the install-tool (.../typo3/install/index.php)
and remove extensions which break the installation

also since 6.2 installed extensions are no longer noticed in
LocalConfiguration.php but in PackageStates.php
so you need to modify this file if you want to do it by hand (not
recommended).

bernd

[Anja Leichsenring]

Hi Joel,

after you got yourself in such a trouble, do the following:

1. Edit typo3conf/PackageStates.php: find the extension that caused the
crash and change its status from active to inactive. Save the file,
delete typo3temp/Cache/* and try again to access the Backend.

2. If you can't access the Backend yet, go to the install tool by using
the url your.domain/typo3/install/index.php. Enter the important actions
section, clear the cache with the button there, and if you get the
option, clear the opcode cache as well.

Now you should be able to access the backend. If you don't, repeat the
steps with other extensions you might have installed before.

If you already renamed folders in typo3conf/ext, remove this folder and
delete PackageStates.php. It will be recreated after you logged into the
Backend, but you have to activate all your extensions again using the
ExtensionManager.

Never ever rename folders in typo3conf/ext, also no backing up
extensions like one could do before 6.2, just leave the folder alone.
PackageStates.php will break otherwise.

Hope that helps
Anja

Post by bernd wilke

Post by joel zimmerli
Just after I installed yag_gallery 3.2.7 on Typo3 6.2 almost all the
"admin" menus in BE (extension manager, languages, install, etc.) are
not available anymore. When I click on the menu, I received the
Oops, an error occurred!
Class Tx_PtExtbase_Utility_FeBeModeDetector does not exist
As I canot use the Extension manager menu, I'm wondering how I can
delete(uninstall) this extension?
I already tried to delete the entry "yag" in LocalConfiguration.php
and deleted all files under typo3temp but I still get this error.
If I just rename the "yag" directory under typo3conf/ext, the whole BE
access is not available (blank screen!).
What is the right way to delete this extension manually?

since 6.2 you can call the install-tool (.../typo3/install/index.php)
and remove extensions which break the installation
also since 6.2 installed extensions are no longer noticed in
LocalConfiguration.php but in PackageStates.php
so you need to modify this file if you want to do it by hand (not
recommended).
bernd

[Xavier Perseguers]

Hi Anja,

Post by Anja Leichsenring
1. Edit typo3conf/PackageStates.php: find the extension that caused the
crash and change its status from active to inactive. Save the file,
delete typo3temp/Cache/* and try again to access the Backend.

What about warning the user prior to the initial activation when the
extension has no TYPO3 dependencies, just as we do when trying to
activate an outdated extension?

Cheers
Xavier

[Anja Leichsenring]

Hi Xavier,

this is the ext_emconf.php of yag extension 3.2.7, that Joel uses.
Nothing wrong with it. So what do you mean? I think I don't get your point.

Greets Anja

https://github.com/YAG-Gallery/yag/blob/6dbba03df9bbdf247a21bc35ea4ff3eff8d1a306/ext_emconf.php

Post by Xavier Perseguers
Hi Anja,

Post by Anja Leichsenring
1. Edit typo3conf/PackageStates.php: find the extension that caused the
crash and change its status from active to inactive. Save the file,
delete typo3temp/Cache/* and try again to access the Backend.

What about warning the user prior to the initial activation when the
extension has no TYPO3 dependencies, just as we do when trying to
activate an outdated extension?
Cheers
Xavier

[joel zimmerli]

I tested on Typo3 4.7 and 6.2 and both instal do not have pt_extlist and pt_extbase.
Do you think this can cause my problem? Maybe this is what means Xavier: if other extensions are required, a warning should be displayed, and yag shouldn't be installed. What do you think?
Regards,
Joel



Le Vendredi 5 septembre 2014 14h25, Anja Leichsenring <aleichsenring at ab-softlab.de> a ?crit :



Hi Xavier,

this is the ext_emconf.php of yag extension 3.2.7, that Joel uses.
Nothing wrong with it. So what do you mean? I think I don't get your point.

Greets Anja

https://github.com/YAG-Gallery/yag/blob/6dbba03df9bbdf247a21bc35ea4ff3eff8d1a306/ext_emconf.php

Post by Xavier Perseguers
Hi Anja,

Post by Anja Leichsenring
1. Edit typo3conf/PackageStates.php: find the extension that caused the
crash and change its status from active to inactive. Save the file,
delete typo3temp/Cache/* and try again to access the Backend.

What about warning the user prior to the initial activation when the
extension has no TYPO3 dependencies, just as we do when trying to
activate an outdated extension?
Cheers
Xavier

[Xavier Perseguers]

Hi Anja,

Post by Anja Leichsenring
this is the ext_emconf.php of yag extension 3.2.7, that Joel uses.
Nothing wrong with it. So what do you mean? I think I don't get your point.

Was not speaking about this particular case because I did not pay
attention to the faulty extension.

What I mean is following. If you try to install extension X which has
dependency with TYPO3 < currently used, you get a warning, I find it
perfect! If you try to install extension Y which has NO dependencies,
you get no warning at all. Since every extension is now supposed to have
dependencies set (and it's a good practice for in house extensions as
well), I would suggest to throw a warning as well in that case.

[Philipp Gampe]

Hi Xavier,

Post by Xavier Perseguers
What I mean is following. If you try to install extension X which has
dependency with TYPO3 < currently used, you get a warning, I find it
perfect! If you try to install extension Y which has NO dependencies,
you get no warning at all. Since every extension is now supposed to have
dependencies set (and it's a good practice for in house extensions as
well), I would suggest to throw a warning as well in that case.

+1

Best regards

[Stefano Kowalke]

Another way is to use the command line interface. Execute the following
command from your document root:

$ ./typo3/cli_dispatch.phpsh extbase extension:uninstall yag

That uninstalls the extension (not delete it)

Regards
Stefano

Post by joel zimmerli
Oops, an error occurred!
Class Tx_PtExtbase_Utility_FeBeModeDetector does not exist
As I canot use the Extension manager menu, I'm wondering how I can delete(uninstall) this extension?
I already tried to delete the entry "yag" in LocalConfiguration.php and deleted all files under typo3temp but I still get this error.
If I just rename the "yag" directory under typo3conf/ext, the whole BE access is not available (blank screen!).
What is the right way to delete this extension manually?
Thank you in advance for your help.
Regards,
Joel

[Sara]

I've just installed yag now and got the same problem.

If extensions are required then this should be flagged up on install and not do as this has which is lock out all the admin functions.

I'm QUITE annoyed that this has not been rectified by the extension creator.