In joomla 4 we are trying to avoid useless descruiptions on fields so you can just delete the _DESC strings

I tested it. The result was successful.

@impressionestudio please mark your test as successfully (how to: https://docs.joomla.org/Testing_Joomla!_patches#Recording_test_results)

@franz-wohlkoenig This PR has PHPCS errors, I've reviewed accordingly.

@impressionestudio please mark your test as successfully (how to: https://docs.joomla.org/Testing_Joomla!_patches#Recording_test_results)

I installed Joomla Patch Tester, applied the patch and then the page crashed with errors like:

• Unknown column 'a.featured_up' in 'field list' Unknown column 'a.featured_up' in 'where clause'
• Warning: Invalid argument supplied for foreach() in D:\Localhost\joomla4\components\com_content\Model\ArticlesModel.php on line 628
• Warning: Invalid argument supplied for foreach() in D:\Localhost\joomla4\modules\mod_articles_news\Helper\ArticlesNewsHelper.php on line 121

@impressionestudio apologies, i didn't thought that j4 can't be testet by patchtester – @richard67 can you please advise @impressionestudio?

@impressionestudio Patchtester has to be latest version 3.0.0-beta4.

After having applied the patch, you have to run the SQL statements in file administrator/components/com_admin/sql/updates/mysql/4.0.0-2019-08-20.sql or administrator/components/com_admin/sql/updates/postgresql/4.0.0-2019-08-20.sql in PhpMyAdmin or PhpPgAdmin, depending on which database you use. You have to replace the #__ with your database prefix (including the _ at the end).

Or if you are on a testing environment where you can do that, also apply the patch, then delete all tables from your database, remove configuration.php and makle a clean new installation.

See PR #25760 to see how to convert datetime to null value.

@richard67 thank you for the instructions and @franz-wohlkoenig for the answers.

I have installed the latest version 3.0.0-beta4.
But the problem is that I am not keen to Github. Also all these actions are too much for me.
I thought that testing would be easier. I wanted to help but it seems I am not able to do it and I don't want to tire you more.

@impressionestudio there's a plan to make patchtester ready fpr j4 – which also would help me to test :-).

"Joomla 4 has steps to compile assets (composer and npm) and the Patchtester component does not support that (yet). The idea is, that our CI system is compiling these assets and provides them via some API to the Patchtester component."

from https://volunteers.joomla.org/teams/automated-tests-working-group/reports/1080-meeting-report-2019-08-05

I will test this PR after @Quy 's suggestions will be implemented.

@Quy Is there something to be done with datetime null values in this PR? I see your comment above but can‘t see to what in the code it is related.

@franz-wohlkoenig The patch tester component never did run the schema updates (these are those sql scripts with date and version in their name) because if it would do that, it would also need a kind of undo script to revert the changes. This was always the case and is same for J3 and J4, so you always have to run the SQL manually. Only difference on J4 is that when a PR changes js or (s)css, you have to run npm install after applying the patch and then again after reverting it after test.

as already reported on the original pr for j3 here #18052 (review) and here #18052 (comment)

"featured_up" and "featured_down" fields should go into the "#__content_frontpage" table and not in the #__content table....

@richard67
In the sql files, remove NOT NULL DEFAULT '0000-00-00 00:00:00' and DEFAULT '1970-01-01 00:00:00' NOT NULL.

In the queries, use isNullDatetime.

Replace getNullDate() with null.

This is a nice feature! :)

RTC

I have tested this item ✅ successfully on 04dd1ea

I have tested this item ✅ successfully on 04dd1ea

Retested with the corrections and now the expired gone too. Works well :)

I have tested this item 🔴 unsuccessfully on 04dd1ea

After applying test patch tester following error appeared in articles view

@rmittl The reason is that this Pull Request contains SQL changes, and the Patchtester does not run those changes. You have to apply the SQL from the update sql script manually e.g. in PypMyAdmin.

See the following comments above:

#25979 (comment)
#25979 (comment)
#25979 (comment)

So please either set your test result back to "I have not tested this item" in the issue tracker, or test again in the right way, e.g. including manual execution of the SQL changes, and set then the appropriate test result in the tracker.

I have tested this item ✅ successfully on 04dd1ea

After apply the database changes, test runs successful.

Thanks for your patience on this over the last 2 years!

Thanks to everybody who helped to create this feature.
The only thing I have to wait for is the 4.0-Stable.
Then I can use this feature.

@wilsonge It seems there is an issue, #26829 , related to this PR. When checking the changed files here, I see stuff for handling featureed up and down times to the content table class, but during development of this PR, the 2 new columns have been moved to the #__content_frontpage. I can see there is something for reading from this table added to the core content table class, routine load(), but I see nothing for writing these columns back to #__content_frontpage. Instead of it I see the handling of the new columns in the check routine as if they would belong to the #__content table. Am I blind or do I understand something wrong? Please check and advise.

Today, I installed Joomla 4.0 beta 2.
There is stuill no option to use the scheduled featured articles.
Is it still nessesary to install that manually or should this be a part of this Beta 2 already?

@WoodyF4u The feature is already present. But it might be difficult to find. It's in Publishing tab. Maybe we should move these fields right under Featured field.

@SharkyKZ by that logic the start publishing dates should be moved as well

@SharkyKZ Thanks for pointing me to the Publishing tab.
I have tested it, but when I add a date and time for Start Featured and Finish Featured and click Save, both fields are empty.
So there is nothing saved and the article will not change in the featured state.
Is it possible that someone else can test it?

@brianteeman Yes, I think it is fine when the fields are in the Publishing tab.
But it must work and now it doesn't.

@WoodyF4u and I forgot that I discovered that the other day and raised an issue #29942

@WoodyF4u You first have to change the featured state to "Featured". Then you can set the start and end times (featured up and featured down). Then the times are respected when showing it on a featured page. Published up and down should work in the same way, by the way.

@riochard67 Thanks. That works!
In case you have to set Featured to ON first, it would be better when the options for Start Featured and Finish Featured will be vbelow the Featured switch.
Cause there is not any warning that tells the user to switch the Featured state first.

Yes, it's not very intuitive how it works. Could be really improved.

Please look at the first screenshpot of this PR. There you see the Featured ON-OFF switch.
When Featured is ON, the two extra fields for scheduling will be visible.
I think that will be the best place for the scheduling option of the Featured articles.

I am not a developer, but I hope someone can fix this for he next beta so we can test it again and maybe approve it for Joomla! 4.