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.

Hi there,

I am wanting to integrate your template with the following: https://github.com/aspnet/JavaScriptServices/

Do you think this would be possible?

Thanks, Patrick

Definitely! :)

Hi guys, question

Are you guys thinking in implementing any type of form validations? like ngx-messages?

Thanks

Yes, we’ll definitely implement this soon. :)

Hi! How can I add links to the breadcrumbs? Currently they only display the friendly name, but nothing happens when clicked. Thanks.

Nevermind, I managed to do it adding this to the correct tag on breadcrum.component.html: routerLink=”{{url}}”

Awesome, hope everything is fine! :)

Did you create that scrollable/fixed header table yourself?

Yes, we did. :)

Is there a way to change the default IconSidenav mode to closed instead of open?

Sure! You can just set the default value for [open] in admin.component.ts. :)

Hi, is the GitHub link the only documentation you have? Also, I was wondering what’s the update process in the case that I already have developed my site with a previous version of Fury. Thanks!

Hey! We’re providing Git Diffs you can use to update your developed site. Furthermore we’ll soon provide access to our repository. :)

Yesterday it was Angular CLI (1.0.0-rc.4), i was waiting for final release for few weeks. I hope you guys will upgrade the template to version 1.0.0.

We definitely will! We’re planning on releasing the update next week. :)

hi.., warning? Your global Angular CLI version (1.0.0) is greater than your local version (1.0.0-rc.1). The local Angular CLI version is used.

To disable this warning use “ng set—global warnings.versionMismatch=false”.

hi Angular CLI (1.0.0-rc.4)?

Hey! We’re working hard on the update and will release it asap. We expect it to be in the course of the next week.

We’re working as hard as possible on the update. It’s been 4 days since the Material2 upgrade to Angular 4. Please give us some time to check everything thoroughly for any problems that could result from the update. We want to provide bug-free templates and this takes a few days. Sorry for the inconvenience!

Hi,

I’m getting a a browser error similar to a comment posted a few days ago:

EXCEPTION: Error in ./AdminComponent class AdminComponent – inline template:8:67 caused by: Expression has changed after it was checked. Previous value: ‘over’. Current value: ‘side’.

It only occurs when using Safari 10.12, and only if you manually resize the browser window, to make the sidenav collapse. (all other browsers ok). After the fault is generated, the navigation goes haywire and need to refresh.

Have tried fresh install (Download, then npm install) and still same result.

However, The demo version on the themeforest site works fine in Safari.

I’m not using any emulators etc. and would appreciate some advice…

Hey! This error only occurs on a local development server and not on a production build. That’s why it’s happening to you and is not on the demo. But no worries, next week we’ll provide an update that fixes this. This error was only happening on Firefox Mobile Simulator, but as it’s now also on Safari, we’ll definitely fix it. Thanks for letting us know! :)

apps/inbox Mail App, check inbox full message, layout issues.

Also I go a question, Are you planning to include additional App’s like , ToDo list, Scrumboard ?

Hey! We’d love to know what issues you are experiencing. If you have the time, please send us detailed information to support@martinsuess.com and we’ll be glad to fix those. Also yes! We’re planning on adding more Apps and are always searching for suggestions on what these should be. We added the Todo-List and the Scrumboard to our TODO-List. :)

Hi, You did a greate job but I have a problem with this theme. I am get below error how can I solve this?

Unhandled Promise rejection: Template parse errors: Can’t bind to ‘mdAutocomplete’ since it isn’t a known property of ‘input’. (” <md-input-container> <input type=”text” mdInput name=”autocomplete” ERROR ->=”auto” placeholder=”Your favorite fruit”> </md-input-container>”): AutocompleteComponent@23:71 There is no directive with “exportAs” set to “mdAutocomplete” (” </md-input-container> ‘md-autocomplete’ is not a known element: 1. If ‘md-autocomplete’ is an Angular component, then verify that it is part of this module. 2. If ‘md-autocomplete’ is a Web Component then add “CUSTOM_ELEMENTS_SCHEMA” to the ’@NgModule.schemas’ of this component to suppress this message. (” </md-input-container> Can’t bind to ‘mdAutocomplete’ since it isn’t a known property of ‘input’. (” <md-input-container> <input type=”text” mdInput name=”autocomplete” ERROR ->=”auto” placeholder=”Your favorite fruit”> </md-input-container>”): AutocompleteComponent@23:71 There is no directive with “exportAs” set to “mdAutocomplete” (” </md-input-container> ‘md-autocomplete’ is not a known element: 1. If ‘md-autocomplete’ is an Angular component, then verify that it is part of this module. 2. If ‘md-autocomplete’ is a Web Component then add “CUSTOM_ELEMENTS_SCHEMA” to the ’@NgModule.schemas’ of this component to suppress this message. (” </md-input-container>

auto=”mdAutocomplete”>

<md-option *ngFor=”let option of opti”): AutocompleteComponent@26:20 at SyntaxError.ZoneAwareError (http://localhost:4200/polyfills.bundle.js:4192:33) at SyntaxError.BaseError [as constructor] (http://localhost:4200/vendor.bundle.js:144515:16) at new SyntaxError (http://localhost:4200/vendor.bundle.js:28898:16) at TemplateParser.parse (http://localhost:4200/vendor.bundle.js:44726:19) at JitCompiler._compileTemplate (http://localhost:4200/vendor.bundle.js:84389:68) at http://localhost:4200/vendor.bundle.js:84272:62 at Set.forEach (native) at JitCompiler._compileComponents (http://localhost:4200/vendor.bundle.js:84272:19) at createResult (http://localhost:4200/vendor.bundle.js:84154:19) at ZoneDelegate.webpackJsonp.1652.ZoneDelegate.invoke (http://localhost:4200/polyfills.bundle.js:3534:26) at Zone.webpackJsonp.1652.Zone.run (http://localhost:4200/polyfills.bundle.js:3326:43) at http://localhost:4200/polyfills.bundle.js:3913:57 at ZoneDelegate.webpackJsonp.1652.ZoneDelegate.invokeTask (http://localhost:4200/polyfills.bundle.js:3567:31) at Zone.webpackJsonp.1652.Zone.runTask (http://localhost:4200/polyfills.bundle.js:3366:47) at drainMicroTaskQueue (http://localhost:4200/polyfills.bundle.js:3746:35)

Hey! It seems like you used the autocomplete component template wrong. Please check with our demo and or here and compare: https://material.angular.io/components/component/autocomplete

If you’re still having issues, let us know! :)

Hello, Please check the console error log. I am seeing links like sex.com and others. Not sure if this is some issue at referenced plugins or so. I checked all my other developments, it works well. Only this template when I run ng serve, it throws this error with explicit links in error.

Error in event handler for (unknown): SyntaxError: Failed to execute ‘insertRule’ on ‘CSSStyleSheet’: Failed to parse the rule ’::content .sponsoredInfo, ::content .store-ads, ::content .textAdBG, ::content .top-sidebar-adbox, ::content .ttlAdsensel, ::content .vuukle-ads, ::content .widget_sej_sidebar_ad, ::content .zRightAdNote, ::content a[href=”http://go.oclaserver.com/”], ::content a[href=”http://www.sex.com/?utm_”], ::content #center_col > #\5f Emc, ::content #AD1line, ::content #AdSense3, ::content #LeftAdF2, ::content #ad-adsensemedium, ::content #ad-introtext, ::content #ad-skyscraper, ::content #ad300×600, ::content #adSpace2, ::content #ad_468×60, ::content #ad_comps_top, ::content #ad_middle_2, ::content #ad_stream10, ::content #adcenter, ::content #adops_cube, ::content #ads-sticky, ::content #ads_eo, ::content #adstripnew, ::content #adv_BoxBottom, ::content #advert_mpu, ::content #advman-2, ::content #article_ad_rt1, ::content #banneradrow, ::content #block_ad_container, ::content #box_ad, ::content #columnTwoAdContainer, ::content #cosponsorTab, ::content #dart_ad_block, ::content #dfp_ad_Home_Btm_300×250, ::content #drudge-column-ads-14, ::content #footer-sponsored, ::content #go-ads-double-3, ::content #hd-banner-ad, ::content #home-advertise, ::content #indexad, ::content #layer_ad_main, ::content #lowerAdvertisementImg, ::content #middle_ads, ::content #nbaLeft600Ad, ::content #pgAdWrapper, ::content #rail-ad-wrap, ::content #right_panel_ads, ::content #section_advertorial_feature, ::content #sidebar_txt_ad_links, ::content #sponsorResults, ::content #stopAdvt, ::content #top-ad-right-spot, ::content #topbanner_sponsor, ::content #visual-ad, ::content #yw-sponsoredad, ::content .Ad_728×90_holder, ::content .HomeContentAd, ::content .Tadspacemrec, ::content .ad-300×100, ::content .ad-bt, ::content .ad-incontent-ad-plus-middle3, ::content .ad-prevent-jump, ::content .ad300_ver2, ::content .adBlockSpot, ::content .adLoaded, ::content .adUnit, ::content .ad_bank_wrapper, ::content .ad_holder, ::content .ad_right_column160, ::content .adblock-600-120, ::content .adgear-bb, ::content .ads-220×90, ::content .ads-top-right, ::content .ads_120×60_index, ::content .ads_topic_300, ::content .adsense_sidebar, ::content .adt-728×90, ::content .adv_250_250, ::content .advert-sidebar, ::content .advertising_box_bg, ::content .agi-adsaleslinks, ::content .avertissement-download, ::content .bannerandads, ::content .block-google-admanager-dfp, ::content .button-ads, ::content .cn24-ads-300×250, ::content .content_middle_adv, ::content .dfp-ad-widget, ::content .embeddedAd, ::content .footerAds, ::content .games-ad-wrapper, ::content .google_ad_wide, ::content .header-ad-zone, ::content .homepage-ad-buzz-col, ::content .index_ad, ::content .js-advert-upsell-popup, ::content .leftAdvert, ::content .main_ad_bg_div, ::content .ml-adverts-sidebar-4, ::content .ms_header_ad, ::content .oas-bottom-ads, ::content .pane_ad_wide, ::content .poster_ad, ::content .rectangle-ad-container, ::content .rightColAdBox, ::content .sbTopadWrapper, ::content .side_ad, ::content .site-nav-ad-inner, ::content .sponsor-bottom, ::content .sponsored_well, ::content .subheader_adsense, ::content .themonic-ad2, ::content .top_ad_disclaimer, ::content .uniblue-text-ad, ::content .white-ad-block, ::content .wpfp_custom_ad, ::content a[href=”http://pwrads.net/”], ::content ahref=”https://understandsolar.com/signup/?lead_source=”, ::content .commercial-unit-desktop-rhs, ::content #AD_Zone, ::content #AdcBB_AdContainer, ::content #DivAd2, ::content #OpenXAds, ::content #acm-ad-tag-728×90-btf, ::content #ad-bottom-banner, ::content #ad-medium-rectangle, ::content #ad-textad-single, ::content #ad728top, ::content #adLocation-4, ::content #adStaticA, ::content #ad_Header_768×90, ::content #ad_frame1, ::content #ad_post_300, ::content #ad_video_abovePlayer, ::content #add_space_sidebar, ::content #ads336Box, ::content #ads_sidebar_roadblock, ::content #adskintop, ::content #adundergame, ::content #adv_wallpaper2, ::content #advertisementArea, ::content #adx_ad_bottom, ::content #b-adw, ::content #bgad, ::content #bodymainAd, ::content #btn-sponsored-features, ::content #containerAds980, ::content #ctl00_GoogleSkyscraper, ::content #dfp-ad-boombox_3, ::content #div-ad-r1, ::content #event_ads, ::content #form_bottomad, ::content #googleAdsenseAdverts, ::content #homepageAdsTop, ::content #int-ad, ::content #leaderboard-ad-container-1, ::content #mainAdvert, ::content #mos-adCarouselContainer, ::content #nrAds, ::content #popupBottomAd, ::content #related-ads, ::content #ringtone-ad-bottom, ::content #side-skyscraper-ad, ::content #skinTopAd, ::content #sponsoredFeaturedHoz, ::content #synch-ad, ::content #topAdShow, ::content #tripleAdInner, ::content #whoisRightAdContainerBottom, ::content .AD_300×100, ::content .AdvBoxSidebar, ::content .MadClose, ::content ._articleAdvert, ::content .ad-88×31, ::content .ad-container-bottom, ::content .ad-leaderheader, ::content .ad-sample, ::content .ad-us, ::content .ad336×250, ::content .adBtm, ::content .adOne, ::content .ad_200, ::content .ad_box1, ::content .ad_leader, ::content .ad_sponsor_fp, ::content .adbox728, ::content .adkit-lb-footer, ::content .ads-block-marketplace-container, ::content .ads1_250, ::content .ads_before, ::content .adsidebar, ::content .adunit_300×100, ::content .adv_main_right_down_wrapper, ::content .advertBlock, ::content .advertisement-sidebar{display: none !important;}’.

Hey! This is definitely not from our template. If there are strange links to obnoxious sites, it’s probably on your site. It’s very likely that you have Malware/Adware that add those links. Please check your Anti-Virus program and/or consider installing Malwarebytes Anti-Malware.

Just purchased the template today and I really like what I see so far. The download includes the live preview, which is great, and necessary as an example, but would you consider also posting a stripped down version with only the basics in addition? I’m stripping this stuff out and am wondering if there isn’t a better way.

Thanks, Dennis

We’ll try to provide a stripped “basic” version soon, thanks for the feedback! :)

Hi there,

I’m trying to use the LineChart example in the demo but no matter what I do it doesn’t work.

I managed to separate it to a new page which I’ve created and when I use the demo data file it works.

When I use an API call it doesn’t work. I copied the demo data and converted it to php format and return it as json.

Here it is: Jan 01 2017 00:00:00 UTC+0000”,value Feb 01 2017 00:00:00 UTC+0000”,value Mar 01 2017 00:00:00 UTC+0000”,value Apr 01 2017 00:00:00 UTC+0000”,value May 01 2017 00:00:00 UTC+0000”,value Jun 01 2017 00:00:00 UTC+0000”,value Jul 01 2017 00:00:00 UTC+0000”,value Aug 01 2017 00:00:00 UTC+0000”,value Sep 01 2017 00:00:00 UTC+0000”,value Oct 01 2017 00:00:00 UTC+0000”,value Nov 01 2017 00:00:00 UTC+0000”,value Dec 01 2017 00:00:00 UTC+0000”,value Cost”,color Jan 01 2017 00:00:00 UTC+0000”,value Feb 01 2017 00:00:00 UTC+0000”,value Mar 01 2017 00:00:00 UTC+0000”,value Apr 01 2017 00:00:00 UTC+0000”,value May 01 2017 00:00:00 UTC+0000”,value Jun 01 2017 00:00:00 UTC+0000”,value Jul 01 2017 00:00:00 UTC+0000”,value Aug 01 2017 00:00:00 UTC+0000”,value Sep 01 2017 00:00:00 UTC+0000”,value Oct 01 2017 00:00:00 UTC+0000”,value Nov 01 2017 00:00:00 UTC+0000”,value Dec 01 2017 00:00:00 UTC+0000”,value}]}]

I can view it in the response and it is mapped to the class structure and all that, yet when I try to use it to give the chart as data it shows nothing.

Please will you be able to assist with a working API call? Perhaps one for chart and one for a grid.

Oh, and I’m using the base.service that is given in the documentations.

Your assistance would be highly appreciated.

Thank you in advance.

Regards, Tal.

Hey! We’ll try to provide an example on this soon, there should be no change necessary. You should be able to pass the data in the line-chart in the promise. :)

Hi again,

I’ve managed to get the chart “shell” showing but not the chart content. It’s giving an error: Error: <path> attribute d: Expected number, “MNaN,310LNaN,310L…”.

On a side note: your “core” files are not reusable at all. They’re customized to only show the demo data in the demo structure. If I want to create a chart of my own with different data I have to rewrite the widget almost from the ground up.

That’s not very useful. It should be such that “core” are generic so that they can be extended to produce different results with different structures. In other words “core” should be like a little framework if you will, which I then extend to produce pages looking like your template’s look and feel.

So far, not a very good experience working with your template…

Regards, Tal.

Hey! Sorry to see you have these issues! The chart component is very customizable and is therefore a bit harder to get started with. We’re using D3.js and nvD3. You may want to check out these libraries and their instructions. We’re integrating more Chart libraries into our template right now that are even easier to use and with ready to use designs. Thanks for your feedback! We’ll try to provide examples with other libraries and async data too. :)

Hello,

I’ve been checking this theme in order to test if it fits my needs, but as far as I can see this theme is not built using modules lazy loading, so the initial load is too slow, because the generated files are huge – the initial load contains all the application.

Do you intent to use angular 2 lazy loading modules in future updates?

Tks

Hey! Adding lazy load support should be no problem in our template. We’ll provide an example on how to do so soon! :)

Hey. I just purchased the Fury theme and the actual folder structure is different then what’s described in the documentation. Also, Angular-CLI isn’t even supported.

Ok, it must be something on my end.

Ok… I fixed it be reinstalling the CLI. Weird!

Anyway, I appreciate the prompt support!

I wonder if your template allows to have a search box with autocomplete searching in two columns (and grouping results by categories)?

Hey! Not right now, but very soon the Material Autocomplete component will be capable of doing this. You will be able to create your own search results, grouped and displayed like you want. :)

super! when it will be out?

Probably in the course of the next few weeks. :)

Where i can set the default route and erros route? Example go login instead dashboard.

Sorry, I found, just suggestion: could create a blank page and a source only with basic application without the demos, would facilitate the project start. However the application is great for the good work.

It’s on our TODO-List. Thanks for the feedback! :)

any idea when data table become available?

Probably as soon as Angular 4 releases a stable version. :)

Hi there,

I’ve having some problems please:

I’m quite new to Angular2 but I’ve had someone sit with me who knows Angular and even he couldn’t get it to work.

1. I’ve added a new component and a respective menu item (Not at runtime) but it doesn’t even navigate to that component. I can’t even output “hello”. Can you please provide a step by step instruction on how to add things? 2. I’ve followed the instructions on the Documentations on how to build an api call, it doesn’t work. When trying to do: [code] 1. customers: Customer[] = [ ]; 2. 3. constructor(private customerService: CustomerService) { } 4. 5. ngOnInit() { 6. this.customerService.find().then((customers) => { 7. this.customers = customers; 8. }); 9. } [/code] It gives an error (line #7) that {} cannot be assigned onto type….. Can you please provide a working example of API utilizing the base class provided in the demo OR please help with working example?

Thank you in advance.

Regards, Tal Orlik.

Hey! There has been a few changes, to fix this, just change the type of ‘customers’ from ‘Customers[]’ to ‘any’. The way Angular handles these got changed a little. We’ll update the documentation! :)

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