Congratulations ThemeBeans! Your portfolio and work is more than perfect…
Well this has been an issue for years. The homepage layout needs to be changed to allow more exposure – it’s as simple as that. The site has used the same structure for years now while the marketplace continues to expand. The result is there is a massive separation between elite authors and regular authors. Elite authors will high sales on popular files have an a monopoly and it will be virtually impossible for any new author to achieve their success. Why? Because of the tiny exposure window, and with all the focus on the popular files page, that income is used to advertise and market expensive campaigns that most would not afford to drive further exposure to those files which only increases their sales and broadens the gap between top sellers and regular authors.
Time for a reality check, do we honestly think a handful of items are pulling in millions of dollars in revenue because they are just “really good” files or do we not see there is huge monopoly on this market place, and those Elite’s won’t even question the system, because it works perfectly for them. Envato also drags their feet because they’re just generating the same amount of income regardless of which authors its coming from.. but at the end of the day regular and new authors, and new talent and ideas are being denied a chance to enjoy making money here.
I think we’re all getting tired of seeing the same old files for years on the popular files pages across all networks. Time for Envato to start being a little bit more innovative and deliver up to date and relevant content. It’s time to see some new ideas, new talent, new files, more opportunities for everyone.Power to the people!
@ThemeBuddies – It was like that out of the box if you followed SyamilMJ’s instructions and used the correct theme. Yes, this is BB-Press with a few additional plugins
@mailmilisku – You’re welcome!
Great achievement, guys! You’re doing a great job! We love your designs. Keep creating!
We’re glad it is of some help
superb, can i just swap your plugin for the the original plugin? iv got it running on my website and would love to use this?
Yes, you can but you’ll have to re-enter your API Keys in plugin settings again as the original DB fields were renamed.
Fantastic! I was waiting for a smarty pants to do something like this. How about a blog post on how you connected to the other API. It would be the first as far as I know of.
You can have a look at the source-code on the GitHub pages. It’s a simple wp_remote_get() to the remote server and then handling the response JSON which is returned by the API.
Really great feature. I remember we missed couple times withdrawal date so this comes really handy.
PS: we can add & remove more swift accounts but what about do the same for Payoneer? Now it’s possible to use just one and that’s it. Would be really cool to be able to manage multiple Payoneer accounts.
We’re fans of SyamilMJ’s Aqua Verifier WP Plugin. We were able to set up our support forum very easily using the method he suggested and the purchase verifier functionality is awesome.
We recently needed to add support for a new API of a different marketplace. We therefore used SyamilMJ’s work and extended it to support this marketplace and prepared it for future marketplace additions as well. Since we got it all for free, we wanted to give back and we’re sharing it with you, guys. Hope it helps anyone.http://plugins.ishyoboy.com/purchase-verifier/
Eyo yo yo, IshYoBoy speakin’! Greetings to all you fellaz.
We’re also a small team of geeks. Our roots and cooperation started in Bratislava although we’re in different countries right now.
Nice to meet you all!
Seems to be an official WP 3.6 Bug and according to the ticket below:http://core.trac.wordpress.org/ticket/24994
The solution would be to remove the 2nd line from “wp-includes/js/jquery/jquery.js”. Although this is a very nasty practice (editing core files) it seems this will be the solution i the next update based on the issue tracker above.
/*! jQuery v1.10.2 | (c) 2005, 2013 jQuery Foundation, Inc. | jquery.org/license //@ sourceMappingURL=jquery-1.10.2.min.map */to:
/*! jQuery v1.10.2 | (c) 2005, 2013 jQuery Foundation, Inc. | jquery.org/license */
How are you guys solving the issue on your side?