Discussion on Fury - Angular 16+ Material Design Admin Template

Discussion on Fury - Angular 16+ Material Design Admin Template

By
Cart 1,868 sales
Well Documented

visurel supports this item

Supported

This author's response time can be up to 1 business day.

427 comments found.

@anderswillstedt I don’t know how to respond to other’s comments here, but if you are using the AOT (ahead of time) compiler using “ng build -aot”, then you will get a typescript compile error for undefined types. One example of this is in the constructor for @angular/flex-layout: “@Inject(ObservableMediaService) private _media$”. Since _media$ has no type, for some reason the compiler will throw an error. I’ve temporarily resolved this by using “@Inject(ObservableMediaService) private _media$:any”. Seems to be a problem with flex-layout and I don’t know what the strict type should be for ObservableMediaService so I’m just using type “any” for now.

Hey! There seems to be a breaking change in the flex-layout 2.0.0-beta.5 update. Try changing the package.json to install 2.0.0-beta.4 explicitly by removing the ^ in front. Hope this helps, we’ll fix this asap, hopefully today! :)

Hi, will you have dynamic tables and form validators in the next update?

Hey! Dynamic tables and form validators are already included with Angular 2. :)

Hi there, I’ve recently purchased your theme, but I’m having hard time building it for production, I’ve got few errors like:

ERROR in ./src/app/core/admin/admin.component.ts Module build failed: TypeError: Cannot read property ‘kind’ of undefined

Building for dev works well, but I cannot go live like that. Keep in mind I’ve made no changes at all and I’m just trying to compile your unmodified package (followed install instructions).

Hey! This seems odd. Would you mind dropping us a message at support@martinsuess.com and we’ll figure out why this happens. What version of NodeJS are you using, did you install the dependencies with `npm install`, how did you build the compiled version (with ng build)? On our side everything is working and we had no complains since. Thanks for letting us know anyway, we’ll figure this out for sure. :)

Issue with resizing since the update – see your fixed table example page, if you close then open the sidebar you get a horizontal scroll.

Fixed by removing the fixed width of 300px on the flex and replacing with %.

Thanks for letting us know! We’ll fix it in our next update. :)

Hi! Are you planning to support “rtl” direction? This will be very important in the choice for purchasing a template. I like this one a lot, but without RTL, it’s not the first option. Thanks!

Hey! We’re looking into supporting RTL direction, we’ll try to integrate it in the next update which should be published in a few weeks. :)

Lovely work, great job, it’s not common people create angular 2 templates. Thanks.

Thanks! :)

How to have the sidebar closed by default?

Thanks.

Hey Designi! The md-sidenav component has an attribute called [opened]. If you set this to false, it should be closed by default. :)

Thanks for the reply but that won’t work. [opened] is set by the sidenavOpen property so I can’t change that. I’ve tried setting to false in the layout.component.ts OnInit event but still no luck.

Maybe more an material issue rather related to the theme but thanks anyway.

When I run the theme via ng serve, then navigate to a sub-page, then hit refresh, it loads the page properly.

When I do a build (via ng build) and then put my dist folder contents on a web server (in this case, I have Apache handy,) page refreshes result in a 404 Not Found error.

It appears that the build version isn’t properly routing to anywhere except the root URL on initial load. Could you take a look and see if this problem replicates for you?

Hey Heatherstone! To automatically route to the appropriate route on an apache server you’ll need to create a custom .htaccess file that routes all requests to the index.html. We’ll try to add a section about this to our documentation today. We’ll let you know as soon it’s published! :)

Hey! Take a look at our documentation. There’s an example for a .htaccess file: https://github.com/EinArzt/fury-documentation#url-mapping-on-an-apache-server

Hi, I like this template… I need to know if your template uses jQuery? or it’s pure Angular 2?

Hey mochoamat! Our template is written in pure Angular 2. We have no dependencies on jQuery. That’s also a reason why it’s so blazing fast. :)

Hi, GLWS. I look your theme’s demo. When I reload page, it returns current url and page is loaded. it is cool. how did you do that with Angular 2? Can you explain to me?

I see in the documentation how to add to the menu. I also see that the sidebarnav object has remove item functions. How do you recommend I do a complete reset on the sidebarnav in my app? Overwrite your constructor that does initial setup? Or in my app, call remove functions, then add functions to get what I want?

Hey Heatherstone! We’d recommend removing the default “Demo-Sidenav-Items” and adding yours anywhere you wish. Overwriting the constructor in general may also be a viable option.

If you have any more questions let us know and we’d be glad to answer them. :)

With the latest version of angular-cli (1.0.0-beta.26 as I write this) the current download doesn’t succeed to build. Basically, as of beta 26, the versions of several components are lagging behind.

I updated the package.json locally with the versions specified by angular-cli, which can be checked using ng -v>

angular-cli: 1.0.0-beta.26 node: 6.9.1 os: win32×64 @angular/common: 2.4.5 @angular/compiler: 2.4.5 @angular/core: 2.4.5 @angular/flex-layout: 2.0.0-beta.4 @angular/forms: 2.4.5 @angular/http: 2.4.5 @angular/material: 2.0.0-beta.1 @angular/platform-browser: 2.4.5 @angular/platform-browser-dynamic: 2.4.5 @angular/router: 3.4.5 @angular/compiler-cli: 2.4.5

Once I updated the downloaded theme and reinstalled using “npm install”, the “ng serve” command works! Yay!

This isn’t to say there’s anything wrong with this theme. It’s a side effect of angular CLI being still in beta and both it and Angular in general still getting lots of changes on a seemingly weekly basis.

I’m looking forward to working with the theme!

Hey Heatherstone! Thanks for your feedback. With our latest update we updated Angular-CLI to version 1.0.0-beta.29, which should be the last update before a production build of Angular-CLI, so we’re looking forward to the next version. The @angular packages are currently at the preferred version of ng-cli, which is ^2.3.1 and currently resolves to version 2.4.5. If your global ng-cli package is at version 1.0.0-beta.29 there should be no issues and no changes necessary to work with our template. Note: Angular-CLI changed their npm-package to @angular/cli. The old “angular-cli” npm-package is furthermore deprecated. (Our current update already uses @angular/cli).

I hope this clarifies everything a bit and if there are any issues using our template, we’d happily take your feedback and improve upon it. Have a nice weekend! :)

Something very special!

Thanks a lot!

Hi , I am Wilfried from Germany..I updated the source code as you offered..but now it is not working anymore , even with rebuild

PS C:\Users\wilfr_000\desktop\fury\fury-source\src> npm rebuild node-sass PS C:\Users\wilfr_000\desktop\fury\fury-source\src> ng serve You seem to not be dependending on ”@angular/core”. This is an error.

Thanks Wilfried

Hey Wilfried! You don’t need to rebuild anything. Make sure to run `npm install` as the first thing after downloading the template. It should load all dependencies, including @angular/core. After it finishes you can run `npm start` and a local server will be started with which you can then start developing. Hope this helps! :)

If you need more in-depth explanation, feel free to message us at support@martinsuess.com.

Great Service…it works..Thank you

Hi can you provide more examples of usage d3 charts besides what’s on home page?

Hey! We’re currently working on more charts and different versions of dashboards. It’ll hopefully be in the next update, if you need any specific help setting up charts, feel free to message us at support@martinsuess.com and we’d be glad to help you set them up. :)

Hi, are you going to add a login page in the near future? This would be quite useful.

In the mean time, how would you proceed to add such a page in a component that would be completely separated from the sidenav-container layout, for example just a card with two inputs and a button?

Thanks for your feedback. We’ll try to add a changelog on the product page in the next days. Usually the core components folder should be updateable just by deleting the old and replacing it with the updated one and maybe adjusting just a few things. With the demo components it gets a little harder. If you already changed something in a component, you’ll probably have to merge the changes manually. In the future we’re looking into providing Git-Repo access, so all changes can easily be viewed.

Have a nice weekend! :)

Hi, the git repo would indeed be very nice! I have one more request: could it be possible to get some theming for error messages in forms?

We’ll look into it, but we’ll probably have to wait until Angular Material properly supports it. :)

Hi!

Why data binding in form-wizard is not working?

Try to do it: <input [(ngModel)]=”tel”>

and change this.tel step by step:

1. “(9” 2. “(91” 3. “(91j” 4. “(91” and 4th step will not change input value

Huh. This seems odd. We’ll defnitely investigate, but we could not reproduce this behaviour. Could you provide a plunkr or a private repository in which you show us the bug? It would really help! We can invite you to our GitLab, so you can create it there, if you’re willing to. Anyhow thanks for letting us know and we’ll see if this has something to do with our template!

Hi! Are you going to add WYSIWYG editor?

Thanks! :)

We’ll write the horizontal menu on our todo-list, but I can’t promise it’ll be as fast as this update. Normal links should be no problem and we’ll add it soon.

If you have a few minutes spare, we’d really appreciate if you could rate our theme. You can do this on the item page right below the “Buy License” and “Download” buttons on the right side. Thanks! :)

The backgrounds are from Oxygenna: http://www.oxygenna.com/news/free-new-set-of-material-design-backgrounds

Hi! Could you add a “loading” component? I need it when my card is updating

Hey! We just pushed our next update. It includes a loading-overlay component, a brand new dashboard and various other overall improvements. As soon as it gets approved you should get notified by mail. It should be available in the next 48 hours. :)

Hello,

thanks for your work, it really helps.

After a little play around i think i have found 2 bugs.

When the window is maximized and i click on the smaller button on the menu top, then the hole content shifts to right instead minimizing the menu.

When the window is small and the menu gets hidden, i open the menu through the button and click on an item. I would expect the menu to automatically close after the route change. But the menu stays open and i have to click again into the window to close it.

thanks in advance

Rafael Rutkowski

Hey Rafael!

Thanks for letting us know about this.

Try moving your mouse to the content after clicking the button to toggle the icon-sidenav, it should minimize the sidenav and show only icons. As the sidenav gets smaller, the content has to get bigger too. :)

As to your addition about the navigating on small screen devices, we’ll definitely add this functionality in our upcoming update.

Hope you can wait a few days for this, otherwise contact us at support@martinsuess.com and we’ll find a quick fix.

Awesome theme! Good luck with sales :)

Thanks! :)

by
by
by
by
by
by

Tell us what you think!

We'd like to ask you a few questions to help improve ThemeForest.

Sure, take me to the survey