Posts by ThemeBlvd

1037 posts
  • Affiliate Level 6
  • Author Level 11
  • Collector Level 4
  • Top Monthly Author
+9 more
ThemeBlvd
says
||+520046|Comodoro said-|| It’s true. Internationalization is right there, but not fully implemented by all authors.

What do you mean not implemented by authors? If a theme is localization-ready and provides you with a default PO file (which almost all here are and do), the next step would be to then translate it into your unique language and put your unique language code into your wp-config.php file, right?

So I’m not quite sure what you’re getting at is all. Are you expecting the theme author to have a several PO files come with the theme to have the theme already translated into different languages or something? What else can an author do for while still keeping with the system that WordPress has implemented?

1037 posts
  • Affiliate Level 6
  • Author Level 11
  • Collector Level 4
  • Top Monthly Author
+9 more
ThemeBlvd
says

I’m not trying to steal your thunder here or anything, but almost every theme on ThemeForest comes localization-ready. Localization is the process by which WordPress has come up with translating its software. This system spreads through the core of WordPress and onto all plugins and themes. I understand it can be a little confusing at first, but once you take the time to learn how localization works (i.e. the translation system WordPress has built for it’s own software), you’ll know how to translate just about any decent theme on ThemeForest posted in the last year or two.

1037 posts
  • Affiliate Level 6
  • Author Level 11
  • Collector Level 4
  • Top Monthly Author
+9 more
ThemeBlvd
says


What I do is, I include the sidebar generator class in my themes so that plugin works as a part of the theme.
What plugin you talking about?

He’s talking about this plugin:

http://wordpress.org/extend/plugins/sidebar-generator/

That’s what’s kind of silly about this while unlimited sidebar thing and saying it’s a feature themes must have because many authors are just copy/pasting that plugin into the theme and calling it a feature, when you could just install the plugin with any theme.

1037 posts
  • Affiliate Level 6
  • Author Level 11
  • Collector Level 4
  • Top Monthly Author
+9 more
ThemeBlvd
says

Now I’m not saying I think it’s okay to slap a HTML5 doctype and call it an HTML5 in the title for marketing purposes…

But another sort of silly thing about this whole situation is that all themes on TF have a preview that you can easily view the source of or inspect with a developer tool before purchasing. If you’re complaining that it has HTML5 in title, but then you have the know-how to assess that it doesn’t have HTML5 elements within the markup, you could have easily diagnosed that before purchasing the theme.

So my point is that users, authors, whoever may define an “HTML5 theme” in different ways, however no matter what’s in the name of the theme, it is what it is, and it’s there for you to see.

1037 posts
  • Affiliate Level 6
  • Author Level 11
  • Collector Level 4
  • Top Monthly Author
+9 more
ThemeBlvd
says

Look at this way… if your item was an easy rejection, they wouldn’t need to hold it ;-)

1037 posts
  • Affiliate Level 6
  • Author Level 11
  • Collector Level 4
  • Top Monthly Author
+9 more
ThemeBlvd
says
patisss said
Hmm, thanks! What’s glossy old stuff?

I think he means the places you’ve tried to incorporate your chrome-looking effects (i.e. the time stamps on the first link, and the twitter/facebook icons, etc) which I think are pretty out-dated at this point. They’re just very over done and over glossy. Other than that, everything does look pretty nice.

1037 posts
  • Affiliate Level 6
  • Author Level 11
  • Collector Level 4
  • Top Monthly Author
+9 more
ThemeBlvd
says
jorgemartinez178 said
templatesquare look at this topic a nice example that works http://demowp.templatesquare.com/sevenwonders/

Look closer at the link you posted. When you shrink the window down to his tablet size and refresh the page, you will notice that it appears the slider has scaled down, but actually the right side of all the photos have just been cut off.

But the good news is one of the Nivo guys has said in their support forum that in their next big release they plan to make Nivo responsive (see here). And someone that works with these guys has also eluded to it on Twitter today. This is my juicy gossip column for the day. ;-)

1037 posts
  • Affiliate Level 6
  • Author Level 11
  • Collector Level 4
  • Top Monthly Author
+9 more
ThemeBlvd
says
Enabled said
I gave you the code. It works for me. I used it for all my customers and my themeforest theme, and the theme i’m working now, and I’ve tested it extensively. Giving out the max-width property will lock it, weather JS wants it or not :D

Nope, not buying it. Prove it w/one link. :-)

1037 posts
  • Affiliate Level 6
  • Author Level 11
  • Collector Level 4
  • Top Monthly Author
+9 more
ThemeBlvd
says

Personally I’ve gotten these kinds of messages a couple times, but there’s no reason why I would ever send files directly to a user anyway. If they are having a problem downloading the theme, this would be an issue to contact ThemeForest support.

So, instead of accusing them of not buying the theme or trying to explain what it means to send me a message through my profile page’s contact form, I just tell them what I said above… mm in a nicer way, lol.

1037 posts
  • Affiliate Level 6
  • Author Level 11
  • Collector Level 4
  • Top Monthly Author
+9 more
ThemeBlvd
says
Enabled said

Nivo slider has a main ID class called #slider, when downloading it as default from the website. Give that class a max-width:300px; value for example, and make it smaller and smaller for each resolution you target. It responds by re-sizing the image :) That’s the only example needed. If you use for example

@media screen and (max-width: 320px){
    #slider {
        position:relative;
        max-width:300px;
        max-height:100%;
        height:160px;
        margin-left:auto;
        margin-right:auto;
        overflow:hidden;
    }
}

That for example is for a iPhone screen in portrait mode, and in the same CSS I also added.

@media screen and (min-width: 340px){    
    #slider {
        position:relative;
        max-width:460px;
        max-height:100%;
        height:160px; 
        margin-left:auto;
        margin-right:auto;
        overflow:hidden;
    }
}

And that’s added in the same CSS for making the nivo-slider resize to 460px, meaning, the iPhones landscape mode ;)

Try it out! :) Just remember to give it a max-width not a width! Don’t ask me why, I tested this on several devices and noticed that sometimes width does not respond as it should.

Do you have a working example of this you can show? I don’t see how this is possible because Nivo applies the sliced up images as background images to different little chunks it breaks everything into for its transitions. So, with your method sure the slider would scale down, but it would just cut off all the images. Maybe I’m missing something?

Now I know this is not the Nivo slider, but a variation Kriesi has created himself, but his is responsive.

http://www.kriesi.at/themes/propulsion/
by
by
by
by
by
by