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

On 05.09.2014 10:48, bernd wilke wrote:
Am 05.09.14 09:35, schrieb 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?

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

_______________________________________________
TYPO3-english mailing list
[email protected]
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

Reply via email to