I'm working on a TYPO3 project with a custom extension and I'm trying to set up femanager but I get the following error when I'm trying to use the backend module provided by femanager:
Class UserBackend does not exist
Does someone know why this error appears and how to get rid of it?
Related
I have the following problem accessing the "Settings > Extension Configuration" menu in my backend.
No class named TYPO3\CMS\Saltedpasswords\Utility\ExtensionManagerConfigurationUtility
Ajax Error
#1294585866 InvalidArgumentException
No class named TYPO3\CMS\Saltedpasswords\Utility\ExtensionManagerConfigurationUtility
in /data/www/www.my-domain.de/public/typo3_src-9.5.22/typo3/sysext/core/Classes/Utility/GeneralUtility.php line 3607
TYPO3 suggests to "check for broken Extensions" - no problems found.
I already tried to access the menu with all extensions disabled - same problem.
We upgraded our page a little while ago but since I did not find a fix for this issue. Does anybody know how to fix it?
The class namespace has been changed as the extension saltedpasswords has been merged into the core. See https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/9.4/Deprecation-85833-ExtensionSaltedpasswordsMergedIntoCoreExtension.html?highlight=extensionmanagerconfigurationutility for the documentation.
As a solution, use TYPO3\CMS\Core\Crypto\PasswordHashing\ExtensionManagerConfigurationUtility
I have to make an update from Typo3 8 to Typo3 9.5 LTS. And i have some trouble with the Flux extension which causes some strange errors. I have used Flux 9.4.2 (latest) and Typo3 LTS (9.5.22). I have used Composer for the new version perhaps that causes the problem.
I have followed all the steps in this tutorial and some others instructions but all of them ends in the same error.
https://sigalambigha.home.blog/2020/04/29/how-to-migrate-fluidcontent-to-flux/
In Backend i get the following error:
And in the Frontend i get this error:
This depends on the Flux element which is on that page the Slider element. The Plug & Play configuration is disabled because of some other errors. Perhaps now i missed something in my configuration but i can't find something in the documentation to configure.
Edit
I have made some more tests an i think the problem is that the newest version of Flux is not really compatible with Typo3 9.5. So i changed to version 9.3.2 which is working better but has other bugs.
Make sure these 3 things in your template provider extension are set correct:
Register the provider extension key using the Vendor.ExtName syntax, not ext_name. Here is an example:
\FluidTYPO3\Flux\Core::registerProviderExtensionKey('Nng.MyExtname', 'Page');
\FluidTYPO3\Flux\Core::registerProviderExtensionKey('Nng.MyExtname', 'Content');
Place the above code in the ext_localconf.php of your extension, not the ext_tables.php. You can find this hint hidden in the documentation.
In older versions of FLUX you might also need to create a ClassAliasMap in EXT:myextensionkey/Migrations/Code/ClassAliasMap.php. Here is a simple example.
Did you try to set a small condition for the used parameter if it's null? that maybe can give an error message instead of the error in the page.
Or you should see if there's any error in the namespace
After upgrading Flux to Typo3 9.5 then you have to register "VendorName" with your content element using Typoscript like i did below.
tt_content {
mytemplate_wrapelement.20.vendorName = <vendorname>
}
here mytemplate is my template provider extension.
Wrapelement is the content element.
I was getting same error.
I'm currently upgrading an old TYPO3 6.2 Installation to 9.5. I'm also using fluidtypo3 (flux 9.3.2 and fluidpages 5.0.0). There are several pibase Extensions, that I can't get to work. One of them has the following error:
Oops, an error occurred! Code: 20200320122044742c5a45 - {"exception":"TYPO3Fluid\\Fluid\\Core\\ViewHelper\\Exception: No Content Object definition found at TypoScript object path \"tt_content.list.20.edxdownload_pi1\"
Any hints what is causing the error? Did I forget anything to register?
I added the plugin in tt_content.php, registered it in localconf.php
(\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addPItoST43('edx_download','','_pi1','list_type',0);)
and added the config in sys_template.php
(TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addStaticFile('edx_download','Configuration/TypoScript/PluginSettings/', 'Edx Download Settings');)
If I make a new element using the new element wizard, I get the following error in frontend:
Content Element with uid "9887" and type edx_download_pi1 has no rendering definition!
Where do I have to set the rendering definition?
Do pibase extensions still work with TYPO3 9?
Edit:
It's working now. I put the method "addPItoST43" back into "ext_localconf.php" and now the extension is loaded. It says you should put it into "TCA/Overrides/tt_content.php", but that doesn't work for me with TYPO3 9.5.
I was trying to override
<preference for="Magento\Customer\Model\CustomerRegistry" type="Mycustom\Mymodule\Model\CustomerRegistry" />
under etc/di.xml. But after running the
php bin/magento setup:upgrade
command will get the 'catalog rule indexing failed' error message. And under the system.log file it will show the below error message -
Type Error occurred when creating object:
Magento\Customer\Model\ResourceModel\AddressRepository,
Note: I have deleted the generated folder and run all required commands. Also, my magento version is 2.3.
I had a similar issue with a preference over a class that is injected into a plugin constructor.
The problem seems to be caused by the Magento developer mode that doesn't have all of the DI data generated at the time the plugin is executed, causing the error when executing the constructor and the DI fails.
Switching to default mode seems to fix the problem.
bin/magento deploy:mode:set default
Anyways, I finally changed the implementation on the classes that use the overridden class in order to use a custom interface that is overridden by the preference, and use the module dependency to make my new module load after the modified one (using sequence dependency).
This is not the best solution, but it worked and I could do this because both modules are from my company, and are implemented in the app/code folder.
You should use plugins instead of preference if you can.
I have had the same issue and after hours of searching I saw some of the classes can not be overridden. You can see more details about this issue here:
https://github.com/magento/magento2/issues/2674
I used magento "around" plugin instead of <preference/>.
I'm currently running TYPO3 version 8.7.18 and running a site_package that was made by using the site package builder: link
Whenever I try to add a form by using the default backend forms module I get the default message Oops, an error occurred! along with that the following error
TYPO3\CMS\Form\Domain\Configuration\FormDefinition\Converters\AddHmacDataConverter not found
Searching for the issue I get several hits on the Gitlab but these do not provide any solution.
Along with this setup, I've added the forms module as a static include in my top-level template.
do you have a composer installation or an extension manager build up?
If a class is not found you may need to rebuild the autoloader information.
My error turned out to be caused by a corrupt installation. I've had to upload the file AddHmacDataConverter.php in the following path /public_html/typo3/sysext/form/Classes/Domain/Configuration/FormDefinition/Converters. A very weird error indeed.
For those that came here with the same error, make sure to check that folder. Apart from that add the news as a static inclusion in your top domain. You could also follow #Bernd Wilke's idea which s to disable the extension, clear all system caches (and additionally remove typo3/temp/autoload and then active the extension again.