Sales have been affected for those in Popular page as well. Let’s not worry about it though. The football fever is on at the moment. Here’s something relevant you might be interested in: https://www.linkedin.com/today/post/article/20140608160051-25760-understanding-the-frenzied-interest-in-soccer-s-world-cup
it would be an ideal time to work on another product or take a vacation yourself.
Though, some sort of testing regarding search results is happening, because on codecanyon this is what can be seen in the source code of the page with any search results:<meta content="original" name="WT.new_sorting_method_test" /> <meta content="100" name="WT.sales_boost_test" /> <meta content="control" name="WT.qs_branch" />http://awesomescreenshot.com/0ea2vkf52f
So: what we see now in the search results is from some temporary branch, displayed with the purpose to see how this affects the sales??
Whether it was this or the blink tag change, it was mighty impressive. @madlep: Any idea if it will come back again?
We at ThemeSphere are looking for a talented person to join our Support Team. The ideal candidate will answer our WordPress theme support queries, while ensuring customer satisfaction. Do note that quality customer support is our top priority. Before applying, make sure you really are up for a challenge!
What do we ask of you?
- Outstanding English Communication Skills (reading and writing). Really, there’s no exception here.
- In-Depth HTML & CSS3 Knowledge. Ability to use tools like Firebug or Chrome Inspector is vital.
- WordPress Knowledge Required: Ability to customize themes, work with plugins, and general expertise at using WordPress.
- A general willingness to go the extra mile where required.
- Willing to spend adequate time to learn every little detail of our WordPress Theme.
- Ability to always keep your cool and help beginners with proper respect.
If this sounds like you, get in touch with us by sending an email through our profile. Please include a brief about yourself, previous work details and experience, asking hourly rate, and your contact details.
If you’re using this combination, the Google web fonts might not render on Chrome 33 (until refreshed or a big dynamic DOM change occurs by something like a slider). This was a hard issue to track when it occurred a few days back. So I thought I would share it here to save some time for other authors.
There’s some layout painting issue that occurs in Chrome 33 with the way FitVids.js inserts its dynamic stylesheets in header. The fix is shared in this issue: https://github.com/davatron5000/FitVids.js/issues/159
Edit: It’s not limited to Google fonts. It almost applies to any web font.