139 comments found.
You have a public homepage template available (no login required)
Thanks for your query.
Well, in this template we have separate landing page as you can see here – https://react.dashlite.net/landing/ which does not required login.
Thank you
If I buy demo 9 do I get all the front layouts or just demo 9 and does it include the source code?
Thanks for your query.
Well, there is no option to purchase demo9 only. If you purchase this react template then you will get all 9 demos whatever you saw in demo here – https://react.dashlite.net
And of-course you will get source whatever we write on our end.
Thank you
I am planning to buy, I need the gantt chart control. Do you plan to develop it?
Thanks for your comment and interest in our template.
Well, at the moment we do not have directly plan to develop, but as you suggest this so we will add that in our next update.
But it take time to available as our team working on DashLite html version update, once that update complete then we will start work on this React template.
So we can not promise your exact-time frame for this.
Hopefully you can understand.
Thank you
I have purchased this template and its working fine only thing is i am not able to see right side widget which have option to change theme color,purchase button ,use case concept etc.
So can you guide me how i can get that widget
Thanks for choosing our application.
Well, the widget you referring is actually only for demo preview and for that reason it not available in package. if you need to change theme color or style then you follow our documentation here – https://docs.dashlite.net/react/
Thank you
Hi! First thanks for share your job. I would like to know how to change in Demo3 the purple color of the main menuBar (the one only with icons) and also the light grey background color in chats (where the chat is showing). Thank you so much, Sara.
Thanks for asking. Please follow as below -
Change value of $sidebar-bg-theme-color in demo3/src/assets/scss/_dashlite_variables.scss to your color.
Also go to demo3/src/assets/scss/apps/_chats.scss line no 775 and change background color value.
Thank you
There’s a layout problem. A large empty vertical space that creates a scroll.
https://dashlite.net/demo1/user-profile-regular.htmlThanks for letting us know.
We will fixed it in our next version.
Thank you
How can show loader before loading the data into the DataTable??
Please feel free to checkout bellow links from official documentation for loader.
https://react-data-table-component.netlify.app/?path=/docs/loading-basic--docs https://react-data-table-component.netlify.app/?path=/docs/loading-custom--docsThank you
When trying to publish build getting error why???
EAD – Host validation failed: {hostName: ’’, hostType: undefined}hostName: ””hostType: undefined[[Prototype]]: Object content.js:2524 Host is not supported content.js:2526 Host is not valid or supported content.js:2526 Host is not in insights whitelist
Sorry to hear from you.
First of all, which version of the template are you using? Also where do you try to publish? we mean hosting and what procedure you have followed?
Thank you
How can I make a button “dark-switch” without it taking the icon?
This is because I would like to switch mode with this button, for exampleThanks
Thanks for your comment.
Sorry but not sure if you purchased our template or not, if you purchase then you should contact us via support center – https://support.softnio.com/
So you should provide us a screenshot of your example so we can understand better.
Thank you
how i can do multiple Tags search in the DataTable, for example Tag1, Tag2 Tag3 ….. in the table
Well, for search or filter in DataTable component you can follow their documentation here – https://reactdatatable.com/?path=/docs/examples-filtering--docs
Thank you
no, what i mean is this: https://bootstrap-tagsinput.github.io/bootstrap-tagsinput/examples/
We understand but in our used datatable plugin does not support like that.
how i can add action menu ” const DropdownTrans = ” in the dataTable ??? i tried but the menu is not showing 3 dots appears but context menu not?? can you help me with the solution ?
Well, we just try on our end and its works fine.
To add a new column to use your dropdown or any other component in datatable, here we try with the example code below -
{
sortable: false,
cell: (row) => (
<DropdownTrans />
),
},
So please try again and let us know.
Thank
I have done the same way but the menu is not showing, the 3 dots appoear but onclick the menu is not showing
yes, it’s working, my mistake i put ” selector ” instead of ” cell “
Glad to hear that.
Thank you
If I purchase the current version of the app built with Create React App and begin working on my project, will it be easy to upgrade to the Vite version when it is released?
Thanks for your comment.
Well, it will not easy to upgrade to Vite unless you follow complete guideline of create-react-app to vite migration as per react guidelines.
We recommended you to wait for 1 week, and hopefully next update will be available very soon and in next version remove create-react-app and replace Vite. So better is start with Vite.
Thank you
Error: error:0308010C:digital envelope routines::unsupported at new Hash (node:internal/crypto/hash:79:19) at Object.createHash (node:crypto:139:10) at module.exports (C:\xampp74\htdocs\kk.projects\resources\node_modules\webpack\lib\util\createHash.js:135:53) at NormalModule._initBuildHash (C:\xampp74\htdocs\kk.projects\resources\node_modules\webpack\lib\NormalModule.js:417:16) at C:\xampp74\htdocs\kk.projects\resources\node_modules\webpack\lib\NormalModule.js:452:10 at C:\xampp74\htdocs\kk.projects\resources\node_modules\webpack\lib\NormalModule.js:323:13 at C:\xampp74\htdocs\kk.projects\resources\node_modules\loader-runner\lib\LoaderRunner.js:367:11 at C:\xampp74\htdocs\kk.projects\resources\node_modules\loader-runner\lib\LoaderRunner.js:233:18 at context.callback (C:\xampp74\htdocs\kk.projects\resources\node_modules\loader-runner\lib\LoaderRunner.js:111:13) at C:\xampp74\htdocs\kk.projects\resources\node_modules\babel-loader\lib\index.js:59:103 { opensslErrorStack: [ ‘error:03000086:digital envelope routines::initialization error’, ‘error:0308010C:digital envelope routines::unsupported’ ], library: ‘digital envelope routines’, reason: ‘unsupported’, code: ‘ERR_OSSL_EVP_UNSUPPORTED’ }
Sorry to hear from you.
Could you please let us know your node and npm version number? Also your environment to run this so we can produce this issue on our end and resolve it.
Thank you
npm warn deprecated rimraf@2.6.3: Rimraf versions prior to v4 are no longer supported npm warn deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported npm warn deprecated eslint-loader@3.0.3: This loader has been deprecated. Please use eslint-webpack-plugin npm warn deprecated babel-eslint@10.1.0: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates. npm warn deprecated eslint@6.8.0: This version is no longer supported. Please see https://eslint.org/version-support for other options.
added 165 packages, removed 179 packages, changed 174 packages, and audited 2028 packages in 2m Failed to compile.
./node_modules/react-toastify/dist/index.mjs Can’t import the named export ‘cloneElement’ from non EcmaScript module (only default export is available) PS C:\xampp74\htdocs\kk.projects\resources> rm -r .\node_modules PS C:\xampp74\htdocs\kk.projects\resources> npm install npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated @babel/plugin-proposal-unicode-property-regex@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-unicode-property-regex instead. npm warn deprecated @babel/plugin-proposal-optional-catch-binding@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-catch-binding instead. npm warn deprecated @babel/plugin-proposal-dynamic-import@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-dynamic-import instead. npm warn deprecated @babel/plugin-proposal-json-strings@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-json-strings instead. npm warn deprecated @babel/plugin-proposal-nullish-coalescing-operator@7.8.3: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead. npm warn deprecated @babel/plugin-proposal-optional-chaining@7.9.0: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead. npm warn deprecated @babel/plugin-proposal-class-properties@7.8.3: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead. npm warn deprecated @babel/plugin-proposal-numeric-separator@7.8.3: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-numeric-separator instead. npm warn deprecated lodash.template@4.5.0: This package is deprecated. Use https://socket.dev/npm/package/eta instead. npm warn deprecated lodash.isequal@4.5.0: This package is deprecated. Use require(‘node:util’).isDeepStrictEqual instead. npm warn deprecated move-concurrently@1.0.1: This package is no longer supported. npm warn deprecated stable@0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility npm warn deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated npm warn deprecated flatten@1.0.3: flatten is deprecated in favor of utility frameworks such as lodash. npm warn deprecated @hapi/bourne@1.3.2: This version has been deprecated and is no longer supported or maintained npm warn deprecated @hapi/topo@3.1.6: This version has been deprecated and is no longer supported or maintained npm warn deprecated figgy-pudding@3.5.2: This module is no longer supported. npm warn deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 npm warn deprecated rimraf@2.6.3: Rimraf versions prior to v4 are no longer supported npm warn deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported npm warn deprecated @babel/plugin-proposal-private-property-in-object@7.21.11: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-property-in-object instead. npm warn deprecated @babel/plugin-proposal-object-rest-spread@7.20.7: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead. npm warn deprecated copy-concurrently@1.0.5: This package is no longer supported. npm warn deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated npm warn deprecated har-validator@5.1.5: this library is no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated @babel/plugin-proposal-async-generator-functions@7.20.7: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-async-generator-functions instead. npm warn deprecated abab@2.0.6: Use your platform’s native atob() and btoa() methods instead npm warn deprecated q@1.5.1: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other. npm warn deprecated npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp) npm warn deprecated domexception@1.0.1: Use your platform’s native DOMException instead npm warn deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated npm warn deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated npm warn deprecated w3c-hr-time@1.0.2: Use your platform’s native performance.now() and performance.timeOrigin. npm warn deprecated left-pad@1.3.0: use String.prototype.padStart() npm warn deprecated workbox-google-analytics@4.3.1: It is not compatible with newer versions of GA starting with v4, as long as you are using GAv3 it should be ok, but the package is not longer being maintained npm warn deprecated fs-write-stream-atomic@1.0.10: This package is no longer supported. npm warn deprecated sane@4.1.0: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added npm warn deprecated eslint-loader@3.0.3: This loader has been deprecated. Please use eslint-webpack-plugin npm warn deprecated @hapi/address@2.1.4: Moved to ‘npm install @sideway/address’ npm warn deprecated html-webpack-plugin@4.0.0-beta.11: please switch to a stable version npm warn deprecated babel-eslint@10.1.0: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates. npm warn deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm warn deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm warn deprecated @hapi/hoek@8.5.1: This version has been deprecated and is no longer supported or maintained npm warn deprecated @hapi/joi@15.1.1: Switch to ‘npm install joi’ npm warn deprecated svgo@1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x. npm warn deprecated react-beautiful-dnd@13.1.1: react-beautiful-dnd is now deprecated. Context and options: https://github.com/atlassian/react-beautiful-dnd/issues/2672 npm warn deprecated eslint@6.8.0: This version is no longer supported. Please see https://eslint.org/version-support for other options. npm warn deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
this is demo2
Thanks for your comment.
Well, the deprecated message just because we use create-react-app as a based react app. Our team working on this to move Vite for compiling and future support. We are hoping in next version we will update it. Also for now you can ignore this deprecate message.
Thank you
Failed to compile.
./node_modules/react-toastify/dist/react-toastify.esm.mjs Can’t import the named export ‘cloneElement’ from non EcmaScript module (only default export is available)
Sorry to hear from you.
Could you please let us know your node and npm version number? Also your environment to run this so we can produce this issue on our end and resolve it.
Thank you
Is this theme not supporting Typescript & Vercel ?
Thanks for your comment.
Sorry but our template is not support typescript as its based on jquery.
Also we have not try vercel yet, so you can try it out.
Thank you
Angular version available ?
Thanks for asking but sorry to inform you that we do not have Angular version of this template.
Thank you
Hi, thank’s for this nice theme, but I’ve got a question, how can i use fontawesome icon in the Icon component, by default it use nioicons and i need fontawesome one’s, i can i do that. Thank’s
Thanks for asking.
Well, right now our template does not integrated fontawesome by default. So as you need fontawesome, so you need to integrated into react as per their documentation.
You can follow their docs – https://docs.fontawesome.com/v5/web/use-with/react
Also after install the fonts, from markup you must need to replace all the default icon that use nioicon which start ‘ni ni-{name}’,
Thank you
Tank’s a lot, this is what i think about.
Glad to hear it.
Thank you
This template has not been updated in a year, has it been abandoned ?
Well, our team working on another template and we will update after current one finish or whenever required it.
Thank you
