Damn, I’m in London 10 days earlier, would love to come
Some other time.
If everything stops working on 1.10.2 you should really question your code.
It’s bad practice to deregister jQuery and load your own version because I as a WordPress developer, whose product might be installed besides yours on some WP page, need to know that if I detect WordPress version X, that there will be jQuery version Y in use.http://pippinsplugins.com/why-loading-your-own-jquery-is-irresponsible/
I know I may be getting on your nerves, I’m sorry but I encountered the following problem – after writing version 1.2 in the XML for a test, I reverted back to version 1.0 but the update notification continues to stay showing that I should update to ver 1.2.
I tried changing the file, the file directory, clearing the browser cache but it still continues to show that a newer version is available and shows information from the old XML :\(Sorry for the double post)
Add this to your theme’s function.php
delete_option( 'notifier-cache-last-updated' );
Reload and notification should be gone. After it is, remove the code.
IE 8 won’t die so fast, since it’s used on WIndows XP which I believe does not support IE9, but I might be wrong.
Anyways, I have a direct experience at home. My mom works for the government and ofc they use Windows XP and IE on the job, so when I tried to install Chrome on her home pc, it failed miserably, cause she does not like it.
Such people are not interested in fancy features or CSS3 support, they are just used to the position of browser controls and don’t like the change very much.
Until a definite block is put to IE8 access, it won’t die any time soon.
Finally someone else noticed it too
You didn’t extract actual plugin from the downloaded .zip.
Once you download .zip archive from CodeCanyon, extract it and in there will be another zip containing plugin files which you need to upload instead.
Sorry I had to report your post, your image is resized, it should be in 1920×1440 resolution.
Phase One – taking effect for new items on September 9th, 2013
Phase Two – Tentatively taking effect for new items November, 2013