Didn’t they tell you? It was a mistake, that package was for me, but address got messed up. I’ll message you with my address so you can forward it to me, I hope you did not eat all the tim-tams already…
Congrats btw Must be a great feeling!
Voted, cool idea, good luck guys!
neutrico saidBrowser extension maybe?
OriginalEXE saidThis is weird. I launched fresh 13.10 instance in VBox and logo background is ok.
neutrico saidNo such issues here on Kubuntu, same version of os and ff.
I know that probably all Envato guys use Apple hardware, but you should test it on another platforms.
There is something wrong with logo background. Firefox 25.0.1; Ubuntu 13.10
^ For some reason i appear first now, but my speed is not even close to this guy (supremethemes) who is 2nd. I think the ranking isn’t very good
Are you sure? I thought the same but that was just temporary because I was the last one to share my speed, not the one with the best speed.
It’s not, though you should do that too. The reason is that some people only need to translate theme to one language, so buying WPML on their part makes no sense. If you provide po and mo files, you make sure that anyone can translate your themes to any language they need.
That is also pretty simple (you don’t need to create those files yourself, you can generate them), all you have to do is load them in your theme.
Well I’m not sure if it’s required here, but you definitely should do it, it’s very simple.This is example from our themes:
<wpml-config> <custom-types> <custom-type translate="1">project</custom-type> <custom-type translate="1">service</custom-type> <custom-type translate="1">staff</custom-type> <custom-type translate="1">testimonial</custom-type> <custom-type translate="0">slide</custom-type> <custom-type translate="0">view</custom-type> <custom-type translate="0">gallery</custom-type> <custom-type translate="0">video</custom-type> </custom-types> <taxonomies> <taxonomy translate="1">prj-category</taxonomy> <taxonomy translate="0">media-tags</taxonomy> </taxonomies> </wpml-config>
This saves you from supporting troubles later too, not all users are technical.
1.) Make sure that every part of your theme is translatable via WPML
2.) Make sure that you have a place for language switcher defined in your theme.
You don’t have to (and can’t) share plugin via your theme, you just declare compatibility, it’s up to buyers to buy the plugin if they need multilingual setup.