when upgrading from TYPO3 8.7 to 9.5 i got this error message in the install tool :
Something went wrong. Please use Check for broken extensions to see if a loaded extension breaks this part of the install tool and unload it.
The box below may additionally reveal further details on what went wrong depending on your debug settings. It may help to temporarily switch to debug mode using Settings > Configuration Presets > Debug settings.
If this error happens at an early state and no full exception back trace is shown, it may also help to manually increase debugging output in typo3conf/LocalConfiguration.php:['BE']['debug'] => true, ['SYS']['devIPmask'] => '*', ['SYS']['displayErrors'] => 1,['SYS']['systemLogLevel'] => 0, ['SYS']['exceptionalErrors'] => 12290
Now i am lost because i dont know how to unload an extension ...
- i cant login in the backend
- the install tool is gone - no possibility to get it running again
- typo3conf/autoload is deleted
- typo3temp is deleted
- and in packagestate there is no possibility to unload an extension
I even emptied the complete extension folder but nothing changes.
How is it possible to unload a extension in TYPO3 9 and get the install tool running? Why does it break?
Thanks!
You could either use the command line with
vendor/bin/typo3 extension:deactivate <EXT-KEY>
or delete the array entry for your extension in the file public/typo3conf/PackageStates.php. In both cases, you may need to also clear public/typo3temp/var manually.
Related
I've taken over a company that is currently running WHMCS 8.4.1 and has a custom built add-on module.
I want to upgrade WHMCS to 8.5.1 so I set up a dev environment and installed the add-on files to it.
As soon as I try to open the add-on I get the following error:
Whoops\Exception\ErrorException: Declaration of ProductExtended\Core\Models\WHMCS\Product::pricing() must be compatible with WHMCS\Product\Product::pricing($currency = ): WHMCS\Product\Pricing in /Users/steph/Sites/localhost/whmcs/modules/addons/ProductExtended/Core/Models/WHMCS/Product.php:22
Stack trace:
#0 /Users/steph/Sites/localhost/whmcs/vendor/whmcs/whmcs-foundation/lib/Utility/Error/Run.php(0): WHMCS\Utility\Error\Run->handleError(64, 'Declaration of ...', '/Users/steph/Si...', 22)
#1 [internal function]: WHMCS\Utility\Error\Run->handleShutdown()
#2 {main}
I've never done any WHMCS coding before, but based on the error I would assume that there have been changes in the core way that
pricing()
is coded.
All the main files are encrypted so impossible to look at those to see what differs to version 8.4.1
Does anyone have any suggestions on where I might find some resources to help resolve this, and likely other changes that could affect the add-on?
I have looked at the 8.5.1 Realease Notes, Changelog and What's New documents, but found nothing specifically related to code changes.
Check to see whether /Users/steph/Sites/localhost/whmcs/modules/addons/ProductExtended/Core/Models/WHMCS/Product.php is coded by ioncube (the default WHMCS PHP encoder)
If you do not have access to the source code of the module, there's nothing you can do to fix the issue. You would need to contact the developer to have the module updated to support the version of WHMCS that you need.
If the module code is encoded, there's no way (at least legally) that you can decode it.
I installed gkeep plugin for Neovim (https://github.com/stevearc/gkeep.nvim) and didn't like it. I removed it from my plugins (I use vim-plug) and run :PlugClean after that. But now I can't open neovim without error mentioning that gkeep plugin. How to fix this?
Error detected while processing function remote#define#request:
line 2:
Error invoking '/home/daniil/dotfiles/nvim/plugged/gkeep.nvim/rplugin/python3/gkeep:autocmd:BufEnter:*'
no request handler registered for "/home/daniil/dotfiles/nvim/plugged/gkeep.nvim/rplugin/python3/gkeep:
It's pointing to ~/dotfiles/nvim because I created symbolic link from ~/dotfiles/nvim to ~/.config/nvim.
Also, there is no directory gkeep.nvim inside plugged folder.
UPD: and this is my plugins
It seems that you haven't removed the configuration related to gkeep.nvim. Try to remove all settings related to gkeep.nvim.
Also, when you open neovim, run the command :UpdateRemotePlugins. It should solve your issue.
I have created an authentication module which was build against
ejabberd 16.02 and runs fine when auth_method is set. It also works against
16.03.
However, from 16.04 onwards it gives me the error "[error] ignoring
option 'auth_method' with invalid value: [jwt]"
I checked the code diff between those releases and the only change
seems to be to the mod_pubsub.erl file, specifically adding the
following:
ServerHost = serverhost(Host),
+ ejabberd_hooks:run(pubsub_subscribe_node, ServerHost,
+ [ServerHost, Host, Node, Subscriber, SubId]),
https://github.com/processone/ejabberd/commit/639c2fb6401391663206c0e4c946d1a699689ac7
I have tried disabling this module and even deleting the beam file as
i don't use it, but i can't seem ti get round it.
Does anyone have any insight as to why these changes will have broken
my authentication module?
My source is at the link below, but as i say has worked fine for a year:
https://github.com/ParamountVentures/ejabberd-auth-jwt
The answer is that from 16.04 onwards you need to drop the .erl file into the ejabberd src folder and compile it with the source. Dropping in the .beam file to use alternative authentication modules no longer works.
I've performed an update from typo3 4.7.20 to 6.2.15. The process worked fine and there were no critical errors while running the install tool.
The frontend looks fine but the backend is broken:
I've removed all uncompatible extensions before I run the update. I've also checked all settings in the installationtool und deleted the temp/cache folder first.
I've got the feeling that the error is caused by the TemplaVoila! extension, I'm using v. 1.9.8. Firebug does not shows any error.
Does anyone had a similar problem and have already solved it?
Thank you very much!
I have come across this one multiple times. More often it is because there is a broken TBE_STYLES. I suggest you look around for $TBE_STYLES in your typo3conf folder and disable it for the time being. Most likely it will be in the extTables.php or some other file which is included dynamically.
seems BE is working, but you css does not got loaded.
check your 'web inspecter' to see if you get errors on loading CSS.
clear your cache (remove everything in typo3temp) and try again
I installed prestashop successfully through your marketplace, and been able to play around with it and also to upload new modules. But every time i try to install the uploaded modules, i get this message
"The following module(s) were not installed properly:"
But the prestashop default modules do install without issues.
What is causing that problem? because the same modules were uploaded and installed without issues on cpanel shared web hosting?
Check modules sql commands for installation. I think module has an character issue. if u enable debugmode and display errors on config/defines.inc.php u can see where the error is.
If u cant solve.
Find this line on your module main php ( for "testmodule" its "testmodule.php") "if (!DB::getInstance()->execute(trim($query))) return false;" some think like that. And remove or close this line. But when u doing this u must manualy run modules sql code with phpmyadmin or something else after or before install module.
modules sql files usualy "install.sql" but some this coders add sql code on modules main phps.
This is a generic error and means that your module installation has failed.