While sample data installation will be removed from the installer, language installation (and with that setting up a multilingual site) afaik will stay. I'm not aware of anyone saying that part should be removed.

Installing blog sampledata and multilingual "sampledata" should both be possible.
If not, that is a bug that should be fixed. Did you get an error message while trying to do that?

As for the order, that would be an easy change. How they appear is based on how the plugins are ordered in the manager. So changing the ordering column values in the installation SQL files would be enough.

I wouldn't add a close/hide button to the module. Simply because other modules don't have that as well. The module is a regular module and can be disabled in the module manager if someone wants to hide it. You cna also hide single entries because those are regular plugins (from the "sampeldata" group).
Keep in mind that 3rd party extensions could offer their own sampledata options in that module.

Thanks Bakuai

language installation (and with that setting up a multilingual site) afaik will stay.

From the first steps installation ?

As an optional step in the installer, like it is today in J3.

That is great news Bakuai.

The ability to install in a few click a fully functional multilingual site is one of the great force that, to my knowledge other CMS cannot do.

More, at the marketing level, this make Joomla a more “international” solution, compare to it’s competitor.

I even propose a design and functionality at #22907

If I understand well, that is not what @Bakual wrote.
He said that installing languages is (or will be, if broken atm) still possible in 4.0 but that it is not considered to add at Installation time the sample data for basic multilingual site as we do in J3.
One still has to do this in CPanel through the module and plugin.

I personally agree with you that it SHOULD still be possible at install time.

@infograf768

I personally agree with you that it SHOULD still be possible at install time.
Of course!
I understand that installing the Blog Sample Data become a choice in the administration, but not including the possibility to install another language and/or Joomla complete multi language system in the installation is an error for 2 main reasons;

1. International administrators will surely appreciate their brand new site administration in their language without any other steps (that maybe be complex for them (think about Newbie to Joomla)

**2.**This is a MAJOR plus for the Joomla platform ( for it’s world domination... :) )
To my knowledge, no other CMS can do that.

Go to #22907
I propose my view of the Joomla installation process (and multilingual installation)

Kind of sad, after trying to reach to revive the Joomla archived team “User Experience Team (JUX)” or join and participate to any team in charge of the ergonomic development, design and UX for Joomla 4. No response ?????

Joomla 4 steaming along with an interface that is really far from optimal and people wanting to help have no place to donate their time.

This is a complete revision of the interface, not porting attention here can be catastrophic. So far I’m far from impress in what I see...

@Chacapamac as wrote on 2 other, same comments: https://volunteers.joomla.org/teams/j4-backend-template-working-group

Re-implementing the possibility of installing a basic multilingual site at Joomla installation time does not depend imho on the back-end template working group.
That decision has to be (or not) taken by the Production Department Team.
Until now, this has been refused and I had to create a specific multilang sampledata plugin in 4.0 to cope with this.

@Webdongle @rdeutz
Can this be reconsidered?

@infograf768 I do not use multilanguage nor do I have any say in the development of Joomla. But if you are asking me then I say your word on multilanguage should be the final word on the subject. And all others should do as you request.

oops, wanted to ping @wilsonge but w got you. 😈

Re-implementing the possibility of installing a basic multilingual site at Joomla installation time does not depend imho on the back-end template working group.
That decision has to be (or not) taken by the Production Department Team.
Until now, this has been refused and I had to create a specific multilane sampledata plugin in 4.0 to cope with this.

Hopefully the light is at the end of the tunnel and the Production Department Team will implement it in the install process. It will be a big plus for Joomla.

Re-implementing the possibility of installing a basic multilingual site at Joomla installation time does not depend imho on the back-end template working group.
That decision has to be (or not) taken by the Production Department Team.
Until now, this has been refused and I had to create a specific multilang sampledata plugin in 4.0 to cope with this.

To be fair here, I don't think it was ever suggested that the multilanguage section be removed in full from the install app (and if it was I agree that's a bad idea, BUT, it must always be in the back of everyone's minds that a lot of Joomla installs happen without seeing Joomla's installer through platforms like Softaculous so some features may never be seen by users unless those vendors are exposing them). Having a multilanguage sample data plugin that follows the plugin driven approach that all sample data is moving to is a good idea and should be implemented regardless of where the "do you want to set up a multilanguage website" steps live.

BUT, it must always be in the back of everyone's minds that a lot of Joomla installs happen without seeing Joomla's installer through platforms like Softaculous

Didn’t think at this...
– Keep Multilingual as an install OPTION

• Keep Multilingual as a backend administration OPTION

The only actual caveat in the administration is the fact that no sample data should be installed before Installing the Multilingual system.
The way it is now, be sure you will have lot of people actually make the mistake to install the Blog sample data before the Multilingual option

Suggestion, something like;
• Original
Sample data which will set up a multilingual site.
Before launching, make sure you have at least 2 languages installed with their Content Languages and that no sample data has been installed.

• it should say, to be clear
Set up a multilingual site (with Multilingual Sample data)
IMPORTANT - If needed, install BEFORE the Blog sample data
Before launching, make sure you have at least 2 languages installed with their Content Languages and that no Blog sample data has been installed.

• Also the multi language option should be first (on top of the Blog sample data)

That conflict only exists between the blog and multilingual sample data sets, and even then there's no confirmation that it is actually an issue (at worst you've got both sets installed and the blog data isn't set up as multilingual content, which is not a bug because even if you have set up a site to be multilanguage that does not mean every piece of content on it must be internationalized). Any text strings should not imply that you can only install one sample data set, because it is entirely possible multiple sets could be installed without any issue at all. Also consider that as a plugin based system, the core supported blog and multilingual sample data sets are not the only options available (https://github.com/joomla-extensions/testing-sample-data has the testing data set and extension vendors can create their own plugins).

@Chacapamac If there is indeed a conflict between those two sample data sets, please open a new issue for it with the details. I'm sure it can be solved.

Before launching, make sure you have at least 2 languages installed with their Content Languages and that no sample data has been installed.

The multilingual sample data can't be installed if there aren't two languages set up already. It will show you an error message.
I wrote a PR which actually hides the option if the languages aren't present: #20749
I'm not convinced this is needed but the code is there if it's deemed necessary 😄

If there is indeed a conflict between those two sample data sets, please open a new issue for it with the details. I'm sure it can be solved.

Does the install sample data screen not say that installing without sample data is to be chosen for multi language sites ?

Does the install sample data screen not say that installing without sample data is to be chosen for multi language sites ?

For 3.x and sample data driven by SQL files, yes you should avoid installing sample data. With either 3.x or 4.x and sample data plugins, this suggestion (restriction?) should not exist.

I wrote a PR which actually hides the option if the languages aren't present: #20749
I'm not convinced this is needed but the code is there if it's deemed necessary 😄

Hiding the option also hides the feature. Not good imho.

With either 3.x or 4.x and sample data plugins, this suggestion (restriction?) should not exist.

It may not be a big issue with blog sample data plugin but, with the present code for 4.x it may be for the multilang sample data, depending on what was already created.
If you have already installed testing sample data then the sampledata module is NOT displayed in CP. Let's enable it, install a language and run it. (BTW, we have a bug for the Position field for admin modules).
Result: Yes, home pages are set as should, but the site is a mess as what was installed with testing sample data is set to ALL languages (except Parks which should be modified I guess).
Very confusing for the user.

As said, open a new issue for conflicts. For the testing sample data there is even an own repo for it.

Very confusing for the user.

Yeah, the UX of it all isn't very good my any means. But from a technical perspective, my point is there shouldn't be a thinking that only one sample data set can ever be installed on a site and after that you're on your own.

'off the wall' thought
Could various people write sample data for various languages. Yes that would take time but if a collection of sample data (for various languages) was to be built up ... could they then be incorporated (during install) in a drop down menu ?

Sample data for different languages doesn't need all the pages translated ... just a few pages with menus/menu items as an example of how a mulit language site can be set up.

@Webdongle
We have a way to install a basic multilang site without it being a tutorial (code is still present in installation and just need to be adapted to j4).
Going further than that is asking a bit too much imho.

@Webdongle The blog sample data by itself is multilingual aware. It will install the items with the currently active language. If you afterwards switch language, you can install it again for that language. All strings used by the plugin are regular language files which are translated the same way the rest of core is.

Set to "closed" on behalf of @jwaisner by The JTracker Application at issues.joomla.org/joomla-cms/23028

Please see #24481

this is nothing to do with #24481