Typo3 9.5.18 / t3extblog 5.1.0 : Error messages

Question

Typo3 9.5.18 / t3extblog 5.1.0 : Error messages

annaemde opened this issue 4 years ago · comments

Hi,

I tried to install t3extblog 5.1.0 on several projects with T3 9.5.18 and I get the following error message in the Upgrade Wizard - Ajax error:

"Deprecated: Referencing the navigation component ID "typo3-pagetree" 
will be removed in TYPO3 v10.0.Use "TYPO3/CMS/Backend/PageTree/PageTreeElement" instead. 
Module key: web-T3extblogTxT3extblog in 
/kunden/201892_70794/rp-hosting/7476/8477/typo3cms/typo3_src-9.5.14/typo3/sysext/core/Classes/Utility/ExtensionManagementUtility.php
 on line 874
{"success":true,"needsUpdate":false,"adds":[]}

Regards
Anna

Felix Nagel · Answer 1 · Thu Jun 18 2020 17:04:07 GMT+0800 (China Standard Time)

Looks like an bad error reporting configuration to me. Deprecation notices should not cause fatal errors.

Anna Emde · Answer 2 · Thu Jun 18 2020 22:50:10 GMT+0800 (China Standard Time)

Thanks for the hint. After switching from "Debug" to "Live" I don't get these messages any longer, so I'll try to find a custom configuration where I do not get deprecation warnings in my development environment :-)

Felix Nagel · Answer 3 · Fri Jun 19 2020 16:12:26 GMT+0800 (China Standard Time)

This should not happen with a fresh TYPO3 installation. Did you upgrade? Probably some old, legacy configuration for your error / log reporting.

Best would be to enable deprecation logs, but only for DEV environment and written to files.

Closing this here, as it's not really related to this extension.

Anna Emde · Answer 4 · Mon Jun 22 2020 21:46:11 GMT+0800 (China Standard Time)

Hi Felix, yes, I made an upgrade of a Typo3 8.7 installation which is actually almost 10 years old. I've learned a lot about error reporting in the meantime ;-) Thanks for closing the issue. Actually you may also delete it, if you can do so. Regards Anna Am 19.06.2020 um 10:12 schrieb Felix Nagel:

…

This should not happen with a fresh TYPO3 installation. Did you upgrade? Probably some old, legacy configuration for your error / log reporting. Best would be to enable deprecation logs, but only for DEV environment and written to files. Closing this here, as it's not really related to this extension. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#231 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHLWFIDNJVIFWFQJIQGDBSTRXMMXPANCNFSM4OBLXMHQ>.