I’m trying to update a TYPO3 site from version 9.5.30 to version 10.0.0.
I have the following error:
(1/1) #1549446998 LogicException TYPO3\CMS\Core\Cache\CacheManager can
not be injected/instantiated during ext_localconf.php loading. Use
lazy loading instead.
Do you really update to TYPO3 10.0.0? You can and should update directly to version 10.4 (10.4.20 as of today).
According to the TYPO3 bug tracker (#88843, #88975), there were problems which have been fixed already a long time ago.
Related
I did a fresh composer installation of TYPO3 v11.5.9...
composer require "typo3/cms-adminpanel:^11.5" "typo3/cms-backend:^11.5" "typo3/cms-belog:^11.5" "typo3/cms-beuser:^11.5" "typo3/cms-core:^11.5" "typo3/cms-dashboard:^11.5" "typo3/cms-extbase:^11.5" "typo3/cms-extensionmanager:^11.5" "typo3/cms-filelist:^11.5" "typo3/cms-fluid:^11.5" "typo3/cms-fluid-styled-content:^11.5" "typo3/cms-form:^11.5" "typo3/cms-frontend:^11.5" "typo3/cms-impexp:^11.5" "typo3/cms-info:^11.5" "typo3/cms-install:^11.5" "typo3/cms-lowlevel:^11.5" "typo3/cms-opendocs:^11.5" "typo3/cms-recordlist:^11.5" "typo3/cms-recycler:^11.5" "typo3/cms-redirects:^11.5" "typo3/cms-reports:^11.5" "typo3/cms-rte-ckeditor:^11.5" "typo3/cms-scheduler:^11.5" "typo3/cms-seo:^11.5" "typo3/cms-setup:^11.5" "typo3/cms-tstemplate:^11.5" "typo3/cms-viewpage:^11.5"
and added fluidtypo3/flux, composer installed v9.5.0:
composer require fluidtypo3/flux
I created a sitepackage with sitepackagebuilder.com.
In the ext_localconf.php I registered Flux like this:
\FluidTYPO3\Flux\Core::registerProviderExtensionKey('Vendor.Sitepackage', 'Content');
\FluidTYPO3\Flux\Core::registerProviderExtensionKey('Vendor.Sitepackage', 'Page');
After adding a root page, creating a main template record, including all static templates and adding the TypoScript to the page, I opened the page in the frontend. The following error occured:
(1/2) #1278450972 TYPO3\CMS\Extbase\Reflection\Exception\UnknownClassException
Class Page does not exist. Reflection failed.
No matter what extension settings are defined or if any templates are present in Resources/Private/Tempaltes/Content/, the exception persists.
But, if I change the version of Flux to dev-development, the frontend loads perfectly fine.
Does anybody know what's going on here? What am I doing wrong?
I found the problem.
The file ext_localconf.php has a faulty condition to check the TYPO3 core version, which leads to a wrong $pageControllerName (row 136). It's Pageinstead of \FluidTYPO3\Flux\Controller\PageController::class which explains the exception message. (The wrong condition also occurs in file Classes/Integration/ContentTypeBuilder.php).
This bug has been fixed in branch development commit #19279684f1792f373d3a1fafdbde4dea0e4e12d9.
after updating to version 19 and ag-grid-community package. I'm getting following error while running ng serve:
ERROR in node_modules/ag-grid-angular/src/interfaces.ts(20,5): error TS6133: 'IToolPanel' is declared but its value is never
read.
I couldn't find any other stackoverflow question / github issue created about it.
This issue happens when you have noUnusedLocals in your tsconfig enabled.
I've reported this to ag-grid team again and they recognized that as a bug. Fix should be released in v20 version by the end of 2018.
I need to upgrade my ajaxcontroltoolkit dll version - 3.0.20820 with the latest version 16.1
Below are couple of controls/class, for which I am facing issue:
CollapsiblePanelExtender: property used: CollapsedCssClass & ExpandedCssClass
PasswordStrength: property used: Strength
CalendarExtender: property used: CalendarMode & Enum - CalendarModeType
Q. What can we use instead of above properties as they are not available in version - 16.1?
I got error in Fluidpages on frontend:
TYPO3 v6.2.11
Flux v7.2.0
Fluidpages v3.2.0
vhs v2.3.1
As before I have setup many projects with Flux and Fluidpages but in latest version I am in stuck.
The problem is probably that you use old class names (the ones with underscores). EXT:flux removed support of old class names in version 7.2.0 (see changelog), same for EXT:fluidpages.
To fix this, just replace your occurrence of Tx_Fluidpages_Controller_PageController with its new name: \FluidTYPO3\Fluidpages\Controller\PageController.
Of course you need to do the same thing for all classes in PHP as well as in all namespace declarations in your fluid templates.
Hey Ghanshaym,
5 >
5 = USER
5.userFunc = TYPO3\CMS\Extbase\Core\Bootstrap->run
5.extensionName = Fluidpages
5.vendorName = FluidTYPO3
5.pluginName = Page
10 >
May be helps
I'm using aldeed:autoform#5. I also want to use yogiben's autoform-file, but I had trouble getting that to work with autoform#5 so I've used a fork by abdj:autoform-file.
Now I want to use yogiben:admin. According to the discussion on github and the latest master (https://github.com/yogiben/meteor-admin/blob/master/package.js), yogiben:admin#1.1.0 uses aldeed:autoform#4.2.2 || 5.0.0.
So why do I get this error?
C:\Webdev\koolaid>meteor add yogiben:admin#1.1.0
=> Errors while adding packages:
While selecting package versions:
error: Conflict: Constraint aldeed:autoform#4.2.2 is not satisfied by aldeed:autoform 5.1.2.
Constraints on package "aldeed:autoform":
* aldeed:autoform#5.0.2 <- abdj:autoform-file 0.2.0
* aldeed:autoform#4.2.2 <- yogiben:admin 1.1.0
Looks to me like Meteor is somehow picking up the wrong version from github? BTW I'm using Meteor WindowsPREVIEW#0.3.0.
How do I get all these packages to play nice together?