-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFC - Remove testing data from distribution #10330
Comments
i agree, also another suggestion. sample data should not create things that are already created by joomla.sql. ex: the component menu. |
I'd rather see the sample data (hell, joomla.sql too) rewritten to not be static SQL dumps. But hey, a guy can dream... |
that would be even greater. |
+1 (especially as it's been on our roadmap for a while now: https://developer.joomla.org/cms/roadmap.html) |
Until someone actually does it words are great but don't change anything.
It's at least 6 months since PLT said someone said they were doing that. In
the meantime I can do this PR in ten minutes.
|
The PLT roadmap is only asking for the 10 minute PR. We can do the clever stuff another day. :-) |
I guess I misread the minutes of the meeting in Germany.
|
see: #10364 |
Set to "closed" on behalf of @zero-24 by The JTracker Application at issues.joomla.org/joomla-cms/10330 |
Closing as we have a PR here #10364 This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/10330. |
Actually, I did a PR once to make the sample data a postinstallation process using an admin module, a plugin per sample set and com_ajax (#7680). It was working with testing data, the others would still have to be done. |
There really is no good reason to include the testing sample data in the released version of joomla - it only has a purpose and use during the staging lifecylcle
It is fairly trivial to add the testing sample data to the list of files excluded from a build if people agree.
The text was updated successfully, but these errors were encountered: