Closed oimken closed 8 years ago
Hello, thanks for reporting.
Did some clean-up, and the jquery path has indeed changed. I've fixed that now.
The reason there are 3 vendor folders (assets/js/vendor
, assets/css/vendor
and assets/vendor
) is because the first 2 are for vendor scripts being pulled in manually, and the latter is for vendor assets pulled in from bower.
The ressources/vendor
folder was indeed from before bower, it has been removed.
I tested removing the published folder for AdminLTE, public/themes/adminlte
, and publishing it again, works now. :smile:
still got 404 for some js and css.
re-produce:
public/themes/adminlte
php artisan stylist:publish
http://asgardcms.loc/themes/adminlte/css/vendor/datatables/dataTables.bootstrap.css
http://asgardcms.loc/themes/adminlte/css/vendor/iCheck/flat/blue.css
http://asgardcms.loc/themes/adminlte/vendor/jquery/dist/jquery.min.js
http://asgardcms.loc/themes/adminlte/js/vendor/datatables/jquery.dataTables.js
http://asgardcms.loc/themes/adminlte/js/vendor/datatables/dataTables.bootstrap.js
I can't reproduce this here. I delete my published adminlte theme, then re-published, everything working fine.
Please update to the latest versions of modules to remove the iCheck error. And run bower update
in the adminlte theme before republishing.
Oh I see, I was able to re-produce on the platform installation.
It is due to the update Core module, core
configuration file. config/asgard.core.core.php
.
You can copy the contents of the one in Modules/Core/Config/core.php
to the published one.
thanks you for your quick reply! Update Platform and asgard.core.core.php
fixed the most path error,
I did run bower update
in Themes/Adminlte
,
and stylist:publish again. still got iCheck path error:
http://asgardcms.loc/themes/adminlte/css/vendor/iCheck/flat/blue.css
in fact that css lies in public/themes/adminlte/vendor/iCheck/skins/flat/blue.css
if you have that on a custom module, you need to remove the iCheck include in the file itself. That has now been included by default on every view.
Example commit: https://github.com/AsgardCms/Blog/commit/52efa4ca1b1e975e44e3c3218ab25d589507ff73
I just ran into a similar issue after upgrading core. Would it be possible to add a note about copying the contents of Modules/Core/Config/core.php
to config/asgard.core.core.php
to the upgrade guide for core
I will thanks.
when I delete
/public/assets/themes/adminlte
and runbower update
,php artisan stylist:publish
, back-end will mess up, some css and js are missing.edit
elixir.json
could make back-end works gain。
And there is lots of duplicate files in
Themes/Adminlte
, such asThemes/Adminlte/assets/js/vendor
Themes/Adminlte/assets/vendor
Themes/Adminlte/resources/js/vendor
.....