Other than those two issues It is truly beautiful work! I really like the look and layout… the documentation wasn’t a big deal as it is pretty standard… I was really looking for the icon font documentation so I could customize them… but then I found your Icon Page… sorry

However even with the reported bugs it is at least 4 star work… I have not reviewed it yet as I am awaiting the bug fixes to give it the 5 stars it truly deserves, thank you!

Hello… anyone still there?

No support?

Hi! Thank you for the bug report. I’ll provide a fix shortly.

The demo is working now. Thank you for letting me know!

Hi pajgps,

Thank you very much for the detailed description of the issue. I’ll look into it and provide an update.

Thanks for your reply. Can you tell me when do you find a solution for this? Thanks in advance

Of course, I’ll be looking into finding a solution as soon as I get my hands on an Android device.

Hi BenzaHdd,

Volta uses the latest version of jQuery 3.x.x. If you’re having issues with jQuery I would suggest you to create an issue on their GitHub repository. https://github.com/jquery/jquery/blob/master/README.md

Also, I don’t quite understand what you mean when you say your site got corrupted. Some more details would be helpful.

Can you send me an email with your purchase code and the console error you’re getting? Thank you!

It’ll be included in today’s update.

Thanks!

Thank you very much for the rating! I very much appreciate it!

The update for the scrollbars is up. Make sure you update your assets.

Hi misaon,

Here’s an update on what’s done in the new version:

- Rewrote all pages to use PugJS as Template Engine
- All themes now available and choosable without switching stylesheets
- Added Browserify support for building assets (unbundled)
- Added WebPack 2 support for bundling assets
- Fixed several responsiveness issues
- Perfected gulp setup
- Removed the need for a server
- Sidebar navigation remains open on active categories when changing pages
- Right sidebar is now touch reactive

Also, some things I’ve done that speed up further development:

- Sidebar links are generated from a JS Object
- Documentation is generated from Markdown files 
- Wrote automated release script
- Added Circle CI support

Next, I’ll deploy it to my server and the new update will be up! That’s when I’ll start adding more of the requested features.

Hi MasJZ, I’m currently not available for any freelancing work as I’m focusing on envato only. Thank you for asking!

Hi Shatan, I’ll add it to the requested features list. Thank you for the suggestion!

Hi ApesPark,

Here’s the status of the update:

- Rewrote all pages to use PugJS as Template Engine
- All themes now available and choosable without switching stylesheets
- Added Browserify support for building assets (unbundled)
- Added WebPack 2 support for bundling assets
- Fixed several responsiveness issues
- Improved and stabilized gulp setup
- Removed the need for a server

As you can see it’s a big update with lots of changes which will make development a breeze. Currently making the files ready to be distributed on Themeforest. This is the tricky part, because I cannot expect everyone to use the build system, so I’ll need to provide 3 output folders from the start:

- A folder containing source files to be built
- A folder containing built sources, can be modified by anyone without knowledge about build systems
- A distribution folder, generated from the build system, directly minified and ready for uploading.

pixevil can you watch this? - input group not render properly - when i use “first WYSIWYG”, i must include Markdown too.. :/ - i have too many warnings on my server [NGINX] (some other admin teplamtes worked fine) (Chrome 58 on Windows 10): OTS parsing error: Failed to convert WOFF 2.0 font to SFNT OTS parsing error: incorrect file size in WOFF header OTS parsing error: Failed to convert WOFF 2.0 font to SFNT - too many resources, can you make change in gulp compilation. Join some core CSS and JS styles into one file - implement trumbowyg please (https://alex-d.github.io/Trumbowyg/), is better, smaller and easier. - add scroll top option - stay tuned and i waiting for changes, good job pixevil

Hey,

The first WISIWYG is called summernote and should not require Markdown. Markdown is used by the second one. I’ll gladly include more WYSIWYG options in the following updates (including Trumbowyg).

The font parsing errors appeared because somewhere along the way, my versioning system (git) added the fonts as text files instead of binary files. I’m afraid you’ll need to download them manually and replace them to get rid of the errors. I’ll see if these persist if I add them as binary.

Scroll top – good suggestion, will definitely add it!

I’m very close to finishing the new build system that will include PugJS as templating engine, allowing you to easily make new pages (required me to completely rewrite the template in Pug, which is why its taking so long).

I think the joining of CSS and JS files should be your choice, since with HTTP\2 it’s not required anymore because it won’t be any major speed enhancement. It can be easily done with a gulp plugin such as https://www.npmjs.com/package/gulp-htmlbuild.

Thank you! I’m glad to hear you’re looking forward to the update.

About http/2 I have a different opinion. This new http protocol has the advantage of better and faster retrieval of all kinds of resources, such as images. BUT! If you load too much CSS or JS on each page, it will stuck load your browser while loading. The browser can read about 10 requests at one time (even with HTTP/2 turned on). The page is then loaded slowly. That’s why I suggested implmentation of the preloader. On my side I will have to deal with concatenate with a gulp. It would be good if VOLTA CORE JS and CSS were already merged in their default state. The best solution would be a webpack. I’m looking forward to the new update! Ty pixevil!

thanks very much its great work.

i have problem with the main page if I hide and show the cave by jquery >> div class=errorCould not draw pie with labels contained inside canvas >> /div

Hi lolyos,

I’ve been looking into your issue. This error is related to Flot http://www.flotcharts.org – a plugin used in Volta for drawing the pie charts. It is caused due to the size of the chart container getting too small for the Flot plugin to draw the chart.

Solution from StackOverflow The pie functionality of flot has restrictions on the legend and labels. The code makes sure that the legend/labels stays within the boundaries of the canvas, and if it doesn’t it fails as you have seen. Your options are:

• Make your canvas bigger
• Make your labels shorter
• Use a legend outside of the canvas using the legend.container option to specify an outside div