341 comments found.
Hi, I can’t find any documentation on the theme? does it exist? Right now my question is – Can the menu shown over the content, rather than move it to the right? Thanks for the answer.
Hi,
You may reach the docs with the Docs link on the main menu at our demo. You may also find an index.html file in documentation folder of the downloaded zip file which redirects to docs. You may reach it with this link: https://piaf-vue-docs.coloredstrategies.com
You may set the menu for “sub-hidden” mode by changing “defaultMenuType” to “menu-sub-hidden” in src/constants/config.js file.
All the best.
thanks, found) all the best
It seems to me that the documentation is not updated along with the Piaf – Vue Admin Template. The docs still refers to v 4.0.0, and so does the changelog in the docs.
Even though I have requested an e-mail when updates are released in the preferences at envatomarket / themeforest, I have not received such on Piaf.
It was just by luck I discovered the changelog all the way down at the bottom of the product page at envatomarket.
Please, keep the info up to date, and notify by e-mail about new updates.
Hi,
You are right about the documentation and sorry about that. We are always behind 2-3 versions and there is not any explanation other than our negligence. We will try to take better care of it.
As for the update e-mails, Envato provides a choice to send them and we go with the silent option. The main reason for it, we also buy stuff from Envato and update emails turn into spam after 50+ items. There is the option to turn them off and we turned them off and now we can not get any updates that we might be interested. So the system is not working very well. As a second reason, our updates are not quite easy to implement to an ongoing project. Users make changes in the project by the nature of the template and also we do. We don’t want to put any developer in a position that they are ordered by a superior or felt the need to update the template before they carry on their project.
This answer turned out longer than I anticipated, so thanks for your patience:)
All the best.
Hi
Is there any UI to present the stepper, I want to show the product delivery status
Thanks
Hi,
Unfortunately there is not any implementation for it.
Hello,
I would like to make new dir under views and change “app” folder, however I could not add new directory file or changing app folder. I was trying to looking for .babelrc file and webpack file, but there are no such files (I used VC and sublime to check hidden file).
Could you tell how to make new dir? because after i add or modified some part on router.js, still error. However if I just simply add new .vue files and add the route under “app” dir, I could modify it.
Thank you so much
Best regards,
Hi,
First of all, there are no hidden files that might effect how the project works. There are only editor config and gitignore files which are hidden. The project is created with Vue CLI so most of the build and compile process is encapsulated in vue.config.js.
Please check this image of router.js file: https://i.ibb.co/BwjvBWm/piaf-new-route.jpg
I have added a folder new-route and inside it added a file new-page. I have changed empty route(”/”) which is the starting route of the project to show /new-route/new-page. This is the way to change starting route. index.vue file in new-route directory is copy of app/index.vue to get layout structure and new-page.vue file is a copy of blank-page.
I have also modified earlier empty route to make it accesible with ”/app” path and prevent the conflict when having two empty routes.
Finally added a ”/” to path: “app/dashboards” path: “app/pages” and so on to make them accesible. (I just noticed that highlighting was wrong with this, sorry about it).
This is basicly it. If you are still having problems and not comfortable working with routes, I may suggest you to look into the Piaf-Vue-Start project. It has very few pages and routes that might be easier to play around and experiment.
You may also check the Lifecycle page on our docs if you haven’t.
https://piaf-vue-docs.coloredstrategies.com/docs/codebase/lifecycleLet us know if this does not help at all.
All the best.
Thank you very much 
May I ask you more? I would like to check where which code should I edit to make “social page” to be on top” and the content become “centered” in full screen. I deploy an example here https://sarisaya-jp.web.app/home/introduction
Thank you and sorry for bothering you guys
best regards
Hi,
It looks like you have not included topnav and sidebar to the page so I guess it’s intentional.
The template does not provide a way to make contents centered so you will need to work on sass part and do some adjustments.
Please locate “src/assets/css/sass/_piaf.style.scss” file and look for the part commented with ”/* 15.Main*/”. Spacing is done via some variables as you may notice in main part and they are located at the very start of the same file. Adjusting these variables should solve the issue.
As an alternative way to handle horizontal spacing, you may use “menu-hidden” as a “defaultMenuType” in “src/constants/config.js” file. This will remove the space on the left which is reserved for menu.
Hi,
Thank you very much for your help ☺️
You are welcome
Ps: If you are happy with template, consider giving it a rating please. https://themeforest.net/downloads
Hi,
I just tried to change defaultMenuType from menu-default to menu-hidden. The results as expected. I could hide the menu nav on large view. However, when i change the to sm size, I could not click hamburger icon thus the menu cannot be viewed. And also I would like to try to menu-hidden on some pages. How could I customised that since defaultMenuType is located at config.js.
Thank you very much
Hi,
You are right about it and we have found a small problem which is causing this behaviour. Changing “isCurrentMenuHasSubItem” function content in “src > containers > Sidebar.vue” file with the one below should fix the problem.
isCurrentMenuHasSubItem() {
const menuItem = this.menuItems.find(
x => x.id === this.selectedParentMenu
);
const isCurrentMenuHasSubItem =
menuItem && menuItem.subs && menuItem.subs.length > 0 ? true : false;
if (isCurrentMenuHasSubItem != this.selectedMenuHasSubItems) {
if (!isCurrentMenuHasSubItem) {
this.changeSideMenuStatus({
step: 0,
classNames: this.menuType,
selectedMenuHasSubItems: false
});
}else{
this.changeSideMenuStatus({
step: 0,
classNames: this.menuType,
selectedMenuHasSubItems: true
});
}
}
return isCurrentMenuHasSubItem;
},
I must admit that changing menu type for an individual page is not very straight forward. You may see the usage at “src/views/app/menu/Types.vue” file with a function “changeDefaultMenuType”. You may need to create a helper file with the contents of the method to call on your view’s mounted event.
Let us know if this does not solve the issue for you.
Hi guys,
Thank you very much. I tried it on and it was great. However, in starter template, when I “single” page clicked, the menu bar could not be open anymore.
And also, how to make something like, when in config.js/menu-sub-hidden is used, then at first click “piaf” will open sub-menu and at second click will close the sub-menu.
Thank you
Hi,
You are right about the problem and sorry for it. We have made the fix and implementing it requires adjustments in multiple files. If you don’t want to implement it yourself, update will be published in a few days. Here is the fix.
- Fix 1
“handleDocumentClick()” function in “src/containers/Sidebar.vue” is changed.
handleDocumentClick(e) {
this.viewingParentMenu = "";
this.selectMenu();
this.toggle();
},
Again in “src/containers/Sidebar.vue” file below change is made.
// This one is changed
<div class="sidebar">
// To this one
<div class="sidebar">{}">
(Adding below closing div tags are irrelevant)
</div></div>
- Fix 3
isMenuOver is removed from states.
Added “stop” to below lines at “src/containers/TopNav.vue”
// This one is changed
@click.prevent="changeSideMenuStatus...
@click.prevent="changeSideMenuForMobile...
// To this one
@click.prevent.stop="changeSideMenuStatus...
@click.prevent.stop="changeSideMenuForMobile...
- Fix 5
A typo fixed in “src/store/modules/menu.js”
//This one is changed
state.menuClickCount = 0
//To this one
state.clickCount = 0
Our answer looks bugged since it contained some html tags. You may see the answer better at your email or below screenshot.
https://ibb.co/7nctJyCHi.I dont know use vue js and I buying Pief theme.I want to use dore theme because ı know only html -css – js.Can you help me this subject.
Best Regards.
Hello,
As you may know, Envato has made authors mainly responsible for refunds and provided a refund policy. I belive we have done everything we can do to prevent mistaken purchases which are not eligible for refund by putting library/framework names on the titles and adding purchase warning in the detail pages.
We accept the refunds without a question if the problem is on our end or if the item was not downloaded yet. If you have downloaded item there is not much we can do. You may check the refund policy here and I will add the part about your case below: https://themeforest.net/page/customer_refund_policy
Kind Regards.
Neither Envato nor authors are obliged to give policy refunds in any of the situations listed below.
You don't want it after you've downloaded it
The item did not meet your expectations or you feel the item is of low quality
You simply change your mind
You bought an item by mistake
You do not have sufficient expertise to use the item
You claim that you are entitled to a refund but do not provide sufficient information as to why you are entitled to a refund
You can no longer access the item because it has been removed or the author who previously provided the item is no longer active on our platform (we advise you to download items as soon as you have purchased them to avoid this situation).Hi, illegal copy of your theme – https://freakpixels.com/template/item/piaf-vuejs-admin-dashboard-template
Hi,
Thank you for taking your time and letting us know. I am not sure there is anything can be done with this kind of websites though.
Have a good one.
Dear Authors,
Do you have more or make complete documentation about the firebase and put some rule-base like member A1, A2 and admin please?
I am not programmer but would love to if you could help with it, I tried once changed Firebase config but still failed, I guessed due my lack of knowledge on it
Many thanks
Hi,
Firebase has a huge documentation so adding ours would be nothing but copy paste.
I really like the idea of user roles and may consider implementing it. However, we are currently working on another project so might take quite a while until we publish it.
I don’t think anybody in our team can qualify as a Firebase expert but if you have specific questions that you have not figured out, we may try to help.
All the best.
Thank you very much for your reply
I found something off when I deploy it to firebase hosting, https://osakade-2019.web.app/app/pages/product/details I am not sure the picture was stretched out link this when I open in Safari, but when I open in Chrome everything is OK.
I don’t have a Mac so I could not test it but I tried testing it via a browser test tool but could not manage to get to the page. They are mostly on private mode and Safari might be preventing session or cookies.
It should not be causing a stretch problem since the image has its height to set auto but you may try adding object-fit: cover to see if it changes anything.
You may modify below block at src/assets/sass/_piaf.style.scss file and include object-fit.
.glide.details {
img {
margin-bottom: 0;
object-fit: cover;
}
.glide__slides {
margin-bottom: 0;
}
}
There should not be any difference with deployed version and your local dev version though. If it is stretched it should be the same for both.
Let us know if this does not help at all.
Hello,
I tried this, but still doesnt work. Maybe I will let you know if I will use this code or not, because seems other pictures seems OK
Hi,
It’s been a while but if you decide to use details page you may try adding below lines to _piaf.style.scss file to set fixed heights for detail images for smaller screens. Still not sure for the cause of the problem but it seems to solve the problem.
.glide.details img {
object-fit: cover;
}
.glide.details img {
width: 100%;
}
@media (max-width: 991px) {
.glide.details img {
max-height: 500px;
}
}
@media (max-width: 767px) {
.glide.details img {
max-height: 400px;
}
}
@media (max-width: 575px) {
.glide.details img {
max-height: 300px;
}
}
@media (max-width: 419px) {
.glide.details img {
max-height: 200px;
}
}
All the best.
Hi , is this comparable with django ?!
Hi,
We don’t have any experience with Django and can not provide a certain answer for your question.
The template is built with Vue CLI 4 so in case you want to search for it.
Hi,
Is there any time picker component ?
Thanks
Hi,
Currently there is not a timepicker implemented in the project. We have not included it since we believe it is better ux to provide two dropdowns for hour and minute for the user and it is quite simple.
If you think a timepicker still necessary, please let us know.
Please advise on the upgrade path for vuetable. Getting a vulnerability error with the axios version its using.
Hi,
We constantly check packages for new versions and aware of the problem with Vuetable and Axios. We have choosen to leave it the way it is until Vuetable is available for version 2. It is currently on beta. https://github.com/ratiw/vuetable-2/releases
Using current version of Axios on a server side application might be risky but since the template is for client side I may say dos vulnerability is not something to worry about.
I can’t run this project… i get all kind of errors on Amazon workspace linux… i had to select use v8.16.2 (npm v6.13.1) ... then with that i’m still not getting all the node dependencies.
This is frustration.. as ive purchased other template and not had this many issues just trying to run the project.. Please advise.
Failed to compile../src/assets/css/sass/themes/piaf.dark.blue.scss (./node_modules/css-loader/dist/cjs.js??ref-8-oneOf-3-1-8-oneOf-3-3!./src/assets/css/sass/themes/piaf.dark.blue.scss)
Module build failed (from ./node_modules/sass-loader/dist/cjs.js):
Error: ENOENT: no such file or directory, scandir ’/home/hbpalme/Downloads/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/vendor’
at Object.fs.readdirSync (fs.js:904:18)
at Object.getInstalledBinaries (/home/hbpalme/Downloads/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/extensions.js:132:13)
at foundBinariesList (/home/hbpalme/Downloads/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:20:15)
at foundBinaries (/home/hbpalme/Downloads/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:15:5)
at Object.module.exports.missingBinary (/home/hbpalme/Downloads/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:45:5)
at module.exports (/home/hbpalme/Downloads/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/binding.js:15:30)
at Object.<anonymous> (/home/hbpalme/Downloads/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/index.js:14:35)
at Module._compile (module.js:653:30)
at Object.Module._extensions..js (module.js:664:10)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Module.require (module.js:597:17)
at require (internal/module.js:11:18)
at getDefaultSassImplementation (/home/hbpalme/Downloads/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/sass-loader/dist/getDefaultSassImplementation.js:24:10)
at getSassImplementation (/home/hbpalme/Downloads/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/sass-loader/dist/getSassImplementation.js:19:72)./node_modules/sass-loader/dist/cjs.js??ref
Hi,
Sorry to hear that you are having problems. We constantly update the template and its dependencies so Node v8 might be somehow outdated. Also, our template has a different way of handling sass files so an os running another template without any problems might not be okay for ours.
As a solution, I may suggest using Node v11 since it is working without any problems at our end.
You may also use v12. I have just tested the template with Node v12.13.0 and Npm v6.9.0. Only package with a problem is Firebase and changing its version to “^7.4.0” solves its issue.
Please let us know if this does not help at all.
Have a good one.
Starting development server… 10% building 2/2 modules 0 activeℹ ｢wds｣: Project is running at http://localhost:8080/ ℹ ｢wds｣: webpack output is served from / ℹ ｢wds｣: Content not from webpack is served from dist ℹ ｢wds｣: 404s will fallback to /index.html 98% after emitting CopyPlugin
ERROR Failed to compile with 10 errors 15:39:45error in ./src/assets/css/sass/themes/piaf.dark.green.scssModule build failed (from ./node_modules/sass-loader/dist/cjs.js): Error: ENOENT: no such file or directory, scandir ’/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/vendor’ at Object.fs.readdirSync (fs.js:904:18) at Object.getInstalledBinaries (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/extensions.js:132:13) at foundBinariesList (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:20:15) at foundBinaries (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:15:5) at Object.module.exports.missingBinary (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:45:5) at module.exports (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/binding.js:15:30) at Object.<anonymous> (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/index.js:14:35) at Module._compile (module.js:653:30) at Object.Module._extensions..js (module.js:664:10) at Module.load (module.js:566:32) at tryModuleLoad (module.js:506:12) at Function.Module._load (module.js:498:3) at Module.require (module.js:597:17) at require (internal/module.js:11:18) at getDefaultSassImplementation (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/sass-loader/dist/getDefaultSassImplementation.js:24:10) at getSassImplementation (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/sass-loader/dist/getSassImplementation.js:19:72)
@ ./src/assets/css/sass/themes/piaf.dark.green.scss 4:14-262 14:3-18:5 15:22-270
@ ./src/assets/css/sass/themes lazy ^\.\/piaf\..\.scss$ namespace object
@ ./src/index.js
@ multi (webpack)-dev-server/client?http://10.112.5.223:8080/sockjs-node (webpack)/hot/dev-server.js ./src/index.jserror in ./src/assets/css/sass/themes/piaf.dark.orange.scssModule build failed (from ./node_modules/sass-loader/dist/cjs.js): Error: ENOENT: no such file or directory, scandir ’/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/vendor’ at Object.fs.readdirSync (fs.js:904:18) at Object.getInstalledBinaries (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/extensions.js:132:13) at foundBinariesList (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:20:15) at foundBinaries (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:15:5) at Object.module.exports.missingBinary (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:45:5) at module.exports (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/binding.js:15:30) at Object.<anonymous> (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/index.js:14:35) at Module._compile (module.js:653:30) at Object.Module._extensions..js (module.js:664:10) at Module.load (module.js:566:32) at tryModuleLoad (module.js:506:12) at Function.Module._load (module.js:498:3) at Module.require (module.js:597:17) at require (internal/module.js:11:18) at getDefaultSassImplementation (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/sass-loader/dist/getDefaultSassImplementation.js:24:10) at getSassImplementation (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/sass-loader/dist/getSassImplementation.js:19:72)
@ ./src/assets/css/sass/themes/piaf.dark.orange.scss 4:14-263 14:3-18:5 15:22-271
@ ./src/assets/css/sass/themes lazy ^\.\/piaf\..\.scss$ namespace object
@ ./src/index.js
@ multi (webpack)-dev-server/client?http://10.112.5.223:8080/sockjs-node (webpack)/hot/dev-server.js ./src/index.jserror in ./src/assets/css/sass/themes/piaf.dark.blue.scssModule build failed (from ./node_modules/sass-loader/dist/cjs.js): Error: ENOENT: no such file or directory, scandir ’/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/vendor’ at Object.fs.readdirSync (fs.js:904:18) at Object.getInstalledBinaries (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/extensions.js:132:13) at foundBinariesList (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:20:15) at foundBinaries (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:15:5) at Object.module.exports.missingBinary (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:45:5) at module.exports (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/binding.js:15:30) at Object.<anonymous> (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/index.js:14:35) at Module._compile (module.js:653:30) at Object.Module._extensions..js (module.js:664:10) at Module.load (module.js:566:32) at tryModuleLoad (module.js:506:12) at Function.Module._load (module.js:498:3) at Module.require (module.js:597:17) at require (internal/module.js:11:18) at getDefaultSassImplementation (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/sass-loader/dist/getDefaultSassImplementation.js:24:10) at getSassImplementation (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/sass-loader/dist/getSassImplementation.js:19:72)
@ ./src/assets/css/sass/themes/piaf.dark.blue.scss 4:14-261 14:3-18:5 15:22-269
@ ./src/assets/css/sass/themes lazy ^\.\/piaf\..\.scss$ namespace object
@ ./src/index.js
@ multi (webpack)-dev-server/client?http://10.112.5.223:8080/sockjs-node (webpack)/hot/dev-server.js ./src/index.jserror in ./src/assets/css/sass/themes/piaf.dark.purple.scssModule build failed (from ./node_modules/sass-loader/dist/cjs.js): Error: ENOENT: no such file or directory, scandir ’/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/vendor’ at Object.fs.readdirSync (fs.js:904:18) at Object.getInstalledBinaries (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/extensions.js:132:13) at foundBinariesList (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:20:15) at foundBinaries (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:15:5) at Object.module.exports.missingBinary (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:45:5) at module.exports (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/binding.js:15:30) at Object.<anonymous> (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/index.js:14:35) at Module._compile (module.js:653:30) at Object.Module._extensions..js (module.js:664:10) at Module.load (module.js:566:32) at tryModuleLoad (module.js:506:12) at Function.Module._load (module.js:498:3) at Module.require (module.js:597:17) at require (internal/module.js:11:18) at getDefaultSassImplementation (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/sass-loader/dist/getDefaultSassImplementation.js:24:10) at getSassImplementation (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/sass-loader/dist/getSassImplementation.js:19:72)
@ ./src/assets/css/sass/themes/piaf.dark.purple.scss 4:14-263 14:3-18:5 15:22-271
@ ./src/assets/css/sass/themes lazy ^\.\/piaf\..\.scss$ namespace object
@ ./src/index.js
@ multi (webpack)-dev-server/client?http://10.112.5.223:8080/sockjs-node (webpack)/hot/dev-server.js ./src/index.jserror in ./src/assets/css/sass/themes/piaf.dark.red.scssModule build failed (from ./node_modules/sass-loader/dist/cjs.js): Error: ENOENT: no such file or directory, scandir ’/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/vendor’ at Object.fs.readdirSync (fs.js:904:18) at Object.getInstalledBinaries (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/extensions.js:132:13) at foundBinariesList (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:20:15) at foundBinaries (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:15:5) at Object.module.exports.missingBinary (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:45:5) at module.exports (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/binding.js:15:30) at Object.<anonymous> (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/index.js:14:35) at Module._compile (module.js:653:30) at Object.Module._extensions..js (module.js:664:10) at Module.load (module.js:566:32) at tryModuleLoad (module.js:506:12) at Function.Module._load (module.js:498:3) at Module.require (module.js:597:17) at require (internal/module.js:11:18) at getDefaultSassImplementation (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/sass-loader/dist/getDefaultSassImplementation.js:24:10) at getSassImplementation (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/sass-loader/dist/getSassImplementation.js:19:72)
@ ./src/assets/css/sass/themes/piaf.dark.red.scss 4:14-260 14:3-18:5 15:22-268
@ ./src/assets/css/sass/themes lazy ^\.\/piaf\..\.scss$ namespace object
@ ./src/index.js
@ multi (webpack)-dev-server/client?http://10.112.5.223:8080/sockjs-node (webpack)/hot/dev-server.js ./src/index.jserror in ./src/assets/css/sass/themes/piaf.light.blue.scssModule build failed (from ./node_modules/sass-loader/dist/cjs.js): Error: ENOENT: no such file or directory, scandir ’/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/vendor’ at Object.fs.readdirSync (fs.js:904:18) at Object.getInstalledBinaries (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/extensions.js:132:13) at foundBinariesList (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:20:15) at foundBinaries (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:15:5) at Object.module.exports.missingBinary (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:45:5) at module.exports (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/binding.js:15:30) at Object.<anonymous> (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/index.js:14:35) at Module._compile (module.js:653:30) at Object.Module._extensions..js (module.js:664:10) at Module.load (module.js:566:32) at tryModuleLoad (module.js:506:12) at Function.Module._load (module.js:498:3) at Module.require (module.js:597:17) at require (internal/module.js:11:18) at getDefaultSassImplementation (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/sass-loader/dist/getDefaultSassImplementation.js:24:10) at getSassImplementation (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/sass-loader/dist/getSassImplementation.js:19:72)
@ ./src/assets/css/sass/themes/piaf.light.blue.scss 4:14-262 14:3-18:5 15:22-270
@ ./src/assets/css/sass/themes lazy ^\.\/piaf\..\.scss$ namespace object
@ ./src/index.js
@ multi (webpack)-dev-server/client?http://10.112.5.223:8080/sockjs-node (webpack)/hot/dev-server.js ./src/index.jserror in ./src/assets/css/sass/themes/piaf.light.orange.scssModule build failed (from ./node_modules/sass-loader/dist/cjs.js): Error: ENOENT: no such file or directory, scandir ’/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/vendor’ at Object.fs.readdirSync (fs.js:904:18) at Object.getInstalledBinaries (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/extensions.js:132:13) at foundBinariesList (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:20:15) at foundBinaries (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:15:5) at Object.module.exports.missingBinary (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:45:5) at module.exports (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/binding.js:15:30) at Object.<anonymous> (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/index.js:14:35) at Module._compile (module.js:653:30) at Object.Module._extensions..js (module.js:664:10) at Module.load (module.js:566:32) at tryModuleLoad (module.js:506:12) at Function.Module._load (module.js:498:3) at Module.require (module.js:597:17) at require (internal/module.js:11:18) at getDefaultSassImplementation (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/sass-loader/dist/getDefaultSassImplementation.js:24:10) at getSassImplementation (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/sass-loader/dist/getSassImplementation.js:19:72)
@ ./src/assets/css/sass/themes/piaf.light.orange.scss 4:14-264 14:3-18:5 15:22-272
@ ./src/assets/css/sass/themes lazy ^\.\/piaf\..\.scss$ namespace object
@ ./src/index.js
@ multi (webpack)-dev-server/client?http://10.112.5.223:8080/sockjs-node (webpack)/hot/dev-server.js ./src/index.jserror in ./src/assets/css/sass/themes/piaf.light.green.scssModule build failed (from ./node_modules/sass-loader/dist/cjs.js): Error: ENOENT: no such file or directory, scandir ’/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/vendor’ at Object.fs.readdirSync (fs.js:904:18) at Object.getInstalledBinaries (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/extensions.js:132:13) at foundBinariesList (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:20:15) at foundBinaries (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:15:5) at Object.module.exports.missingBinary (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:45:5) at module.exports (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/binding.js:15:30) at Object.<anonymous> (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/index.js:14:35) at Module._compile (module.js:653:30) at Object.Module._extensions..js (module.js:664:10) at Module.load (module.js:566:32) at tryModuleLoad (module.js:506:12) at Function.Module._load (module.js:498:3) at Module.require (module.js:597:17) at require (internal/module.js:11:18) at getDefaultSassImplementation (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/sass-loader/dist/getDefaultSassImplementation.js:24:10) at getSassImplementation (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/sass-loader/dist/getSassImplementation.js:19:72)
@ ./src/assets/css/sass/themes/piaf.light.green.scss 4:14-263 14:3-18:5 15:22-271
@ ./src/assets/css/sass/themes lazy ^\.\/piaf\..\.scss$ namespace object
@ ./src/index.js
@ multi (webpack)-dev-server/client?http://10.112.5.223:8080/sockjs-node (webpack)/hot/dev-server.js ./src/index.jserror in ./src/assets/css/sass/themes/piaf.light.purple.scssModule build failed (from ./node_modules/sass-loader/dist/cjs.js): Error: ENOENT: no such file or directory, scandir ’/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/vendor’ at Object.fs.readdirSync (fs.js:904:18) at Object.getInstalledBinaries (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/extensions.js:132:13) at foundBinariesList (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:20:15) at foundBinaries (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:15:5) at Object.module.exports.missingBinary (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:45:5) at module.exports (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/binding.js:15:30) at Object.<anonymous> (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/index.js:14:35) at Module._compile (module.js:653:30) at Object.Module._extensions..js (module.js:664:10) at Module.load (module.js:566:32) at tryModuleLoad (module.js:506:12) at Function.Module._load (module.js:498:3) at Module.require (module.js:597:17) at require (internal/module.js:11:18) at getDefaultSassImplementation (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/sass-loader/dist/getDefaultSassImplementation.js:24:10) at getSassImplementation (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/sass-loader/dist/getSassImplementation.js:19:72)
@ ./src/assets/css/sass/themes/piaf.light.purple.scss 4:14-264 14:3-18:5 15:22-272
@ ./src/assets/css/sass/themes lazy ^\.\/piaf\..\.scss$ namespace object
@ ./src/index.js
@ multi (webpack)-dev-server/client?http://10.112.5.223:8080/sockjs-node (webpack)/hot/dev-server.js ./src/index.jserror in ./src/assets/css/sass/themes/piaf.light.red.scssModule build failed (from ./node_modules/sass-loader/dist/cjs.js): Error: ENOENT: no such file or directory, scandir ’/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/vendor’ at Object.fs.readdirSync (fs.js:904:18) at Object.getInstalledBinaries (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/extensions.js:132:13) at foundBinariesList (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:20:15) at foundBinaries (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:15:5) at Object.module.exports.missingBinary (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/errors.js:45:5) at module.exports (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/binding.js:15:30) at Object.<anonymous> (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/node-sass/lib/index.js:14:35) at Module._compile (module.js:653:30) at Object.Module._extensions..js (module.js:664:10) at Module.load (module.js:566:32) at tryModuleLoad (module.js:506:12) at Function.Module._load (module.js:498:3) at Module.require (module.js:597:17) at require (internal/module.js:11:18) at getDefaultSassImplementation (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/sass-loader/dist/getDefaultSassImplementation.js:24:10) at getSassImplementation (/home/hbpalme/Documents/Sandbox/Piaf-Vuejs-Admin-Dashboard-4.0.1/Source/Piaf-Vue/node_modules/sass-loader/dist/getSassImplementation.js:19:72)
@ ./src/assets/css/sass/themes/piaf.light.red.scss 4:14-261 14:3-18:5 15:22-269
@ ./src/assets/css/sass/themes lazy ^\.\/piaf\..\.scss$ namespace object
@ ./src/index.js
@ multi (webpack)-dev-server/client?http://10.112.5.223:8080/sockjs-node (webpack)/hot/dev-server.js ./src/index.jsHi,
Node Sass is a library that can be quite problematic for different op systems. We have created the project on Windows so package-lock.json file might be cause of the problem if you are on Mac. Please delete node_modules and package-lock.json file and install again to see if problem is fixed.
If not, you may find a table for Node and Os versions of Node Sass below and might need to adjust your version at package.json file accordingly.
https://github.com/sass/node-sass/releasesLet us know if none of this helps.
I’m working with the template and it looks amazing. Can you tell me which location I can edit the text written in this sample ”$t(‘menu.blank-page’)”?
Hi,
Glad to hear that you like the template.
As for your question, $t provides a dictionary of strings based on the current language. You may find and modify the source at below files and blank-page is located around line 86.
src/locales/en.json
src/locales/es.json
Cheers.
Why export doesn’t work in tables
Hi,
If you are referring Vuetable by tables, then I don’t think it has the feature to export of any kind.
Best Regards.
Hello ColoredStrategies.
My company has bought your theme and we run into the problem that the menu isn’t working as expected on ios and iPad devices. Did you encounter any problems with the sidebar when you were developing this?
We can reproduce the bug every time so if you want to check it out we can give you access to the environment where we hosted the template. We also reproduced this on the demo site that your provided.
Edit:
Some additional information provided by my coworker: On ios devices, the first click in the menus is always ignored. This is true for both the main menu and the foldout menu. After the initial click it starts to work properly. When it is used as a one page app its not a major issue (except when opening it for the first time). However, since we are using it as a hybrid app it becomes a severe issue. It is also important to notice it is an iOS specific issue and not just a safari issue, we encounter the same problem in chrome on iOS.
Best regards, Wouter.
Hi,
Thank you for the detailed information. We will look into the problem and get back to you as fast as we can.
All the best.
I have listed using the same code of you used, connected to firestore API, but I can not pagitation, I detailed information of how the pagination module works
Hi,
Please check below screenshot which contains returned data from our api. It contains information like total page count, items per page, current page and so on. You may configure your api to provide these information or you may modify Vue code to work with your api. That decision is up to you. https://ibb.co/ck8j7m8
All the best.
Hi,
I’ve created pages and menus in project set all config. And then run to test but not found my page to created and show error 404.
Thanks,
Hi,
Creating routes has a few steps and there might be a problem with one of the steps.
Please take a look at the docs page if you have not: https://gogo-react-docs.coloredstrategies.com/docs/codebase/routing
Also please check routing code examples in the project at index.js pages from views/index.js -> views/app/index.js -> views/app/[any folder]/index.js
Cheers.
Hi,
I’ve created routes in router.js file { path: ‘app/econveyance’, component: () => import(’./views/app/econveyance’), redirect: ’/app/econveyance/carrequest’, children: [ { path: ‘carrequest’, component: () => import(’./views/app/econveyance/Carrequest’) }, { path: ‘cartype’, component: () => import(’./views/app/econveyance/Cartype’) } ] },
And menu.js file id: “econveyance”, icon: “iconsminds-car”, label: “e-con.econveyance”, to: ”/app/econveyance”, subs: [{ icon: “iconsminds-folder”, label: “e-con.carrequest”, to: ”/app/econveyance/carrequest” },
Am I wrong?
So sorry for earlier response which points to React docs and provides the answer React in mind.
I have checked the code you have provided and it might be related if you don’t have an index.vue file in econveyance folder with a <router-view/> tag.
Also please test below paths and let us know the result.
/app
/app/econveyance
/app/econveyance/Carrequest
I have provided index.vue file in econveyance folder with a <router-view/> tag. Not yet 404 error.
I may recommend looking into Piaf-Vue-Start project which has a smaller routing and you might catch the problem by studying it.
If it does not help, please send your project(without node_modules) to support@crealeaf.com so we may take a look.
Cheers.
HI,
I have sent my project via email to you for find problems.
Thanks,
Hi,
You need to add your routes as child of app since they are located there.
Below screenshot works without a problem. https://ibb.co/zr64WMXCheers.
I have add routes to your suggest but found a problem.
Hello I will used version clic 4.0 but template is 3.5, is there a way up version at moment to installer?? Peter Regards
Hi,
If you mean Vue CLI version, then we will update version 4 probably with our next update.
You may try to increase version in package.json and install again after deleting node_modules and package-lock.json but I am not sure if that will do it.
Cheers.
Is internet access necessary for the template to work correctly?
Hi,
The template is created with Vue-CLI and as far as I know, it does not provide an offline first approach.
Hi, i want to use this template with NUXT. This is possible?
Hi,
The template is created with Vue-CLI and it does not come with a NUXT implementation.
