My TYPO3 has broken after deactivating an extension (direct_email). I can't access my backend anymore and also I cannot deactivate the extension through the Installation tool.
This is the error that I got:
Errors after deactivating an extension sounds strange.
That only should occur if other extension do not have declared dependencies.
Aside from the PackageStates.php you should clean the caches. If you have no access to the Install_Tool (typoe/install) to clear the cache and check for broken extensions, you need to delete all caches in the cache-folders /typoe3temp/var/Cache (or similar, dependening on TYPO3 version)
You might give some more information about your installation (versions, kind of installation (composer), ..)
I got to work on a Typo3 page and I have to say I'm at the very beginning if it comes to TYPO3.
So I wanted to fix a bug and updated the plugin "fluidpages" from version 4.1.0 (I guess) to 4.3. That cause the "Oops, an error occurred!" in the backend and frontend, so I dont have access from that side. I still have the FTP login for the website. The version of TYPO3 is 8.7.18.
The errorcode I get is that one:
Could not analyse class:
"FluidTYPO3\Flux\Configuration\ConfigurationManager" maybe not loaded
or no autoloader?
Class FluidTYPO3\Flux\Configuration\ConfigurationManager does not exist
So does anyone know what I need to do?
From my research I think I need to update another plugins to make it back to work? And can I update them just by uploading them through FTP?
Thanks in advance!
Edit: After I tried to get the old version of the plugin running, I'm getting this error code from the log file:
Mon, 17 Feb 2020 22:59:56 +0100 [ALERT] request="fec23f8baf6dc" component="TYPO3.CMS.Frontend.ContentObject.Exception.ProductionExceptionHandler": Oops, an error occurred! Code: 2020021722595594039a4d - {"exception":"TYPO3\CMS\Extbase\Mvc\Exception: The default controller for extension \"Flux\" and plugin \"Page\" can not be determined. Please check for TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin() in your ext_localconf.php.
You can enter the Install Tool via https://example.org/typo3/install.php and start with Check for broken extensions. If that doesn't yield the extension in question, you can always manually change the PackageStates.php file and remove the extension you want to unload. Afterwards you should flush all caches through the Install Tool.
In the long term you should consider a few things:
Use a local development environment which mirrors your production environment. You can safely perform all steps without any risk here before deploying.
Use a deployment strategy/tool which allows for rollbacks. This allows you to quickly revert to a working version of your instance in case all other checks have failed. A simple but flexible solution is Deployer, you'll need SSH for this though.
Have you tried dumping autoload from Install Tool? Generally, it would help for the class not loaded problem. Otherwise, you may want to check the log at typo3/temp/var/log/ and find the errors in code.
I found one solution, download latest version from VSCode website. I tried same but still facing this issue.
i want to add React Native extension.
I am unable to access this URL because of the Proxy.
How to resolve this issue?
I'm using VSCodium On Archlinux and had the same problem. I installed vscodium-bin-marketplace to make it work. There's also a package named code-marketplace for Code OSS.
I found a solution that works for me.
Stop VSCode.
Open ~/.vscode/argv.json if you're using VSCode
Open ~/.vscode-oss/argv.json if you're using VSCodium
Then add
// Browser Code Loading.
"enable-browser-code-loading": false
Don't forget to add a comma to the previous entry, since this is a JSON file (but you knew that already, right?).
This just worked for me:
Add the proxy server to VS Code settings.json (open it in VSCode command line)
Add keys "http.proxy" and "https.proxy" with values of your Proxy Server URL, for example:
settings.json:
{
...
"http.proxy": "http://my-http-proxy-server.com:123",
"https.proxy": "https://my-https-proxy-server.com:124"
}
Bypass the url from proxy.
Open proxy settings (run command - inetcpl.cpl)
Go to connection tab, now in your proxy add that url
If it works then ok . Else you have to contact network team or need to do some firewall settings
Unistall vscode from unins000.exe C:\Users\{username-PC}\AppData\Local\Programs\Microsoft VS Code
Delete C:\Users\{username-PC}\AppData\Roaming\Code
Delete C:\Users\{username-PC}\.vscode
Restart
I went to Toggle Developer Tools. As described in here. Saw that ERR_TUNNEL_CONNECTION_FAILED error is there.
I had a proxy server added to the network settings. (Which was working fine for other purposes) I had to remove the proxy server in order to get this working.
Deleting my .vscode (hidden folder) worked for me.
C:\Users\USERNAME.vscode
Other alternative could be uninstalling vscode and deleting the whole folder at
C:\Users\USERNAME\AppData\Local\Programs\Microsoft VS Code
1.Unistall vscode from unins000.exe C:\Users\{username-PC}\AppData\Local\Programs\Microsoft VS Code
2.Delete C:\Users\{username-PC}\AppData\Roaming\Code
3.Delete C:\Users\{username-PC}\.vscode
4.Restart
5.Reset your windows firewall
6.Restart and install Vscode
This worked for me: in extensions search box, wrote #color (I'm guessing searching for anything will do) and extensions tab populated with results. Never saw the error again.
I recommend this solution for linux operating systems:
in file ~/.vscode-oss/argv.json
add this line: "enable-browser-code-loading": false
I am using kaspersky antivirus, disable it for a while, and my problem solved.
If no option works above. You can install the extension through the Vsix file.You can download it from this site.
Vsix File Free Download
If you are using linux you can install code-marketplace using your package manager which in my case it's pamac.
Just like this:
pamac build code-marketplace
This fixed my problem loading extensions in vscode.
goto your pc settings and look for proxy
turn it all off
that worked for me
I just uninstalled vscode downloaded it again and it works fine now for me you can try out this once
When you look at the ip-traffic what it tries to do, it starts with DNS-query with A-record (good) and also with AAAA-record (not so good if you don't have proper v6 routing in place).
Application should have built-in code to try AAAA-record connections and if they fail, it should automatically fall back to v4-connections and routing. Now it fails to do so and just gives an error that it failed to connect marketplace. Well, you just didn't try hard enough, did you?
For Linux systems, you disable your host's v6 protocol with:
# sysctl -w net.ipv6.conf.all.disable_ipv6=1
net.ipv6.conf.all.disable_ipv6 = 1
# sysctl -w net.ipv6.conf.default.disable_ipv6=1
net.ipv6.conf.default.disable_ipv6 = 1
and you might want to write them into /etc/sysctl.conf file as well.
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
I did it using the world's best editor Vim! :)
You need to restart the application before marketplace starts working.
the apollo-graphql extension was marked as malicious (I'm sure mistakingly) ... I need to enable it to work with it as I really enjoy it.
How can I force VS Code to enable it?
You can install it again, it was disabled by MS because of the
Event-Stream package problem
I've updated my Typo3 from 4.5.5 to 4.7.0 and I get several deprecated errors:
ERROR: Content Element type "login" has no rendering definition!
call to undefined error in t3lib_div::view_array
fail to include class.t3lib_htmlmail.php
The install tool gives me "typo3/ext/ directory not writable" but I've the correct right. I've even allow all?????
When I select a CType Element in the BE it give me this warning: PHP Warning
PHP Warning: Invalid argument supplied for foreach() in /var/www/typo3_src-4.7.0/t3lib/l10n/parser/class.t3lib_l10n_parser_llphp.php line 95
The solution for 2. is to use the new class t3lib_utility_debug but what is with the other errors?
Edit: 1. http://lists.typo3.org/pipermail/typo3-english/2011-November/078129.html
Edit 2: The solution for the missing class t3lib_htmlmail is to include another class t3lib_mail_message: require_once(PATH_t3lib .'mail/class.t3lib_mail_message.php');
You solved allready: install system extension "felogin"
you solved allready: use t3lib_utility_debug
check where the error is from. Often it is helpfull to search for that file in typo3conf/temp_*.
You could check your filesystem, if your webserver is allowed to write to typo3/ext/. I guess, it is not. But you do not need to. Usually you install extensions to typo3conf/ext/.
Update your language files via the extension manager.
Well, i know it is to late now, but for all others wo think about an update: just activate the deprecation log in the isntall toll and fix that problems first!
Updating from 4.5.X to 4.7.x broke my felogin as well. The reason was that there has been a local extension installation that has been of higher priority than the system one. So if you suffer the same update issue, check for an local installation of felogin in "typo3conf/ext" - and delete it in case it is there. This solved my problem!