Metronic 9.2.0
Hi, I am new to front end development.
Now i am using symfony framework.
i had purchase the composer package over here :
https://keenthemes.com/metronic/tailwind/docs/composer
and also metronic theme at themeforest.
now i wanted to use demo2 as my template. i follow exactly above document. After generate asset file, i copy all the assets file into my project directory "my_project/assets"
i try to run php bin/console asset-map:compile, here come the error.
Unable to find asset "images/layers.png" referenced in "Desktop/tailwind/myproject/assets/vendors/leaflet/leaflet.bundle.css". The file "Desktop/tailwind/myproject/assets/vendors/leaflet/images/layers.png" does not exist.
i try to search for the image at metronic-tailwind-html-9.2.0/dist/assets/vendors/leaflet/images/layers.png, i cant find the file
anyone can teach me how to solve this issue?
beside that, do i need to copy over package.lock.json, postcss.config.js, prettier.config.js, webpack.vendors,js from metronic-tailwind-html-9.2.0 to my myproject and run npm install to install all the dependency?
Replies (3)
Hi
In /metronic-tailwind-html/webpack.vendors.js. It seems missing leaflet images.
leaflet: [
{
src: ["node_modules/leaflet/dist/leaflet.css"],
dist: "/vendors/leaflet/leaflet.bundle.css",
bundle: true,
},
{
src: [
"node_modules/leaflet/dist/leaflet.js",
"node_modules/esri-leaflet/dist/esri-leaflet.js",
"node_modules/esri-leaflet-geocoder/dist/esri-leaflet-geocoder.js",
],
dist: "/vendors/leaflet/leaflet.bundle.js",
bundle: true,
},
{
src: ["node_modules/leaflet/dist/images"],
dist: "/vendors/leaflet/images",
},
],As workaround, could you please copy images from node_modules/leaflet/dist/images to your path? Desktop/tailwind/myproject/assets/vendors/leaflet/images
Thanks
thank for your help.
now i facing new problem. when i refresh the page, datatable search input will become undefined. this problem also happen when i click the thead for sorting
Thanks for reporting the issue.
The problem is coming from the KtUI component library side, we’ve identified the cause and will fix the bug in an upcoming update.
Thanks
