?
avatar Scrabble96
Scrabble96
3 Jan 2019

Steps to reproduce the issue

At the top of this page, click on the <> Code tab, switch the brand to 4.0-dev.

Expected result

A top-level folder named 'Media'.

Actual result

No folder named 'Media'

System information (as much as possible)

I am using a Alpha 7dev site on CloudAccess.net and on the front end am using Firefox inspector to try to find the location of system messages. According to the inspector the one that tells you that you can't delete a primary template style is in, or initiated by, media/vendor/joomla-custom-elements/js/joomla.alert.min.js Please see screen shot.

image

Additional comments

avatar Scrabble96 Scrabble96 - open - 3 Jan 2019
avatar joomla-cms-bot joomla-cms-bot - change - 3 Jan 2019
Labels Added: ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 3 Jan 2019
avatar Bakual
Bakual - comment - 3 Jan 2019

What Brian wanted to say is that the media folder will be populated by the build scripts (composer and npm) dynamically. The released package will contain them as usual, but you will not find it in the git repo. The link Brian posted explains how to use the build scripts yourself if you wish to build your own package based on Git.

Closing this issue as expected behavior.

avatar Bakual Bakual - change - 3 Jan 2019
Status New Closed
Closed_Date 0000-00-00 00:00:00 2019-01-03 18:35:04
Closed_By Bakual
avatar Bakual Bakual - close - 3 Jan 2019
avatar Scrabble96
Scrabble96 - comment - 3 Jan 2019

Thank you, @Bakual

Add a Comment

Login with GitHub to post a comment