1.9.5 is an update that incorporates more WordPress 3.6 features than we managed to implement in 1.9.4. Updating from 1.9.4 to 1.9.5 should go smoothly.
Bug: fixed date archives (bug since 1.9.4)
Bug: fixed author archives (author link) (bug since 1.9.4)
Bug: fixed width of content-none.php (bug since 1.9.4)
Bug: fixed "Upload" field in admin panel - it wasn't working well with videos
Improved: switched from our
[youtube] to WordPress's native video and audio shortcodes and its improved embeds (many more services are now supported). WordPress 3.6 introduced native
[embed] shortcodes and Audio/Video API so our ones are redundant at this moment.
Improved: moved nav.php to /core/nav.php (and switched pagination and post navigation to better functions).
Improved: mobile mode (comments area, blog)
Improved: iPad's viewport
Improved: rtl.css - it's still not a full solution but the next iteration makes it 75% ready.
Improved: randomizing thumbnails (now more "small" are chosen to leave less empty gaps).
Improved: moved project-script.php to /modules/isotope/portfolio.js and got rid of PHP in that file.
Improved: cleanup of /modules/library-isotope/portfolio.css
Improved: removed SuperSlide
- We no longer see a reason to keep SuperSlide for this project. It was developed when WordPress 3.4 was the newest WordPress version available and its Media Library looked like this: http://gyazo.com/1e9f482120e6558fbbb1c39f751a73bd.png (not very convenient, no bulk upload, no reordering). WordPress 3.5 introduced this Media Library: http://gyazo.com/c8e7aaa64ac1e82bab8e91dda74f6dea.png and we started to consider removal of SuperSlide because this new media manager introduced functions such as reordering, bulk uploader and clean interface (we created SuperSlide to have these). Half of the SuperSlide Editor was removed back then. Now, once WordPress 3.6 is out with new Audio/Video API and native
[embed]shortcodes, removing SuperSlide brings more benefits than keeping it.
[slide]shortcode will remain in the package for a long time to maintin backwards compatibility.
- SuperSlide removal benefits for users:
No functions are gone:
- You can still insert images easily using WordPress's "Add Media" button.
- You have drag and drop uploader there like before.
- You have ability to reorder images like before.
- You have slide description like before.
- You have
alt=""tag like before.
- The time needed to insert media is similar.
New functions that wouldn't be otherwise available:
- More alignment options (left, center, right, none).
- More linking options (none, attachment page, large image).
- Attached images are marked as attached to certain posts in "Media Library" which helps manage them in the long run.
- Instead of supporting Image/Vimeo/YouTube, new WordPress 3.6 Embeds allow you to insert media from like 20 more services - WordPress Embeds.
- New native WordPress's 3.6
[embed]shortcodes made us delete our
- Only thanks to SuperSlide removal you can manipulate various YouTube/Vimeo and other settings such as: (a) start at 0:10, (b) enable HD, (c) disable "related videos" screen, (d) change player color's for Vimeo players, (e) create non-fullscreen video player etc.
- You can now write there any text, columns and even shortcodes (if you enable page reloads) which was made difficult or impossible with SuperSlide. Projects in Daisho looks like standard pages so now you can edit them like a standard page.
- Its WordPress's feature which means that (a) most users are familiar with that and (b) it will react to plugins that extend "Media Library".
- SuperSlide was what 90% of people needed and most of you didn't need to ever insert there anything more than a couple of images. Its simple interface is a good advantage but this isn't sufficient for 10% of people.
- WordPress's native Vimeo and YouTube players don't maintain 16:9 pixel ratio on lower resolutions. SuperSlide was doing this. This is not a limitation of WordPress but HTML. It isn't a big issue though and it happens on all themes (including Twenty Thirteen) that use WordPress's new Video/Audio API.
Improved: moved portfolio captions below images
- Although previous captions on images were visually attractive, in HTML captions have always been doable below elements rather than on top of them and there are good technical reasons behind that: (a) they can be longer this way, (b) they won't cover or overlap images, (c) dark text on dark images or white text on white images is sometimes problematic, (d) this is the only solution that will work for small screens and videos.
- On mobile devices and for videos captions have always been present below images due to small screen size and conflicts with videos' controls. We now decided to make it consistent everywhere.