nitsan-technologies / ns_ext_compatibility Goto Github PK

• Is there any feasibility to integrate "extensions scanner https://github.com/tuurlijk/typo3scan" feature into this extension?
• If yes, we should integrate it with whatever features like click on "scan action", the open modal box which displays all the deprecated and breaking code.
• It will be a great feature which will useful for the developer as 'all in one' solution/package.

• During the T3DD18, the suggestion was to check if a particular extension has been developed with "PI" based old-school method?
• Let's add one more column for the same

Hey there - i have a problem with the class SendExtensionsReportTask

every time the task "TYPO3 Extensions Compatibility Report via Email Notification (ns_ext_compatibility)" are executed via CLI I get the following Error Message :

Core: Exception handler (CLI): Uncaught TYPO3 Exception: Class 'TYPO3\CMS\fluid\View\StandaloneView' not found | Error thrown in file /path/to/vendor/typo3/cms/typo3/sysext/core/Classes/Utility/GeneralUtility.php in line 3956

With manuell execution every things works fine.
Is possible to change the use column from :

use TYPO3\CMS\fluid\View\StandaloneView;

to

use TYPO3\CMS\Fluid\View\StandaloneView;

Used Version : 1.1.1
TYPO3 8.7.19

Can some confirm this behavior or give me a hint how to fix it?

Best regards

Introduce a new column to showcase the latest version sourced from GitHub releases.
Retrieve the most recent extension version from both GitHub releases and Packagist.

Hi,

I think the extension key in composer.json should be renamed to ns_ext_compatibility.

First, thanks for making all those Extensions!

I think there's a third state missing for extensions: Unknow (?)

My understanding is that homemade (not on TER) extensions are marked with the RED X but in fact it's "unknown" if it's compatible for a higher version of TYPO3.

First run and it throws js error: Uncaught Error: Script error for "datatables", needed by: TYPO3/CMS/NsExtCompatibility/Main
and opens empty modal after clicking on extension.

T3: 10.4.6
ext: 5.0.0

I receive the following warning in the typo3 Backend:

PHP Runtime Deprecation Notice
Core: Error handler (BE): PHP Runtime Deprecation Notice: Array and string offset access syntax with curly braces is deprecated in /typo3conf/ext/ns_ext_compatibility/Classes/PHPExcel-1.8/PHPExcel/Shared/String.php line 541

Only for this file for several lines: 526, 527, 538, 539, 541, 542

Hey!

If a particular server does not allow some PHP functions like shell_exec(), there should be two options:

• Is there any alternative solution to achieve that particular features? If yes, then we should set such setup as an alternative.

• Atleast, Let's set 'Warning' message instead of the TYPO3 error (see attached).

Cheers!

If TYPO3 is configured to use PHP 7.2 (7.2.10) the backend module complains about a missing setting für "max_execution_time" although directive is set in php.ini. There is no error if used with PHP 7.1 /7.1.22).

Hii,
While I have check this extension in typo3 8, I found that total installed extension is count twice!!
Please remove line 748 to752 in file ns_ext_compatibility/blob/master/Classes/Controller/nsextcompatibilityController.php

Under TYPO3 Version 6.1.7 the following exception is thrown:

Argument "loadJQuery" was not registered.

I traced this back to the "Default.html" Layout file which has the argument loadJQuery using the viewhelper f:be.container.

I guess the argument isn't registered at fluid when having the above TYPO3 version.

In Resources/Private/Partials/Common/Header.html, the option value for TYPO3 11.x is 10.x. This prevents the module from checking the typo3 v11 compatibility.

We want to use the great email report to send automatic notifications to customers. I think some points could be optimized:

• Show installed TYPO3 Version and latest TYPO3 Version (sth. like "Installed Version 8.7.22 / Latest Version 8.7.26 / no-security updates")
• Show on updates for extensions, if these are security relevant

f:be.container does not have the following arguments in TYPO3 6.2:

• jQueryNamespace
• includeRequireJsModules

If you remove these arguments, you will see the module content, but due to the missing JS not all things do work properly.

Hello,
I started the check on an 8.x TYPO3. The result from one of the checked extension is:

Comp. 8.x => Yes
Comp. 9.x => No

The Current Version Dependency of this extension is:
php => '7.0.0-0.0.0' typo3 => '8.7.0-9.5.99'

Although the extension clearly states itself as compatible with 9.5.x, the result of the nx_ext_compatibility check is "not compatible". Why?

• From T3DD18 event, we get continues feedback to add this feature
• Let's add one column which shows, the particular extension is used or not, which is one of the very important features
• Technically, let's try to find the entries from tt_content (of the plugin) + look at include static + check for custom backend module + check schedule entry and so on.,

Since Typo3 11 was finally released in October 2021 (https://typo3.org/article/typo3-v11-lts-warp-speed ) it woulb be great to check compatibility with your extension.

Currently (ns_ext_compatibility 5.0.3) it seems not to support this.

Currently there is a warning alert at top of the backend module when the last extension list update is some time ago.
If you are in composer mode you can't update the extension list in Extension Manager, so the warning should not be displayed.