I want to migrate an extension from Typo3 6.2 to Typo3 7.5 In Typo3 6.2 it works fine but in the Typo3 7.5 I get the following error:
Fatal error: Class 't3lib_pageSelect' not found in ...
It think that its not anymore supported, but when I'm right what I must use now?
I found a solution. In Typo3 7.x there is no support for the old classes anymore. Instead of t3lib_pageSelect I must use the new class with namespace: \TYPO3\CMS\Frontend\Page\PageRepository.
So for my case I want to read the Typo3 cache and know I must use
\TYPO3\CMS\Frontend\Page\PageRepository::getHash(md5Hash)
An in the case of save the cache I must use
\TYPO3\CMS\Frontend\Page\PageRepository::storeHash(md5Hash, data as a string,'NAME')
Thats the new one for the old class t3lib_pageSelect.
Related
I upgraded to Laravel 9 the other day, and now the ddd() helper is failing with the error Call to undefined function ddd(). I found this post on the Laracasts forum, but at time of writing there is only a single reply that states that the facade/ignition was replaced with spatie/laravel-ignition. I did not see anything in the documentation for the new package that mentions anything changing with ddd(), is there an additional configuration or something that is needed to re-enable ddd()?
Take a look at this https://github.com/facade/ignition/pull/201#event-2712168617
jasonvarga deleted the ddd branch 2 years ago
And you are right about not seeing any documentation about it in changelogs as well.
I heard this ddd() helper for the first time from you, so thax for that.
Please do check out the documentation of both of the packages.
Here facade / ignition and spatie / laravel-ignition
Both packages saying the same thing that
spatie/laravel-ignition works for Laravel 8 and 9 applications running
on PHP 8.0 and above. Looking for Ignition for Laravel 5.x, 6.x or 7.x
or old PHP versions? facade/ignition is still compatible.
In spatie/laravel-ignition version 1.2.0, ddd() was added back in! If you are not able to use ddd(), first check your composer.json file to make sure that your spatie/laravel-ignition version is 1.2.0 or above.
"require-dev": {
"spatie/laravel-ignition": "^1.2.3"
}
Just upgraded to Laravel 8 / Laravel Passport 10.1 and Locbucci JWT 4.1. I'm getting this error:
Target [Lcobucci\JWT\Parser] is not instantiable while building [Laravel\Passport\Http\Controllers\AccessTokenController]
This error makes sense since Parser is an interface, if I remove it from the AccessTokenController everything works as expected. As far as I can tell these packages should work together. Am I missing something here?
This is an error caused by the version of Laravel/passport, to solve this problem you must update to a new version of the package
execute this command, good luck
composer update laravel/passport
I upgraded TYPO3 from v9.5.31 to v10.4.20 Backend works well but the Frontend I have the following error
(1/1) Error
Class 'TYPO3\CMS\Extbase\Service\FlexFormService' not found
Does anyone know why TYPO3 does not recognize the class?
Thanks
I created a cakephp3 project with composer.
composer create-project --prefer-dist cakephp/app foobar
Then, I baked a helper with
bin/cake bake helper Progress
And copypasted the helper-example in the cakephp testing tutorial
Switching in the directory and performing phpunit says
PHP Fatal error: Class Cake\TestSuite\Fixture\FixtureInjector contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (PHPUnit_Framework_TestListener::addWarning) in /home/matthias/www/isbn.localhost/vendor/cakephp/cakephp/src/TestSuite/Fixture/FixtureInjector.php on line 173
PHP Stack trace:
PHP 1. {main}() /usr/bin/phpunit:0
PHP 2. PHPUnit_TextUI_Command::main() /usr/bin/phpunit:42
PHP 3. PHPUnit_TextUI_Command->run() /usr/share/php/PHPUnit/TextUI/Command.php:138
PHP 4. PHPUnit_TextUI_TestRunner->doRun() /usr/share/php/PHPUnit/TextUI/Command.php:186
PHP 5. PHPUnit_TextUI_TestRunner->handleConfiguration() /home/matthias/www/foobar/vendor/phpunit/phpunit/src/TextUI/TestRunner.php:145
PHP 6. require_once() /home/matthias/www/foobar/vendor/phpunit/phpunit/src/TextUI/TestRunner.php:771
Fatal error: Class Cake\TestSuite\Fixture\FixtureInjector contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (PHPUnit_Framework_TestListener::addWarning) in /home/matthias/www/foobar/vendor/cakephp/cakephp/src/TestSuite/Fixture/FixtureInjector.php on line 173
Call Stack:
0.0001 225152 1. {main}() /usr/bin/phpunit:0
0.0031 515440 2. PHPUnit_TextUI_Command::main() /usr/bin/phpunit:42
0.0031 516064 3. PHPUnit_TextUI_Command->run() /usr/share/php/PHPUnit/TextUI/Command.php:138
0.6384 6931096 4. PHPUnit_TextUI_TestRunner->doRun() /usr/share/php/PHPUnit/TextUI/Command.php:186
0.6384 6932312 5. PHPUnit_TextUI_TestRunner->handleConfiguration() /home/matthias/www/foobar/vendor/phpunit/phpunit/src/TextUI/TestRunner.php:145
0.6458 7043088 6. require_once('/home/matthias/www/foobar/vendor/cakephp/cakephp/src/TestSuite/Fixture/FixtureInjector.php') /home/matthias/www/foobar/vendor/phpunit/phpunit/src/TextUI/TestRunner.php:771
Doesn't matter if the global installed phpunit 4.2.6 or the latest version, installed with composer, is used. Where comes this from and how to can I fix this?
Thanks a lot!
Do not use a global PHPUnit installation when you have one that is local to your CakePHP installation, as you can see this will conflict, look at the stacktrace, you're starting in /usr/bin/phpunit, and then it jumps into /home/matthias/www/foobar/vendor/phpunit/phpunit/....
That being said, you seem to have installed the "wrong" PHPUnit version in your CakePHP app, the mentioned method addWarning was introduced with PHPUnit 5.1 alpha! The whole 5.x branch is not yet stable, and CakePHP is not yet compatible to it was just recently updated (not yet released) to support the changes, so for now you should install the stable 4.x branch instead, like
$ composer require --dev phpunit/phpunit:~4.0
Unfortunately the prefer-stable option (which is by default set to true in the CakePHP app skeletons composer.json) doesn't seem to help here, as Composer will choose ~5.1#dev when not specifying a version on your own (even if it's just *).
I think I have found an error with the current (snapshot) JSF 2.0 Myfaces 2.2 Version; I think I am not the only one having this issue:
when I want to create a link with the following style:
<h:link outcome="../../test" />
I get following error:
PM org.apache.myfaces.shared.renderkit.html.util.OutcomeTargetUtils
getOutcomeTargetHref Warning: Could not determine NavigationCase for
UIOutcomeTarget component {Component-Path : [Class:
javax.faces.component.UIViewRoot,ViewId: ..
When i try it with an old snapshop version (e.g. 2013-04-24), the links are created correctly, also when the outcome-site is in the same folder as the linking file.
anyone else having this problem or is there a way to fix this? I dont't want to switch back to the old version because it has much more serious problems than this link issue
It is a bug caused by the new JSF 2.2 spec, which enforces the use of ResourceHandler.createViewResource(...), and that code internally has a check to avoid ../ or ./ in the resourceName. It has been fixed on MYFACES-3839.