I can not see any SQL script changes in this PR to add the new plugin to the extensions table, neither in base.sql for new installation nor in a new update SQL script for updates.

i'll add...
but as it is , is testable, just discover

i'll add...
but as it is , is testable, just discover

Yes, it is testable in this state … but not mergeable ;-)

@alikon Regarding the update SQL scripts please look up in other update SQL scripts of the 4.2-dev branch how we add extensions, especially regarding the new INSERT IGNORE (MySQL) or ON CONFLICT DO NOTHING (PostgreSQL) which was introduced with PR #37156 , and also regarding columns which we do not use in update SQL scripts when inserting extensions.

Update: Silly me, that’s not needed here.

@alikon In addition, make sure to use the right “ordering” values in the I sent statements in the update SQL script. The values should be the same as in base.sql, but currently they are different in your PR (16 in the update SQL versus 5 in base.sql).

@richard67 frankly speaking i don't think... those are "strictly" needed.
anyway feel free to enhance it, this pr is open

p.s
for the ordering field what I should do ?

@richard67 frankly speaking i don't think... those are "strictly" needed. anyway feel free to enhance it, this pr is open

In my PR to which I referred to it is explained in detail why they were added, and it should not be a big thing for you to add that here, too. I am off my desk today and limited to mobile so I won’t be able to make a PR.

Update: Sorry for the confusion. I just see we don’t need that here in this case.

p.s for the ordering field what I should do ?

Use value 5 and not 16 in the update SQL script.

@richard67 frankly speaking i don't think... those are "strictly" needed. anyway feel free to enhance it, this pr is open

@alikon I just see I was wrong, we do not need INSERT IGNORE here, it was for other cases where we used IDs. Sorry for the confusion.

After site A has the PR applied and the New Task plugin enabled the site crashes - JROOT\plugins\task\webcronstart\services\provider.php:49
An error has occurred.
0 syntax error, unexpected end of file, expecting ";"
#Fields: datetime priority clientip category message
2022-05-25T06:35:59+00:00 CRITICAL 127.0.0.1 error Uncaught Throwable of type ParseError thrown with message "syntax error, unexpected end of file, expecting ";"". Stack trace: #0 [ROOT]\libraries\src\Extension\ExtensionManagerTrait.php(94): Joomla\CMS\Application\CMSApplication->loadExtension('Joomla\CMS\Exte...', 'webcronstart:ta...', '[ROOT]...')

Did the following to get back to the back end:

• removed blank link 49
• changed line 48 from } to };

  ---

  _{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37878.}

good spot fixed

I have tested this item ✅ successfully on f9a26af

Tested successfully on two 4.2.0-beta1-dev of 25 May. The PR#37868] - [4.1] Fix generate web cron key was applied first in site B. Added to the CLI command the following arguments: --id 1 --verbose and received a normal response to the command prompt. Without --id 1 received the message "No tasks due!"

I can't imagine a use case for a CMS where a remote web cron task should be executed on a regular basis. It is a CMS and not an administration panel. If it would be some kind of web hock feature for actions like an article save or user create, then ok. This plugin would be a perfect fit for the JED, but not for the core.

@alikon Currently api and system tests are failing with loging in to backend after having made a new installation. The screenshot made from the failed login shows a syntax error, unexpected ')', unfortunately not with file and line number: https://ci.joomla.org/artifacts/joomla/joomla-cms/4.2-dev/37878/system-tests/54571/InstallCest.configureJoomla.mysql.fail.png . I suggest you test that, make a new installation with your branch and then login to backend.

Just wondering, where is the difference to the "Get-Request" Task, which is already in the system?