3890 comments found.
Hi @ace.
Is there any chance to have access to the angular version? My github username is akatche
Thanks in advance
Hi there
We have already sent an invite 
can you check again ?
@ace thank for the continuous hard work! Can hardly wait any long, when will the 1.2.0 be released?
Thank you! we lied its more like v2.0 
its that big, working day and night trying to get it released. You will be able to use Angular and Meteor by the weekend and I’m a bit sorry to drag it this long it will be during next week officially
I totally understand. I look forward to the V2.0 release as you claimed it to be!
Dear @ace, I would like to access the GitHub repo. My username is firdausramlan. Thank you.
Hi there
Sent you an invite
Hello!! I’m having an issue with datepicker into a modal, it’s not showing the datepicker.
I have tried with the gisp you have made and is not working as well, the datepicker is behind the modal, as you can see in the print screen:
http://prntscr.com/6uf6leIs there a way to solve this?
thanks!!!!
Hi there
Sure, can you add the following code to your custom css file ? usually custom style.css is located below the pages.css file
.datepicker.dropdown-menu{
z-index:1200 important!;
}
Hi!! Thanks for the fast reply!!
Well, it worked on firefox but not on chrome :/ It’s kinda weird
.datepicker.dropdown-menu{
z-index:1200 !important;
}
. If it works now, you can ignore the below lines 
Did you set any config option in datepicker to load it inside another div other than body (as a child)? If so, that parent z-index maybe conflicting. It’d be great if you can share your code with us (support@revox.io)
Now It works in your example, but not on my code 
I’m going to send you an email with details
thanks!!!
Hi there,
We need a bit of help in regards to styling your awesome theme with datatables. We have purchased your template as well as the editor upgrade (http://editor.datatables.net/)
So we just have a few inconsistencies that I was hoping you could just look at and this would be paid work for you. Likely 1-2 hrs max Id imagine.
Just things like… - tooltips showing the way you have here on the TABLE WITH EXPORT OPTIONS - editor modals that come with datatables are very basic while in your template example they look really nice (your modal popup when you click the ‘Add row’ button - few other button items
so its mostly cosmetic stuff if you will
Please let me know if you are interested. I know you’re in the midst of a new version release so I can definitely wait a week or so.
If you are not available do you know someone you could point me to?
Thanks again for your help
Hi there
Alright yes we are in the midst of a big release, I will have to look at this during the weekend if that ok with you ?
No rush at all. Is there an email I can communicate with you to get you details and to be sure I can pay you…. support@revox.io?
Thanks
Yes its support@revox.io
awesome, Ill send you an email right now to touch base – Thanks!
Got it!
Hi, awesome template!
Can I get acces to test Angular version, please? My username is emichiappero Thanks!
Hi there
Sent you an invite
Is it easy to integrate this template for a Java project on Eclipse IDE?
Hi there
We do not have any boilerplates for java projects yet, currently only for expressjs, sailsjs and ruby rails and an beta Meteor package. It should be quite easy if you chunk them down to modules, like header, foot & sidebar
Some icons are png images, it would be nice to be fonts, like fontawesome
Hi there
You must be referring to the icons on the top, yes because we wanted to get a good clarity out of them, they are actually pixel perfect icons
Hi Ace, i have some inconsistency between my event date starting at “2015-10-07T06:00:00” and the day calendar rendred view is drawed at Thursday 8. I changed my default calendar setting to : locale: ‘fr’ startOfTheWeek: ‘1’ endOfTheWeek:’0’
Hi there
This is a known bug and its fixed will you able to drop an email to support@revox.io so that I can email you the pages.calendar.js file Simply replace with yours and you should be ok.
Hey! Found an issue with the moment.js inclusion in the package.js for Meteor. I had to remove it from the package.js and manually install it.
Meteor (not the browser) was throwing “this function is undefined” error and pointing to line 130 of daterangepicker.js, which uses moment. Even though it was included after moment, it still wasn’t working until I manually installed the momentjs package.
When I did that however, pages.calendar.min.js threw a console error, had to remove that from the package.js as well, and add it manually in the client folder so that it would load after moment.js.
Hi there
Thank you for reporting again Moment Js seems to be the official package in atmosphere.
I will also check it out.
You’re welcome! And it is, all I did was enter meteor add momentjs:moment in terminal. That’s the same package you included in the package.js, so I’m not sure why it didn’t work the original way. Checked the source and the file was included originally to. Might have something to do with the version, but I can’t be sure.
One more thing, I can’t get the Bootstrap-wysihtml5 plugin working. “TypeError: Handlebars.template is not a function” is logged in my Firefox console, Chrome isn’t giving me a specific error, just says undefined is not a function.
Hi Ace,
Is the frontend ready to go ??
We’re looking forward to play with it
Cheers !!
Hi there
Yes! its almost there, testing out different devices, also we are doing angular & frontend simultaneously and new bunch of features coming out
Can’t wait
Hello, i would like to get access to the repo too please. My username is: karlozm
thanks in advance!
Hi there
Sent you an invite
Thank you very much! Joined to the party!
Hi,
Purchased this theme few days back. I was playing around with the layout today and discovered the following:
I created a row with 3 input fields @ col-md-6, col-md-3 and col-md-3. The layout seemed fine on a large screen, See http://prntscr.com/6t8do5.
But on a smaller screen, the input fields had unnecessary paddings on the left and right. See http://prntscr.com/6t8end.
Is there a quick fix for that I can use?
Cheers.
Hi there
For some reason the links that you have sent are not working could you be able to send it again ?
Hi,
Please add these to your pages.css
@media (min-width: 768px) and (max-width: 991px){
form .row [class*="col-"]:not(:first-child), form .row [class*="col-"]:not(:last-child){
padding-right: 0;
padding-left: 0;
}
}
Legend!
It does cause one tiny issue with some other fields using col-sm, see http://prntscr.com/6ta592.
Email address, telephone and fax are in col-sm-6 and address area is also in col-sm-6
But i think i can live with that. Cheers for sorting the issue out
wrong link here is the correct one: http://prntscr.com/6ta592
@media (min-width: 768px) and (max-width: 991px) {
form .row [class*="col-md-"]:not(:first-child),
form .row [class*="col-md-"]:not(:last-child) {
padding-right: 0;
padding-left: 0;
}
}
Awesome! Thank you
Hey Ace,
Just sent you an email through your profile page about getting access to the Meteor package on your github repo. Just didn’t want to publicize my username in the comments.
Thanks!
Hi there sent you the invitation
Its in the following branch v1.2 not in the master
https://github.com/revoxltd/pages/tree/v1.2.0Are you aware of how to setup a local package without using atmosphere in Meteor ? I can get you the guide, it will be in the documentation of v1.2 which we are preparing
Hey! Yes, I run an agency that uses Meteor exclusively for web/mobile apps . It’s installed and good to go. I’ll let you know if I notice any Meteor-specific kinks, but I’m glad you guys set up the integration because we’ve ported HTML/CSS/JS templates over before, and it was NOT fun haha. Thank you!!
Hey—I actually did find a bug. There’s an Uncaught TypeError: Cannot read property ‘toggleOverlay’ of undefined pertaining to the search (on pages.js:1964) when I click the search box. The search overlay isn’t toggling on when the window is in focus and being typed in. Did you see this already?
I noticed some icons were missing but it turns out it’s because they’re images. Dropped the /img/ and /assets/ directories into my project’s public folder to fix that.
Hi there
That should be because you have not included the assets/js/script.js file that has the toggle Search
I assumed that would’ve been in the package, but I guess not. Threw it into the client folder of my project and it looks like it’s working now. Thank you!
I found a few other bugs though—the css files all source assets like background: url(../img/filename.extension);
In Meteor, the path would be url('/img/filename.extension');
Quotes are necessary because otherwise the MIME type is interpreted as text. The path shouldn’t be prefixed with periods because it’s not looking through the same folder structure.
For instance, if the “img” directory gets thrown into the “public” folder in your project, the path would be http://yourdomain.com/img/
Another one is the loading bar remains on top and spinner spins perpetually if you try to add a template include instance using Meteor’s syntax.
It only works properly on the index page, if you have all of the HTML thrown inside that body tag. Even if you add a template insert, like {{> register}} inside if those body tags, it doesn’t work properly. A few bugs I noticed were that the sidebar doesn’t animate out on hover if the corresponding HTML is a template include. It has to be within the body tags in the index.html file.
<body class="fixed-header> html here works fine, template includes don't. The sliding sidebar doesn't slide out on hover if it's a template include.
This makes setting up routes impossible, because they rely on Meteor templates. Are you planning on setting up a full-fledged Meteor version? Because it seems a lot of the JavaScript/jQuery isn’t functioning properly out of the box, and unfortunately I only purchased this template because I saw you were working on releasing a Meteor version.
Meteor is far more than just a development tool like bower, it has a lot of nuances that need to be accounted for.
Hi there
Thank you for advising on all this, it will be looked into . Mean while please do understand its Pre Beta and not a public release, but it will be released a bug free pages meteor package in v1.2. Its one of the biggest updates we are going to add.
We want Pages to be like bootstrap package in metoer. Thirdparty plugins have to be added when needed only example : charts, select2 etc. But the idea of what we are doing is to create a package for meteor not the working demo site you find, it will work obviously. Something more like a boilerplate.
For now, you can include the following, but these all will be taken care after the official version
<script>
$(window).load(function(){
$.Pages.init();
});
</script>
Did you try something like this ?
Also I do not wont to disappoint you, v1.2 will be release definitely within the week. Do let me know how we can improve on Pages for Meteor
Yes, the local package was installed in the same way you described. And I’m using the HTML from that gist.
The issue is if I take all of the code from within that gist’s body tags, and throw it into a meteor template called “layout” for instance, (typically we would chunk it up into multiple templates, for sidebar, top bar, content etc., but this was just to make sure it would work), and include the template, some of your javascript isn’t working properly with routes.
I tried adding your initialization code above, it doesn’t make a difference if I’m using iron:router to point to a specific template for a specific path, like /register for the registration form template. Without iron:router, the index file is fine, even with a template include, I just confirmed. But of course, routes are necessary for Meteor apps.
It seems it’s because there are some jQuery plugins that aren’t being bound to the DOM/initialized properly with routes. Can you have a look at the iron:router package and see how we might be able to correct this? It’s one of the most widely used packages in the Meteor community and superseded Meteor’s core router, it’s the only package people use for routing now.
I appreciate your efforts and I’m glad to hear you guys are actively working on it. I’d like to see integration that deep, where everything just “works,” like bootstrap.
Are there any other functions that need initializing after the DOM is ready? Because in Meteor you can add a hook like so:
Template.myTemplate.rendered = function() {
// initialize stuff here
}
I’ve tried adding your initialization code to that, as well as to the template and to the index.html file but neither of the 3 worked. I’m assuming there’s another initializing script for the sidebar animating outward on hover?
There is a work around that you can wrap pages.js in a window.load function but its not a good practice, could you try adding the following code to Meteor rendered callback ?
// Start initializing Pages core plugins
$('[data-pages="sidebar"]').sidebar(); // initialize sidebar
$('[data-pages-progress="circle"]').circularProgress(); // initialize circular progress
$('[data-pages="parallax"]').parallax(); // initialize parallax
$('[data-pages="portlet"]').portlet(); // initialize portlet
$('[data-pages="quickview"]').quickview(); // initialize quickview
<pre /></pre>
Yes! That worked, and fixed the sidebar issue when iron:router points to a template for the root. Perfect.
But when it points to a register template (I created one and pasted all of the code between the two body tags from your register.html file), the spinner/loading bar stays hanging. I tried adding that original initialize code + the plugin initialize code that you just sent to a rendered callback for the register template, but still no dice.
$(window).load(function(){
$.Pages.init();
});
Any error log on the browser console log ?
classie.js jquery-easy.js jquery-ui.min.js jquery.actual.min.js jquery.bez.min.js jquery.ioslist.min.js jquery.scrollbar.min.js jquery.unveil.min.js jquery.validate.min.js modernizr.custom.js select2.min.js switchery.min.jsIf I add pace.min.js, I see a second loading spinner. But no console errors. Looks like the pace plugin thinks something is still loading for some reason…
If you open up the package.js
You will find the dependencies
api.use(['jquery','mizzao:bootstrap-3', 'momentjs:moment', 'bkruse:pace', 'gromo:jquery.scrollbar','mrt:modernizr-meteor','fortawesome:fontawesome'], where);
There might be a problem with “bkruse:pace” this is not the pace official package, its by a contributor.
https://atmospherejs.com/bkruse/paceThey also do not have a pace.css which is required for it to run.
I really appreciate your corporation with this
You’re right. I removed that from package.js, and manually included the pace.min.js file, as well as the flash theme which was in your plugins folder. That needed to be thrown in for it to work. It caused your nice .svg spinner to look really strange, so I had to comment out these lines of plugin’s css file (I’m guessing it’s overwriting your custom css from the package):
width: 14px; height: 14px; border: solid 2px transparent; border-top-color: #0aa699; border-left-color: #0aa699; border-radius: 10px; -webkit-animation: pace-spinner 400ms linear infinite; -moz-animation: pace-spinner 400ms linear infinite; -ms-animation: pace-spinner 400ms linear infinite; -o-animation: pace-spinner 400ms linear infinite; animation: pace-spinner 400ms linear infinite;
Works and looks fine, and is in the correct position (top right) now! I’m glad to help, thank you for pointing me in the right direction for these fixes.
The last thing that seems to be an issue for this register page is the nice client-side validation you have in your demo. When the input fields are in focus, they don’t turn a darker shade of grey, and when you tab out of a field without filling anything in, it doesn’t turn red and show the required warning. I assume this is just an issue of something not being bound properly.
I added the jQuery validate initialization to a rendered callback, which does show errors if you try to submit the form: $('#form-register').validate()
But there’s something missing to get that form validation working before it’s submitted.
I found the code pertaining to form input in the initFormGroupDefault function. Added a console.log there to confirm that it was being initialized. The issue is it wasn’t being initialized at the right time.
So I commented out the $.Pages.init(); at the bottom, and added it to the rendered callback instead…and now focusing works. This means EVERY template will need a rendered callback with that code.
You guys can use this to achieve that:
Meteor.startup(function(){
for(var property in Template){
// check if the property is actually a blaze template
if(Blaze.isTemplate(Template[property])){
var template=Template[property];
// assign the template a rendered callback who simply prints the view name
template.rendered=function(){
$.Pages.init();
};
}
}
});
Got validation to work—all other jQuery plugins that depend on the init function need to be bound after it fires, I had to add that $('#form-register').validate() bit after the init for the validation to work. Ended up creating a separate rendered callback for this template instead of using that snippet above. This is what it looks like now:
Template.register.rendered = function () {
// Start initializing Pages core plugins
$('[data-pages="sidebar"]').sidebar(); // initialize sidebar
$('[data-pages-progress="circle"]').circularProgress(); // initialize circular progress
$('[data-pages="parallax"]').parallax(); // initialize parallax
$('[data-pages="portlet"]').portlet(); // initialize portlet
$('[data-pages="quickview"]').quickview(); // initialize quickview
$.Pages.init();
$('#form-register').validate();
};
Sorry about the late reply
Just a quick note, Im glad that everything was ok
about pages.init()
// Call initializers
Pages.prototype.init = function() {
// init layout
this.initSidebar();
this.initDropDown();
this.initFormGroupDefault();
this.initSlidingTabs();
this.initNotificationCenter();
this.initProgressBars();
// init plugins
this.initTooltipPlugin();
this.initSelect2Plugin();
this.initScrollBarPlugin();
this.initSwitcheryPlugin();
this.initSelectFxPlugin();
this.initUnveilPlugin();
this.initValidatorPlugin();
this.initView();
this.initListView();
}
It does the following, so initValidatorPlugin() is called in too.
Yup, I saw it in the pages.js file. Just remember for Meteor, you can’t call that pages.init() function in the definition file, because it depends on the template being rendered. Has to be called in a rendered callback. Once that’s taken care of, things work fine.
If anything else pops up, I’ll be sure to let you know.
Select2’s styles were off. Meteor loads package files first, then files in the lib directory, then assets are sorted alphabetically. The pages.min.css file with all the rules needed to be included in the project’s client folder, and I named it “zzzzzz.css” just to get it to load last. Keep that in mind for your updates too.
Hi, can I get acces to test Angular version too, please? I have username “petrbednar”.
Have a nice day.
Hi there sent you the invitation
Its in the following branch v1.2 not in the master
https://github.com/revoxltd/pages/tree/v1.2.0One main style that appears to be missing is the styling of standard file inputs (singular). I see you’ve included a dropzone uploader, but sometimes we just want a single file input to look good.
Hi there
Its in our update list for v1.2
$(".widget-3 .metro").liveTile();
this is the html of the widget-3 I am using (straight from the index.html (dashboard) in the demo folder):
https://gist.github.com/kreoo/f21315991b4a19231369
<link type="text/css" rel="stylesheet" href="assets/plugins/jquery-metrojs/MetroJs.css">
I just wanted to say thank you for the awesome framework you have built. I have been using it for a few months now and I love it more and more everyday. Plus, the support you provide is the best on Themeforest. I could not be happier
Hi there
Thank you very very much! stay tuned for the new update
Can you explain the idea behind using font classes?
E.g. div class=”fs-14”
I’ve seen it in a few other frameworks but I can’t imagine how this is good practice? It seems we are going backwards and handing styling back to HTML instead of CSS where it belongs. If I want to make an update in the future and change all font sizes from 14 to 16 I’ll have to edit each instance across all of the html instead of just one section of CSS.
Am I missing something here?
Thanks
Hi there
Sure
These are helper classes.
The goal behind is for you to make quick elements without having to touch your css.
Example
you have a two paragraphs one with a smaller font and both wrapped in a div with margin top so instead of doing this
.my-widget{
margin-top:10px;
p.small{
font-size:12px
}
}
You directly make it in your html
<div class="m-t-10"> <p>Hello World</p> <p class="fs-12">I'm a the small typo </p> </div>
This really helps us to make widgets without having to update the core css file, so every-time we add a new widget the file size of the css will not increase. If not for these helper classes by year or so you will be looking at at-least 800kb css file that you might not even use the entire classes. Yes there might be downsides, our recommendation is use it carefully but it really really helps
And yes it is a good practice, most of the people who bought recommended it and so far they love using these classes.
Hope you got it, if you have any questions feel free to ask
You can see more about helper classes here
http://pages.revox.io/doc/1.1.0/jquery/helpers.phpHi Ace, I realize this isn’t a gulp tutorial page but If you can lend any assistance, it would be appreciated:
I’m trying to get gulp watch to recognize the ‘assets/less’ folder as well as the ‘pages/less’ folder. I really want to compile all these files into one css file using gulp since editing the ‘pages/less’ files will be overwritten with updates.
I edited the glupfile.js’ watch function to include the assets folder in the path like so:
gulp.task('watch', function () {
gulp.watch(config.pages+'/less/*.less', function(event) {
gulp.run('less');
});
gulp.watch(config.assets+'/less/*.less', function(event) {
gulp.run('less');
});
});
I ran gulp watch, made some edits to the assets/less file and did see the css file in ‘pages/css’ was updated via a timestamp. However, when I search for my new classes, I don’t see them in the ‘pages/css’ file.
Can you lend any guidance? I want to stay away from editing any of the core pages files.
Thanks
Hi there
I’m facing a similar issue, gulp has been updated and so has the gulp-less packages by there authors there some big changes in the changelog, your are not seeing any errors in your console ? Will send you a fix for this
No errors in the console. Not sure why I would since it’s just updating the css file and isn’t even making it to the browser. unless I’m missing something?
No your not missing anything I will post a fix in a few hours for this, could you be able to email me your package.json I just want to see the version numbers for gulp and less its support@revox.io
