Discussion on Pages - Admin Dashboard Template

Discussion on Pages - Admin Dashboard Template

By
Cart 11,420 sales
Well Documented

ace supports this item

Supported

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

3890 comments found.

Hello, just purchased! Please add to github repo: justinkgreenberg

What is the status of Angular integration? Please let me know.

Thanks :)

Hi there

I tried searching you up but I do not see anyone with that user name can you double check ? :)

Hi I’m sorry github username is justingreenberg

Any word on angular integration? Thanks again :)

Sent you the invite :) we will be starting this week.

hmmm grunt generates only part of what you need, non of the partials.

What our idea was to kickstart your project like the getting_started folder in pages package :) In the terms of creating a view controller what are the packages you wish to have ? as an idea we can convert the entire demo folder to ruby on rails ? :)

That would be awesome to drop in the entire demo folder into a standard rails directory path and have all of the references work with the asset pipeline. Crap if you do this, I’ll buy this a couple more times just to support the effort.

:D Thank you! yes I will be

Hi Ace,

If i needed to change the social-wrapper to another class name because i have two pages with specific widths needed for the cards, whats the best way to do so?

Best, rick

@ace, let me know if that is possible to modify the script to accept custom config such as:

$('.brands').social(){ colWidh = 375; }; 
This way each page with a different class can have its own width without having to insert a different JS. Thanks for all the help ace.

Hi,

Yes, it’s possible too. Please use the code below:
$('.brands').social({
     colWidth : 375
});

Thanks Ace. Works perfectly.

After upgrading to the new version, the menu stopped working. If I reverse to the old pages.min and Jquery 1.8.3 works. Is there a way to fix this conflict? Does anyone else have the same problem?

Hi there

Please make sure you update pages.js and pages.min.js from pages/js folder :)

The menu stops working (appearing) after I replace the files with the ones from the new version folder

Ok is there an error on you console log, you can see your console the following way

http://javascript.info/tutorial/development

or you can show a demo link of the version that you have and drop an email to support@revox.io :)

I just want to let others know, this is a very good product and the support has been excellent. I’m always happy when I communicate directly through the comment system for support rather than being told to use their internal support system.

The only negative, the documentation isn’t very detailed. It’s not bad, but it could be better. More code examples would help. Not a big deal though, as I said before the support has been excellent.

Thank you for the comment and your input! :) Sure, will try to add in examples and if you have a specific page or part of the documentation which you saw that would need improvements do let me know, Will attend to it right away :)

Thanks. I’ll try to throw source code examples back when for the pages that I had trouble with.

I may have spotted a bug. The <textarea> element is being populated with white space. If this is intentional, please tell me where to find it in the source so I can prevent this from happening. Thanks.

I’ll try now.

Thanks! That made no difference, however I figured out the issue.

It was the tabs in the source code. E.g.

<textarea>

\t data (pretend the \t is a tab, since I can’t use tabs in the comments, also there shouldn’t be line breaks below and above the tags, had to add them because everything was on a single line like my example below)

</textarea>

had to change to

<textarea>data</textarea>

Not sure why this is happening, the source code formatting hasn’t been an issue before unless there were spaces or &nbsp’s.

Hi,

There shouldn’t be any leading or trailing spaces inside a <textarea>. Therefore:
<textarea>data</textarea>
is the correct form. Have a look at the following SO question: http://stackoverflow.com/questions/2202999/why-is-textarea-filled-with-mysterious-white-spaces

in the mobile / tablet view of the email page, the user dropdown goes behind the email page rather than in front like the other pages

We have hidden the user dropdown for small/mobile screens in the demo. Have you made it visible by removing visible-lg and visible-md?

we made it mobile following the guidelines / samples you provided to an earlier comment about just having the avitar available. Otherwise those settings are not available. to device users

Hi there, I understand that you have PSD for the design. Any chance for a Sketch format?

Hi there

I’m not very familiar with Sketch format, for now we will be sticking to PSDs for raw designs :)

Hello guy, so with a regular license can i for example “build a video streaming APP” and charge people for that service?

Best regards

Hi there

According to themeforest if your end product is sold or the user is been charge you will have to stick with extended license when you go live :) also you can double check by submitting a ticket at the bottom of the following page

https://help.market.envato.com/hc/en-us/categories/200216004

There’s a bug with the fullscreen modal for anything smaller than a laptop. The overlay is sitting on top of the buttons and there’s no way to dismiss it. Maybe there’s a missing z-index for xs,sm,md.

Hi there

Sure will add it to the doc :) from my knowledge its ok to have it on top, but do let me know if its a big concern to have it at the page bottom :)

Thanks, I appreciate that as I will surely forget this detail in the future.

It’s not a big concern, I think back in the day it was though, because search engines would index from top to bottom. When a description is not used the search engines would create one from the content on the top, so your description would contain the contents of the modal which isn’t desirable.

It used to also be good practice to put all of your content on top in the source and everything else at the bottom, but perhaps that’s no longer relevant. If it is still relevant I would recommend bottom placement for all the off screen content, because it used to make a big difference in the search results (having content at the bottom moved my pages up in the results).

Of course, if using this theme for it’s intended purpose, there’s probably not much concern for search engine results, because you don’t want your password protected admin site indexed anyway.

That is true its intended for webapps but we made sure it can be used more than that :) I will look into it if SEO have an issue of that sort and thank you very much for you inputs

Can you add this to helpers?

.auto { cursor: auto!important; } .default { cursor: default!important; } .none { cursor: none!important; } .context-menu { cursor: context-menu!important; } .help { cursor: help!important; } .pointer { cursor: pointer!important; } .progress { cursor: progress!important; } .wait { cursor: wait!important; } .cell { cursor: cell!important; } .crosshair { cursor: crosshair!important; } .text { cursor: text!important; } .vertical-text { cursor: vertical-text!important; } .alias { cursor: alias!important; } .copy { cursor: copy!important; } .move { cursor: move!important; } .no-drop { cursor: no-drop!important; } .not-allowed { cursor: not-allowed!important; } .all-scroll { cursor: all-scroll!important; } .col-resize { cursor: col-resize!important; } .row-resize { cursor: row-resize!important; } .n-resize { cursor: n-resize!important; } .e-resize { cursor: e-resize!important; } .s-resize { cursor: s-resize!important; } .w-resize { cursor: w-resize!important; } .ns-resize { cursor: ns-resize!important; } .ew-resize { cursor: ew-resize!important; } .ne-resize { cursor: ne-resize!important; } .nw-resize { cursor: nw-resize!important; } .se-resize { cursor: se-resize!important; } .sw-resize { cursor: sw-resize!important; } .nesw-resize { cursor: nesw-resize!important; } .nwse-resize { cursor: nwse-resize!important; }

Hi there

A lot of cursor classes :D any specific reason why it is important ? :)

It does add a little overhead, but it’s nice when developing a web app vs. a traditional website. For example, I used the not-allowed cursor on a disabled form button to add extra context for the user.

It’s also another feature/selling point. If I were considering two themes that were basically equal with the exception that one had the cursor helpers and one didn’t, my sale would go to the one with the cursors, because that theme provides more perceived value than the other. I know this example is somewhat contrived, but even if one person bought your theme for this reason, wouldn’t that sale cover the costs to add this?

Wouldn’t this be another feature that your theme offers that the others don’t? Even though it’s not really a super cool feature, it’s still a value proposition which you can use to be more competitive and increase your sales. You put enough of these web app features together and now your not selling an admin theme (dime a dozen), you are standing out as the only guy selling a framework for modern web app development that can also be used for an admin site. This sends more interested buyers you way, those looking for ui kits and modern frameworks, not just folks looking for an admin theme.

Point taken :) I just wanted to know your where you are going to apply. Will be adding this :)

I noticed that in the example you provided to “ehsanquddusi” on the “Avatar on Mobile” it does not show up in “regular mode” . . . I noticed also in your code it seems that we may have to configure a different setup for each view (including the dropdown menu). Is there a way to recode it so it shows up in none-mobile views as you have it now and then into the condensed view on mobile. using only a few code adjustments rather than including two versions? . . . hope that all makes sense

Hi there

Alright, I will check it up again :) yes true, Will make a common one for both mobile and desktops.

Thanks . . . in the meantime, we’re setting up two identical views following your examples as you have it currently modeled

Great! so I think its crucial to get the mobile user also the ability to see almost all the content possible, will be working on fix for that :)

Hi!

I like to get access to the GitHub, my username is jorisvanw

Thanks,

Joris

Invitation sent.

This is a repost of my previous issue. I guess that got lost in thin air ;-)

Just wanted to figure it out how to display User picture on mobile view with dropdown. Username will be removed from xs view and user picture with remain there (on the right side).

Or maybe the user stuff will move under left side menu?

Please help to sort it out.

You have an unclosed tag in your code snippet. Please find the corrected example in the gist below:

https://gist.github.com/praveenaj/94bb8da22c0eb5e89c3f

Thank you for your help, but it doesnot solve the problem. Only col-xs-* has effect on it. Please try for col-sm-* or col-md-*. These classes make no difference to it.

From what I tested, col-sm-* and col-md-* start working at their relevant resolutions. Would you mind sharing the code you have so that we can identify what’s happening. You can reach us on support@revox.io

Great theme! I’m trying to locate the documentation for the Mapplic plugin but I’m not seeing it in the download. Will you either send that or let me know where I can find it?

Please send a mail to support@revox.io to receive the documentation. Thanks

Bro, you absolutely hit the nail on the head as I was trying to figure a way to integrate SailJs with your theme. I will promote your framework at the hardware hackathons for sure!! Keep making templates like this that can hook into these frameworks and you can just TAKE MY MONEY!! Great job and I look forward to more updates like these!! I appreciate it, going to hook up CylonJS to your generator and crank out some cool stuff!!

Thanks AGAIN!!!

Awesome! We’re glad you like it. Thanks for your support :)

Love the generator… Do you think you could make something like that for METEOR? That will be sweet.

Thanks for your suggestion. We’ll consider that in a future update.

Hello there!!

I’m having an issue with checkbox. I’m ussing the theme in a .NET project and .net ads an hidden field right after the checkbox, so the checkbox doesn’t work – I can’t check or unckeck it.

The code above can reproduce the issue.

<div class="checkbox check-default"> <input type="checkbox" checked="checked" value="1" id="checkbox2"> <input name="checkbox2" type="hidden" value="false" /> <label for="checkbox2">Keep Me Signed in</label> </div>

Is there a fix for that?

Thanks in advance. Julio

Hello, thanks for the quickly reply. :)

So, that is the problem, the hidden field is added automatically by the .net framework at runtime, I’m can’t handle this to add the hidden field below the label, unfortunately.

Is there another way to fix this?

Thanks again!!

Hi there

So the reason is because we use + css selector to select the next closest label, so the work around is using JS :)

Add this code to any of your custom js file

    $(document).ready(function(){
      $('.checkbox label').on('click',function() {
        $(this).parent().toggleClass('checked');
      });
    })

and in your custom css in the assets/style.css you can add

the following without changing the core pages so you can take updates easily :)

.checkbox.checked label::after {
font-family: 'FontAwesome';
content: "\F00C";
color: #fff;
}

.checkbox.checked label:before {
border-width: 8px;
}

Hey man, this just saved my life :)

thanks a lot for this. It works like a charm.

Thanks!!!

can you create rtl version please

We’ll be adding a rtl version in a future update.

thank you

Quick question. When pinning the menu down, is it possible to display the secondary logo (brand inline) rather than have it hidden behind the menu?

Yes,

menu-pin class is appended to body when the menu is pinned. Using that you can set a margin-left for the brand so it’ll start to appear ex:
.menu-pin .brand.inline{
margin-left: 185px;
}

Perfect, 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