Thanks everyone – we are looking into the sort and filter issues now – will let you know when we have a fix.
Still not fixed… Similar issue happened when you released item comments search and @madlep solved it very quickly http://themeforest.net/forums/thread/item-comments-search-is-live/115860?page=3#940935 Please call @madlep to fix this also, if @madlep is not in vacation…
Eh, wouldn’t it have been more beneficial to allow buyers to search comments rather than authors?
which comment search for buyer that you refer here? it is already available. item search comment feature has been released, and it is dedicated for buyer. now, they improve it to enable comment search for authors also on author dashboard…
EDIT: michelle beats me to answer it…
it is very nice idea… we will play with this…
if there was a chance that staff could had missed the comment NOW they will see it for sure.
You know, they are watching, they are following, they are listening. It is impossible they could miss any post on TF forum now. If there is no reply on it, it means they are still discussing about it…
I will surely miss PrimaThemes. Bold author!
Miss you too Typps…
As Ruben said is not allowed, but since no one is watching (imagine staff losing time checking github and compare with code in item sold here) you are relatively safe, except now they know you do it so expect the envato SWAT team to knock on your door
Hahaha… I always enjoy reading your comments.
Rules can change. So, I clicked “Request Staff Reply” on my own comment above. Lets see what Envato will say on this thread…
I think we need to make it clear first.
First Case: If it is complete product and you sell it here, you can’t put it on public Github repo. If it is available for public on Github, then why you sell it here and why buyer have to buy it here.
Second Case: If it is only partial code that exists in your theme, you are free to make it available on public Github repo, as long as it is not your “full” product. It is your code.
This time, some authors already do this because of updated WordPress Theme requirements. We extract some codes from our themes and make it portable into a plugin and some of us make it available for free to download from our website or WordPress repository. And of course creating public Github repo for this plugin is also totally acceptable.
NOTE: When dealing with Envato Support, we have to be as clear as possible… I am serious… We can get different answer by only using different sentences…
Congrats for your 2 sales now…
don’t know about that charity part, doesn’t seem correct if you have financial problems
Some people believe that, “The MORE you give the MORE you GET!”... Of course you will not give 100% of your money for charity, but 2.5% is minimum…
We are on DigitalOcean also now…
There are many types of “multilingual” website in WordPress.
1) Manage multilingual posts in one post per language. Translations are then linked together, indicating that one page is the translation of another.
Plugin: WPML http://wpml.org/ (paid)
2) Store all languages alternatives for each post in the same post.
Plugin: Qtranslate http://wordpress.org/extend/plugins/qtranslate/ (free)
3) Link together separate WordPress network (multisite) installations for each language by pinging back and forth.
Plugin: Multilingual Press http://wordpress.org/plugins/multilingual-press/ (free&paid)
Which one is the best? It depends on what you need.
If you want to make a simple multilingual, you can go with Qtranslate.
If you want complete solution, including multilingual woocommerce, you can go with WPML.
If you don’t want to see lock in effect – when you disable our plugin, all sites will still work as separate sites without any data-loss or garbage output – then you can go with MultiLingual Press.