Can't reproduce this issue with the sampledata plugin.
Admin sampledata module OK too.
PHP 7.2.5
MySQL 5.7.22

Installed multilang. Sampledata – works as expected.

System Information

@franz-wohlkoenig The title of this issue clearly tells that it is about testing sample data, not multi language sample data.

Testing sample data is only available when working on clone of the GitHub repo, not when working with a nightly build.

@ghazal Did you try with testing sample data?

I could not replicate this

@richard67 Yes, I tried the sampledata plugin, not the module.
On a today's cloned version, with composer and npm installed.

I've just tried it again and still have the error.

I did a clean install into an empty database with current 4.0-dev branch, with error reporting set to "Development" in global config server settings.

Current 4.0-dev means

• No remainders from previous tests
• Same external packages versions like on 4.0-dev, i.e. no composer update or so.

To make sure I have no remaonders from previous tests and no other unwanted files, I always do:

1. git checkout 4.0-dev
2. git remote update
3. git clean -d -x -f
4. git reset --hard upstream/4.0-dev
5. git push origin +4.0-dev
6. composer install
7. npm install

Then I cleared browser cache in order to be sure not to have any cached old js or css.

Then I make a new installation into empty database, without any modifications, i.e. no sample data, no additional languages.

Then I switch error reporting to "Development".

Then I go to the home dashboard and use the button marked with a red frame in the following screenshot to install testing sample data:

@ghazal @brianteeman Sure you did not have any remainders from previous tests, or any updates external packages from a previous run of "composer update"? Or maybe it is the error reporting set to development which changes something? Btw. any debug I had switched off in global config. Can you check again with these settings?

I can reproduce the issue where Step 3 is stuck with PHP notices and console JS error.

Thanks god someone can reproduce it. I started to believe that I have visions or something wrong is in my tobacco ;-)

i can reproduce too, it seems related to the fact that now the finder plugins are enabled by default
at least this is what i can read in the error log

@richard67 Don't worry about your tobacco.
I was finally able to reproduce the error with Error Reporting set to Development (and Finder plugins enabled).
Today's distrib.

Confirmed. It is still an issue.

confirmed still an issue as of 1hr ago pull

Its expected that an Issue isn't resolved if no Pull Request is created ;-)

This breaks in the 2/2 section for articles. It appears to be duplicate category issue.
step 4-6 completes properly.
pr #26235 does NOT fix the issue.

bit of debug info..

j4test.local.har.zip

@N6REJ
#26235 solves part of the issue here:

Steps 8 and 9 not done.

After another test, it sticks to step3... ⛔️

To get it to work, I disabled ALL finder related plugins, including Content - Smartsearch
It installs fine but with a weird display:

yup disabling the smart search content plugin is good enough to work around for now (obviously not the long term solution). I've done some improved error handling in #26385 on the plane home last night so it now doesn't hang on the spinner but shows an error (doesn't actually solve the issue tho)

Maybe we could disable the plugin in step1 and re-enable it in step9?

My guess is that if you manually create a category. then manually create an article and put it in the new category you're going to get the same error.

Will be solved by PR #26392 together with PR #27008 .