Contact the author directly from the item’s page. That’s the best way to get help.
I have a plugin here on Code Canyon. There are a couple of others that should work just fine as well.
The best place to ask this is in the item comments for the particular slider you purchased. This is a public forum, not a support forum for individual items.
Knowing which slider it is also helps
I built that gallery system for CG Cookie (my brother is one of the co-founders). While I’ve never put together a single complete plugin, I have written extensive tutorials on the different components of the gallery:
Writing a Love It plugin (full plugin available for download): http://pippinsplugins.com/write-a-love-it-plugin-with-ajax/
Creating a User Submitted Gallery System: http://pippinsplugins.com/series/user-submitted-image-galleries/
Creating a User Follow System: http://pippinsplugins.com/series/creating-a-user-follow-system-plugin/
October was my best month ever.
Unfortunately this is not the ideal situation, but officially we are not allowed to offer automatic updates. Rumors say that Envato is working on something similar to the automatic update they offer for WordPress themes on themeforest.
I spoke with Collis personally a few days ago and brought this up. He said that that is definitely not true, and if it is, it shouldn’t be. Authors are more than welcome to include auto updaters. I include auto updaters in all of my new plugins.
@colorit unfortunately for buyers, the only way to get notified is if authors have included something like the updater (I wrote/adapted it) above. When I spoke to Collis (Envato CEO ) a few days ago, I brought this up as a major problem with the marketplaces, so hopefully we’ll eventually see some sort of notification system implemented.
Ad.2 I meant that most options frameworks store data in a single db option instead of few. Plugins require separate db options thus causing additional queries.
The options are still stored in the same DB table and with the way that the WordPress database functions (such as get_option()) work, you actually aren’t querying the database each time. Post meta works the same way: each time you use get_post_meta(), you’re not actually querying the database with each function call.
There are some problems with plugin approach: 1. Plugins update requires additional work for user. 2. Additional queries to db. 3. Relying on third-party plugins may limit flexibility when developing new features
1. Very true but it’s best to get users used to using plugins because it prevents them from getting locked into a particular theme.
2. Not true at all. There is zero difference between code in a plugin and code in a theme.
3. Then build it as a plugin yourself.
partnuz saidWhy would you use the Google recaptcha library in a theme?
Otto42 saidI completely disagree with you. Theme check’s flags even Google recaptcha library. The main goal of theme check was to ease the work wordpress.org reviewers.
If a theme author can’t even get their theme to pass Theme Check’s ridiculously dumb checks, then it’s probably not worth the valuable time of our reviewers to even look at.
That’s a perfect example of a feature that should never be in a theme. You would only place the reCaptcha form in one of a few places: comment forms, registration, login, contact form, etc. And none of those should be built into a theme.
Note that the Theme Check plugin was built specifically for WordPress.org themes and base64 encoded source is not allowed there.
Saying it’s dumb because people rely on it is way over the top. That’s simply stating that the users of the theme check plugin are dumb because they use that as the be-all-end-all tool for determining whether the theme is good. It is a fantastic tool for giving a quick once over on a theme to determine if there are obvious problems, but no automated tool will ever do it all for you. Period. End of story.
If people are using Theme Check as the only check then they are the idiots. Not the plugin.