@chmst There are still code style issues, e.g. unused imports (use statements) to be removed. Unfortunately many of them are outside of what can be done with a code change suggestion on GitHub, so I can't help with suggestions here. See the log here: https://ci.joomla.org/joomla/joomla-cms/78000/1/7 . If necessary I can help tomorrow after work. Would be good to get the phpcs fixed so the system tests will be started in Drone.

• @deprecated 6.0 will be removed in 7.0

I thought the policy was deprecated in x and removed in x+2 ?

@chmst Does this PR replace PR #35228 ? If yes, shall we close the latter?

And could you check the conflicting files? I think the conflicts come from PRs #43323 and #43512 , but I don't have the time now to check in detail.

@chmst I've allowed myself to fix the conflicts. Please check the result.

1. Full prebuilt package installation.
2. Blog sample data installation failed (red There is an error in a sample data plugin. Response is invalid.)
3. Saving new Article:
   Article not saved.

The PR has the support of the Enhancement Development team. This is still something the team wants to talk to the maintenance team and the release managers for 6.0 about: we do think it would make future changes to the core simpler if this PR was merged early on and tested throughout the 6.0 pre-release cycle.

@obuisard thats what is always said and the fixes never happen. Once it is merged then the people behind it move on to other things.

Adding the following code in the DisplayController will prevent old URLs to fail with 500 error but be redirected to the 'articles' view instead.

if ($view == 'featured') {
    $this->setRedirect(Route::_('index.php?option=com_content&view=articles&featured=1', false));
    return false;
}

Just started a new Installation. I think that the first select "All" is not self-explaining.

Would "featured / unfeatured " be better? The text is rather long especially in other languages.
or " - select featured - " ?

@chmst Could you check the conflict in file „administrator/components/com_content/tmpl/featured/default.php“? I think it comes from #44053 .

Just started a new Installation. I think that the first select "All" is not self-explaining.
Would "featured / unfeatured " be better? The text is rather long especially in other languages. or " - select featured - " ?

In my opinion, " - select featured - ", "featured", "unfeatured" sounds better.

The filter needs to be changed. It cannot be featured / unfeatured but also needs a value "all".

-- select featured --
all
featured
unfeatured

Created a new site and added sample data.
Unfeatured articles leaving only 1 of the 11 articles featured

Content > Featured Articles displayed the 1 article that was featured. The item count showed 1-11/11 items, should this be 1-1/1 items since only 1 article is featured?

Content > Articles displayed only the featured article with the selector set at Featured Articles. Should the selector be Select Featured?

With sample data, do you mean testing sample data (the old plugin for developers) or blog sample data? When I install blog sample data, every count is correct for me.

Hi @chmst,

Other than the double highlighting bug mentioned in #35228, I was able to test successfully...

( noticed after the fact that it couldn't be tested on 5.2.3 and the update 5.2.3 ---> 6.0.0 alpha 1 created a *@%#! so then I wiped everything and installed Joomla_6.0.0-alpha1-dev+pr.43907-Development-Full_Package.zip. ).

I have tested this item ✅ successfully on fab5f02

Aside from my comment on the PR, I was able to test it successfully.

Thank you for the hard work.

Hello @SharkyKZ, any reason for the thumb down?

With new changes, the filter goes back into the normal filter toolbar, so that user do not see a differnce against J5, we do not need make changes in user documentation.

At the moment we have one flaw - the featured link in the admin module ist not marked as active.

Everything works flawlessly and I like this change. Great thanks Christiane @chmst.

I do have one comment, which is a behavior I have noticed:

• when you filter articles by a category, for instance 'blog', then go somewhere else, for instance in the 'fields' page and then you go back to the articles view, the filter 'blog' is still selected (and everything works that way for categories...).
• when you filter articles by category 'blog', then go to 'featured articles' view, the category 'blog' is no longer selected.

This is reproducing the behavior we had before this PR: when going to the 'featured articles' view, we had a featured articles view you could filter independently from the articles view. But now that the views are merged, we cannot have distinct filtering any longer.

I do think that for consistency with the other pages, we should retain filters while switching between 'articles' and 'featured articles' views.

I have tested this again thoroughly and agree with Olivier, aside from the oddity he describes, it works but it would b great if that oddity was solved.

I have tested this item ✅ successfully on fab5f02

Is this documented?

Hi, @chmst, Thank you for persisting and getting to this point.
Would you mind providing some documentation for the manual.joomla.org? I am sure Anja will be wanting to get an article about it for the magazine as well

I am happy that it is merged - thanks to all who helped with that. I am pretty sure that there will come some more issues.

@laoneo will do documentation in the manual for deprecations. There is no change in the views and users should not see any difference.

@softforge - will see what I can do