Hope my issue was not missed? Results for ‘university’ are dominated by ‘universe’ and ‘universal’... Excluding terms in query would be useful.http://audiojungle.net/search?utf8=%E2%9C%93&term=university
New search results for University include Universe and Universal:http://graphicriver.net/search?utf8=%E2%9C%93&term=university
There are probably more word groups with similar problem.
> Unauthorised activity occurs on a credit card (...) PayPal or Moneybookers account
So correct me if I’m wrong:
Someone is using stolen credit card information or hijacked PayPal account (obtained via viruses, trojans, hacked websites or other means…) to buy themes. And until the real owner of the card (or payment processor) notices there is no way to do anything about it (because nothing suspicious) and then it is too late.
It reminds me of the gold days of shareware… piracy.
EDIT: Well, there is also possibility that automatic fraud prevention system marked the transaction as suspicious (not history of buying digital goods on the internet…) or something like that… Have someone investigated it?
Anyone knows how Envato reviewers are dealing with it? With so many themes around they need to have some nice testing automation…
ChapterThemes saidYES, but testing with different physical devices is always very humbling experience with all kinds of strange issues showing: slow or choppy animation on older hardware, colors looking different on non hi grade graphic displays, fonts missing, patches/updates for IE not applied, links too small to click on some phones etc etc …
@ZxxxZ nice explanation. I just need the ability to check different IE browsers. Now i can but on different machines. And i’m not planning to always have like 3 machines available for IE testing.
I’ve never seen that modern.ie website. So i can get images for use with virtual box just like that? And test the different browsers?
Yes, similar images were once available on microsoft.com page and required some more magic to work in Linux, now Microsoft is trying even harder to make it easier to people to test compatibility. Backward compatibility was always a big thing for them, which ironically is partially responsible for all the headache IE is giving us now… introduce one bug back in IE5, now you need to carry it forward or people will blame YOU for breaking their broken page.Once there was a Linux LiveCD (so no installation required!) that contained number of exotic browsers, emulators and scripts to install IE – so you only would ever needed (in theory…) to run only it for testing, But the last release is 2 years old http://susestudio.com/a/ppX0Yr/browserbox .
Touch events etc. i think does need to be tested on devices like the ipad itself.
Now what you really need is automation. See: 10 browsers * 15 pages * 7 resolutions * 3 pixel densities * 2 orientations * 3 operating systems * huge number of feature like touch * some content variations (with images/without/short text/long text/no text/...) = a lot of testing
Of course final testing should be done by humans (preferably more than one human) but some testing needs to be done along the development. Some people say: just build it in chrome and add ‘rest’ at the end – this is good solution, but sometimes can result in unexpectedly long time spend in fixing issues with other browsers (not only IE) at the “end” of development.
Personally I’m in favor of splitting design into semi-independent aspects like: base typography, layout (including breakpoints), “theme” (colors, fonts, shadows, gradients and textures…), and components (menu, footer, sidebar, comments, etc…) – and trying to find issues as soon as possible at each step. Some CSS methodologies like SMACSS may be of help here.
I’ve heard some people utilize lot of automation with tools like Selenium – so tests run without human interaction, there are automatic lint-like tools to spot some cross-browser issues, http://csste.st/tools/ lists some of them – I was very impressed by this http://www.youtube.com/watch?v=WY3C6FHqSqQ (go to 21 minute and watch for 5 minutes).
But I’m yet to incorporate all of that into my workflow – time savings may be huge but so is initial investment:( There was also some service that records you testing your web page and “reruns” it in several browsers looking for glitches, but I’ve forgot the name:(
Testing being hard and time consuming is partially the reason why people are turning to prebuild components and frameworks.
Would love to read how others are testing things!
You can legally download disk images with IE6-10 for testing from http://www.modern.ie/en-US/virtualization-tools#downloads . There is even version for Linux, working with VirtualBox. Setting it all up takes some time, effort and disk space, here is helpful script https://github.com/xdissent/ievms for Linux if you are into that sort of thing:)
To test ‘retina ready’ without any iDevice use latest Firefox, go to about:config and change layout.css.devPixelsPerPx to 2.0 to emulate Apple devices, or any of ‘CSS pixel ratio’ values from that page http://en.wikipedia.org/wiki/List_of_displays_by_pixel_density to check Nokia, LG, HTC, Samsung, Sony, Blackberry…
My real question would be: what are you actually testing/looking for? Different resolutions, different DPI, fonts installed, base font sizes, mouse/touch events, smoothness of animations and scrolling, z-index issues, grid problems, ... ?
Do you have some kind of dummy content with all these weird issues users create: looooong multi line titles, suprlonggermanwords, images with strange sizes, ill formated paragraphs, menus with too many items, empty lists, lists-tables-etc with even|odd|0|1|100 number of elements… ?
There should be some kind of wiki, where themeforest authors could share stuff like that, workout some standards and easily keep it up to date!
- at least 30% increase in sales meaning there are some themes with more than 30% sales increase after adding multilingual functionality,
- it does not say anything about themes with that functionality build-in from the start (so change in sales could not be compared)
- 3x more sales is about the whole market, not only themes which added multilingual functionality after some time.
- also we do not know how well those reported themes were selling before adding that functionality – they could be like 1.5x the average for example (eg. theme regulary updated by author)
Any way I would believe both claims.
I kind of agree with Cubell, but there is also this http://s04.flagcounter.com/more/ceGa/ (stats from one of popular WP themes, not mine, hope it’s OK to post it, link was in theme description) at least 30% of visitors – and probably more! – are from nations that do not use English as official language!