Discussion on Metronic | Tailwind, Bootstrap, React, Next.js, Vue, Angular, Laravel Admin Dashboard HTML Template

Discussion on Metronic | Tailwind, Bootstrap, React, Next.js, Vue, Angular, Laravel Admin Dashboard HTML Template

Cart 119,803 sales
Recently Updated
Well Documented

keenthemes supports this item

Supported

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

12205 comments found.

Hi,

First of all: well done on this amazing theme. It looks really impressing!

I’ve got a question about the sidebar menu on the left side. How can I add the ‘active’ class to a menu item as soon as the item is active? So, for example, the ‘home’ item (index.php) should get the active class when the loaded page is index.php.

Does Metronic support this?

Thanks!

Jelle

Hi Jelle :),

Thanks for the comment.

Please note, the menu links active state should be handled in server side(in your php script) based on the page’s URL. Let’s say you have a script called sidebar.php which you use to generate the sidebar menu for all of your pages(using php’s include function). So you have one centralized code to handle the sidebar menu. In sidebar.php you will need to generate the sidebar menu HTML code based on your current active page(you can pass your page ID via URL).

Please let me know if you need any further clarification.

Thanks.

I’m having some problems with awesome-fonts in Firefox. the symbols doesn’t appears in the screen, but a not-found icon or something. Can you help me? Thanks for the beautiful work!

Hi there,

Could you please check your page and make sure that you included the fontawesome css file as shown below:

<link href="assets/plugins/font-awesome/css/font-awesome.min.css" rel="stylesheet" type="text/css"/>

Please let me know if you need any further assistance.

Thanks.

Hi ya, me again with some more questions.

1. I activated the tab click on the form wizard however none of the validation or navigation work. please advise.

2. in the inbox how can i pass an id of the mail through. if you check the js below i want to get the message id from the td row. Thats it for now thanks.

 var loadMessage = function (el, name, resetMenu) {

        var message_id =  HOW CAN I GET THIS AND ATTACH IT BELOW;

        var url =  '{{ Request::root() }}/admin/view-message/message_id';

        alert(message_id);

        loading.show();
        content.html('');
        toggleButton(el);

        $.ajax({
            type: "GET",
            cache: false,
            url: url,
            dataType: "html",
            success: function(res) 
            {
                toggleButton(el);

                if (resetMenu) {
                    $('.inbox-nav > li.active').removeClass('active');
                }
                $('.inbox-header > h1').text('View Message');

                loading.hide();
                content.html(res);
                App.fixContentHeight();
                App.initUniform();
            },
            error: function(xhr, ajaxOptions, thrownError)
            {
                toggleButton(el);
            },
            async: false
        });
    }

Last thing on the wizard it also doesn’t display the back buttons or the tick to say the previous tab is complete when using the tab navigation. thanks

Hi,

For the wizard, please add below function right after “displayConfirm” function in assets/scripts/form_wizard.js:

var handleTitle = function(tab, navigation, index) {
                var total = navigation.find('li').length;
                var current = index + 1;
                // set wizard title
                $('.step-title', $('#form_wizard_1')).text('Step ' + (index + 1) + ' of ' + total);
                // set done steps
                jQuery('li', $('#form_wizard_1')).removeClass("done");
                var li_list = navigation.find('li');
                for (var i = 0; i < index; i++) {
                    jQuery(li_list[i]).addClass("done");
                }

                if (current == 1) {
                    $('#form_wizard_1').find('.button-previous').hide();
                } else {
                    $('#form_wizard_1').find('.button-previous').show();
                }

                if (current >= total) {
                    $('#form_wizard_1').find('.button-next').hide();
                    $('#form_wizard_1').find('.button-submit').show();
                    displayConfirm();
                } else {
                    $('#form_wizard_1').find('.button-next').show();
                    $('#form_wizard_1').find('.button-submit').hide();
                }
                App.scrollTo($('.page-title'));
            }

Than replace the wizard initialization code ”$(’#form_wizard_1’).bootstrapWizard” with following one:

// default form wizard
            $('#form_wizard_1').bootstrapWizard({
                'nextSelector': '.button-next',
                'previousSelector': '.button-previous',
                onTabClick: function (tab, navigation, index, clickedIndex) {
                    success.hide();
                    error.hide();
                    if (form.valid() == false) {
                        return false;
                    }
                    handleTitle(tab, navigation, clickedIndex);
                },
                onNext: function (tab, navigation, index) {
                    success.hide();
                    error.hide();

                    if (form.valid() == false) {
                        return false;
                    }

                    handleTitle(tab, navigation, index);
                },
                onPrevious: function (tab, navigation, index) {
                    success.hide();
                    error.hide();

                    handleTitle(tab, navigation, index);
                },
                onTabShow: function (tab, navigation, index) {
                    var total = navigation.find('li').length;
                    var current = index + 1;
                    var $percent = (current / total) * 100;
                    $('#form_wizard_1').find('.progress-bar').css({
                        width: $percent + '%'
                    });
                }
            });

Please let me know if you need further assistance.

Thanks.

Hi,

Regarding the horizontal menu, on layout_horizontal_menu1.html page the menu dropdowns are opened on mouse hover, on layout_horizontal_menu2.html the menu dropdowns are opened on mouse click. So this is just an option.

Please let me know if you need further clarification.

Thanks.

Hello, Thank you so much for your awesome template. I updated my template from v1.5 to v1.5.1 . Then the “Full screen” button doesn’t work. How can I fix this problem?

Hi :),

Thanks for reporting this. We will fix it in the next update very soon. In the main time you can just go to assets/scripts/app.js and replace handleFullScreenMode function with below:

var handleFullScreenMode = function() {
        // mozfullscreenerror event handler

        // toggle full screen
        function toggleFullScreen() {
          if (!document.fullscreenElement &&    // alternative standard method
              !document.mozFullScreenElement && !document.webkitFullscreenElement) {  // current working methods
            if (document.documentElement.requestFullscreen) {
              document.documentElement.requestFullscreen();
            } else if (document.documentElement.mozRequestFullScreen) {
              document.documentElement.mozRequestFullScreen();
            } else if (document.documentElement.webkitRequestFullscreen) {
              document.documentElement.webkitRequestFullscreen(Element.ALLOW_KEYBOARD_INPUT);
            }
          } else {
            if (document.cancelFullScreen) {
              document.cancelFullScreen();
            } else if (document.mozCancelFullScreen) {
              document.mozCancelFullScreen();
            } else if (document.webkitCancelFullScreen) {
              document.webkitCancelFullScreen();
            }
          }
        }

        $('#trigger_fullscreen').click(function() {
            toggleFullScreen();
        });
    }

Thanks.

Thank you so much. Your support is awesome same as your template.

You are most welcome :) We are glad to help you out! Good luck with your project.

Just applying the 1.5.1 update. Have yet to try it in earnest, but thanks for the responsive table scrollbar!

Unrelated I had a ‘problem’ with the scroller (slimScroll). Basically the default colors (grey on grey) are difficult to see. The solution is to set the ‘handle’ color to something different (I chose a shade of blue). I think this is code that could be useful in the next version. My modification in the admin\scripts\app.js:

    var handleScrollers = function () {
        $('.scroller').each(function () {
            var height;
            if ($(this).attr("data-height")) {
                height = $(this).attr("data-height");
            } else {
                height = $(this).css('height');
            }
            $(this).slimScroll({
                size: '7px',
        color: ($(this).attr("hcolor")),  /*'#a1b2bd',*/
                position: isRTL ? 'left' : 'right',
                height: height,
                alwaysVisible: ($(this).attr("data-always-visible") == "1" ? true : false),
                railVisible: ($(this).attr("data-rail-visible") == "1" ? true : false),
                disableFadeOut: true
            });
        });
    }

Note that I set the handle color from the HTML attribute ‘hcolor’. This is flexible because it lets the user specify the color without digging into the script. You will probably want to change the name of the attribute. Also, add ?: code to check the attribute has been set, and to use the original color as a default.

Hi winwaed :),

Thanks for sharing this solution. We will definitely use it in the next update. The name of the attribute could be “data-handle-color”. A bit long but readable :).

Thanks.

Thanks – yes a much better name :-)

Hi, thank you for that sweet theme. It’s very handy, and when you get used to it, it is very easy as well :)

I have a question. I am trying to check and uncheck a checkbox using exactly the same codes in http://www.keenthemes.com/preview/index.php?theme=metronic_admin&page=index.html page. The problem is, I cannot use the usual $(”#chb_Id”).prop(“checked”, true); statement to make checkbox look checked. That code provides the functionality, though. The checkbox behaves like it’s checked already because when I click on it after running the code, it looks like nothing is happening and functions like it’s already checked when clicked. In other words, after running prop function, it behaves like it’s checked but it shows like it’s still unchecked.

When I look at the codes, I see a wrapping div and a span around the input tag. I’m guessing that’s because of these wrapping tags because that span gaines a class=”checked” when checkbox is checked, and deletes that class when unchecked.

Before beginning to start adding and deleting classes on my js codes, I wanted to check with you if there is a simpler way to solve that issue. I would appreciate a simpler solution because I have a lot of these in my pages… :(

Thanks in advance…

Hi CraZyLteR :),

Thanks for the comment.

Please note, for the styled checkboxes and radios we used jQuery Uniform Plugin. When you change the actual checkbox state you will need to call the plugin function to sync its UI state using below code:

 $("#chb_Id").prop(“checked”, true);
 $.uniform.update("#chb_Id");

Please let me know if you need any further clarification.

Thanks.

Excellent! Thank you :)

You are most welcome ;) Good luck with your project!

Thanks to resolve some bugs in short time but there are many bugs still remaining which i have remind you before.

All this are UI Bugs. Please download screen shots from this link - http://www50.zippyshare.com/v/82189629/file.html

- Thanks Harshal

Hi,

Thanks for the details for these minor issues. We will check them further. For further conversation could you use our support email support@keenthemes.com since it will be easier for you to get updated.

Thanks

Hi, I had mail to your suggested email address but i did not got nay reply and still i have no information that when you will fix all bugs of Version 1.5.1

Hi harshaljha,

Please note, our support response time is 48 hours. We have received your email and we will try to look at your email shortly.

Thanks.

Hi,

This template is the leader of the pack IMHO. Well done to all concerned.

However, there is one small frustation: there does not seem to be an easy way to remove the “Meet Metronic” message that appears on Dashboard load. A previos answer to a similar question reads:

“Yes, you can disable it in assets/js/app.js by removing javascript function “handleIntro()” from App.init() function.”

All of the .js scripts are now in assets/scripts/ ?

I’ve had a look at assets/scripts/app.js and can’t seem to find the “handleIntro()” function. Am I looking in the wrong place?

Documentation on the removal of the message would be welcome.

Many thanks.

Hi there :),

Thanks for the comment.

Yes, all the js scripts moved to assets/scripts since v1.2. To disable the intro messages, please go to index.html and remove Index.initIntro(); line from the bottom of the page. We will put this info in the doc in the update.

Please let me know if you need any further assistance.

Thanks.

Brilliant, many thanks for the fast reply. Your solution works perfectly.

Great! You are most welcome :)

Hello, You are amazing Team ..

How to update from 1.4 to 1.5.1 easily?

Hi :),

Thanks for the comment. Please check out the documentation from admin/documentation/index.html the section “Upgrade”. There you can find the migration guide with css class changes table.

Please let me know if you need any further assistance.

Thanks.

You guys are terribly awesome!!! :D How do you manage to do these? :)

Hi praveenscience :),

Many thanks for the comment.

We love what we are doing and we just can’t stop doing it :). This is not the last one, more amazing endless updates will be coming in the future.

Thanks.

You are amazing…Thanks kt.

Many thanks, mahirc :)

Hi,

I downloaded the update 1.5.1 version.

I perform the update, which files have been modified?

Hi mirulu :),

Please check out the detailed changelog from the documentation admin/documentation/index.html

Please let me know if you need any further assistance.

Thanks.

Hello – great theme!

Is there a way to have the breadcrumb and the title above it fixed so it doesn’t scroll away on pages with long content?

Hi claimfame :),

Thanks for the comment. At the moment the theme does not support a fixed breadcrumb option. To implement this we need to redesign the breadcrumb part to suit it for the fixed position. However we will consider implementing this in a future release.

Thanks.

thanks for the quick response!

You are most welcome, claimfame :).

Hi, i’m looking through your template and i think it looks fantastic. However i’ve found a few bugs with the boxed layout.

1. Go to: http://www.keenthemes.com/preview/metronic_admin/page_portfolio.html 2. choose boxed layout 3. click on 3 columns or 2 columns and the view icons are either missing or cut in half.

Hi mawendel :),

Thanks for the comment and feedback. We will take a look at this and improve it in a future release. In the main time you can adjust(make the text more short) the content inside the portfolio item’s container to fit it for your preferred device width.

Thanks.

Hi, this template have a jquery dialog?

Hi johnjunior,

At the moment the jquery dialog feature is not supported. However we will consider adding it in a future release.

Thanks.

Is it possible to keep the old naming conventions for example for css classes? It is extremely hard to update the theme to the latest version when these changes. I have to revise all my code on each update.

For example, in 1.4, the mini buttons had “mini” as CSS class, now in 1.5 it was replaced by “btn-sm”.

Why do you always keep changing these? Because of this, I need to change ALL my buttons to use the new class…..

Hi Parkyprg :),

Thanks for your feedback. Since Bootstrap 3.0 version we had to revise the class names and in the future we will stick with current class names. I would suggest you to check out the class name change table in the documentation admin/documentation/index.html and use the global text replacing(in your editor) to update the class names for your server side scripts.

Please let me know if you need any further clarification.

Thanks.

Hello!

It would be great if you add a design of “Requirement Page”.

When you install an application, it first checks if the environment provides necessary options to be installed.

You can see some examples below. Although the examples are in Turkish, I’m sure you will get the idea.

Regards, Bunyamin Inan.

Examples

aa

bb

Hi bunizz :),

Thanks for your suggestion. We will consider including this feature in a future release.

Thanks.

We have bought this theme and got the download, but in the download I can only see demos of what things are available but can not find any document instructing how to use the features. Is the user supposed to inspect the elements of the demos to try to figure out how to use the pages/widgets and stuff? There is a html-page under the documentation directory showing how to use a limited number of included tools. Have I missed something? How would I go about to read about how to implement say a login page/form using your tools? Thank you for an otherwise excellent product.

Hi smlinstitute :),

Please note that the theme comes with a general documentation and if you will have any further questions that are not covered by the doc you can always ask our support at support@keenthemes.com. The template code is clean and easy to understand. So to get started with your project, the demo pages can help a lot. You can inspect the template pages and retrieve code snippet you need to build your own pages.

Please let me know if you need any further assistance.

Thanks.

Wondering if your going to support .less for this theme?

Hi thinkingcap :),

Yes, we do have serious plans for LESS support in the future. However it requires some afford and time and at the moment we can’t give any clear timeline. But we will do our best to release it as soon as possible since many of our customers request for this feature.

Thanks.

Hi keenthemes.

In Form Components page, the data-date-viewmode attribute doesn’t work. Can you take a look at it, please?

Regards, rrispoli.

Edit: the new bootstrap-datepicker.js file doesn’t support data-date… attribute. I think it can be fixed in the form-components.js, reading the data attribute values.

Hi rrispoli :),

Viewmode parameter is referred as startView option that can be passed when you initialize the datepicker:

$('.datepicker').datepicker({startView: 'year'});

To learn more about the datepicker plugin please check out http://bootstrap-datepicker.readthedocs.org/en/latest/

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