Updating from 1.9.3 to 1.9.4
Simpler and shorter installation: http://www.youtube.com/watch?v=OEeC3f4LxXQ (1:40)
1.9.4 documentation: http://docs.devatic.com/daisho/
1.9.3 documentation: http://docs.devatic.com/daisho/193/
- August 06, 2013 - a minor fix to 1.9.4 has been submitted to ThemeForest. It corrects [Settings > Reading] because auto-installer was setting IDs to pages that may not exist and that was causing "Redirect Loop".
- August 07, 2013 - a minor update that fixes issues from #5930.
- August 08, 2013 - one more update was submitted to ThemeForest. It updates the documentation in the package and style on mobile phones.
To update standard procedures apply:
- Please use Envato's Toolkit plugin to update the theme (please make sure to use "backup" option as well)...
- ...or please rename old theme folder from 'daisho' to 'daisho-backup' and upload 1.9.4 to 'daisho' folder. You can always revert back to 1.9.3 if something will not work in 1.9.4 by switching folder names.
- Please create a support ticket if something went wrong. We'll be able to inform you why is that if the list below doesn't cover your case.
Things that may require some action after updating:
- [Admin Panel > Daisho > General > Homepage] has been moved to [Admin Panel > Settings > Reading]. Blog is your front page by default now. You can set different page template for [Pages > Homepage] and use this as your front page in [Admin Panel > Settings > Reading].
- [Appearance > Menus] doesn't accept single letters in "Description" field to add menu icons anymore. From now on it accepts CSS classes that are listed in the updated documentation.
- Our Team, Services and News pages don't have separate page templates now.
[content_block]shortcode works on the "Default Template" now. It also accepts some content above or below the carousel.
- Shortcodes such as drop caps, highlight, prettyPhoto have been removed. If you were using them, please use plugins instead. You'll find alternatives in "Common Changes" thread.
- Blog posts that didn't have manual excerpt specified will now show in full. We now use the same functions like Twenty Thirteen WordPress theme does -
the_content()by default (reacts to
- If you're using a child theme and if your theme is modified then some places like (a) menus, (b) comments, (c) blog, (d) single post pages, (e) recent projects on classic homepage, (f) content_block shortcode on Services/Our Team pages, (g) basic HTML elements have simpler structure and new and simpler style and CSS classes. These new class names are very likely to stay this way permanently. If you have modified any of these then you may lose these changes and you'll need to update your child theme's style.css to restore them.
- We switched
post_layoutfrom meaningless numbers in the database: 1 (normal), 2 (right sidebar), 3 (left sidebar) to words: left-sidebar, right-sidebar. Some pages or posts may require an update of "Layout" option.
- Custom field for the second title has been removed. Its purpose was to enable users not to specify the second title but we now think that it's a better idea to hide unwanted titles with CSS instead.
- New ThemeForest Review Standards (July 2013) - ThemeForest was accepting items that are not compatible with WordPress's philosophies for a long time and recently they reviewed their submission requirements. It is still being discussed but generally speaking their decision is excellent and Daisho 1.9.4 is in large part compatible with these new standards.
- WordPress 3.6 - Daisho 1.9.4 has been also tested with WordPress 3.6 and we already implemented some of the new functions it brings. Daisho 1.9.4 may not be backwards compatible with WordPress 3.5 but it uses newer, faster and safer functions everywhere.
- Twenty Thirteen - all Daisho's template files have been reviewed and compared to Twenty Thirteen's new structure. We used this as reference and when in doubt we used the same functions in the same form as the default theme to maintain the best compatibility with plugins such as SEO ones, translation ones, caching, shortcodes etc.
Improved: Styled remaining widgets and made the style consistent between the sidebar and the footer.
- Our SEO module was based on Yoast SEO and instead of updating it in the theme with each release we decided to disconnect it and let users decide what plugin they would like to use. We recommend Yoast SEO or All in One SEO Pack. Both plugins come with all the necessary SEO options.
- We updated many places of the theme to consider SEO better now. HTML5 structure of the document has been revised and updated with consideration of 2013's WordPress and W3C standards.
- Facebook sharing has been improved for portfolio projects. It now uses better default data. You can also set your own sharing data with plugins like WP Facebook Open Graph protocol.
the_excerpt() to posts listing pages.
- You can now display full post content that parses HTML.
<!--more-->tag to cut it with "Continue Reading" link.
- Or you can still specify manual excerpt to display something else than the beginning of the post or full post on your post listing pages (recommended).
Added: Page refresh for portfolio projects.
- You can now add/remove
page-refreshclass to force page refreshes everywhere. This can be done in /core/body-class.php (you can remove our action and add your own in your child theme).
- Thanks to this you'll be able to use Google Analytics and shortcodes in portfolio projects.
Added: Normal header everywhere.
- Compact header appeares on page that have
compact-headerclass added to the body. You can remove it from all pages in /core/body-class.php (you can remove our action and add your own in your child theme).
- Thanks to this you can have the normal header on all pages, including blog and single post pages. It doesn't work for portfolio projects though because they display two headers at the same time.
Added: Upgraded comments.
- Comments structure has been updated from XHTML to HTML5 output introduced by WP3.6.
- Comment form now supports all pluggable action hooks.
- Dynamic "Reply"/"Cancel Reply" button that moves comment form to the appropriate place.
- New layout that allows insertion of additional form fields.
- Avatar support.
Added: Upgraded menus.
- Custom menu walkers have been removed from /core/nav.php. We think that they are not a good idea because some plugins like WPML add their own menu items and they skip custom walkers for some reason. We now use native WordPress function
wp_nav_menus()in its unmodified form which will contribute to better plugin compatibility.
- Animations have been removed. In the long run instantly opening menus (like in default WP themes, Themeforest.net and other large services) are more enjoyed by visitors. We're aiming professional look rather than flashy one.
- Removed separators and added flat style.
- Removal of custom menu walker means that the "Description" field for icons can no longer be used. We added support for icons added via custom CSS classes instead.
Added: Child Theme.
- Creating one is a couple of minutes of work but now it will be a couple of seconds because you can download it (daisho-child.zip).
- Some people noticed that /modules/ folder can't be overwritten in a child theme (without dequeuing scripts). From now on /modules/loader.php considers that and it allows overwriting folders.
Added: Replaced Custom Sidebars Module.
- The old built-in sidebars module was removed.
- It now comes as an optional plugin (WooSidebars) that will work when you switch themes.
- The new plugin has more sidebar replacement options. Previous module allowed users to replace sidebars on single posts and pages only.
Added: New mobile mode.
viewportmeta tag was set to
device-widthinstead of fixed
640px. That's the only solution to make it prepared for devices between mobile phones and tablets and for netbooks with smaller screens.
- To disable responsiveness you can simply get rid of the
viewportmeta tag in header.php.
- Moved most CSS @media queries to the bottom of style.css and other style files.
- New mobile menu and a version without floating header (this makes the theme compatible with pretty much any mobile phone and tablet with any system installed (not only iOS, Windows and Android).
Added: We're going in the flat, classy, simple and professional-looking style direction.
- Although elements like this http://gyazo.com/8666b6d8014cd9ba094abb2ae6a5ace3.png are alright, they are not suitable for majority of users and projects. Most of you need uniform, consistent, simple, clean, clear, flat and professional-looking elements and not flashy and bulky tables with gradients.
- Therefore, we decided to give up on this design and introduce something better. Flat and simple elements are much lighter and easier to be modified in a child theme. They are also easier to be used in RTL mode. CSS3 gradients, shadows and double separators were simplified.
- Entire website now uses font weight of
400(bolder) instead of
- Shortcodes that will work: tabs, accordion, toggles, Vimeo, Youtube, HTML5 Video, Google Maps, Our Team/Services Slider, Widget Area in Content.
- Shortcodes that will not work: drop caps, prettyPhoto, highlight.
- Shortcodes that the new plugin adds: boxes, highlights, dividers, callout boxes, pricing tables, skillbars, columns that are compatible with Daisho's old columns and more...
- New ThemeForest submission requirements and all-time WordPress standards require most shortcodes to be available as plugins. We removed a few libraries and shortcodes from the theme files but most of them will still work if you install "Symple Shortcodes" plugin that we decided to use for now as a replacement for our shortcodes. The plugin is included in the package and will auto-install.
front_page from [Daisho > General]. From now on please use [Settings > Reading] to pick a static front page with "Portfolio Template" selected. In addition "Classic Homepage" is now a page template and not a built-in core script.
Removed: template-blog.php and
flow_blog_page from [Daisho > General]. From now on please use [Settings > Reading] to pick a blog page. Front page is a blog page by default since 1.9.4 like in Twenty Thirteen default WP theme and most other themes. Portfolio is no longer a core module - it is a separate page template.
Removed: template-news.php. From now on please use
[content_block post_type="news" posts_per_page="15"] shortcode on a standard page.
Removed: [Daisho > About] - reason: it has no real value or functionality other than being an "information page".
Removed: [Daisho > Blog] - reason: an option to limit posts per page is now available in [Settings > Reading].
Removed: [Daisho > Slideshow] - reason: it consisted of only two options. Now the slideshow comes with preferable default options.
Removed: "Custom Footer Code" - reasons: (a) it required us to enable unfiltered HTML code and (b) exactly the same thing is allowed in a child theme in a better way (via action hooks) - hence, usage of a child theme is now preferred and required for custom modifications.
Removed: prettyPhoto library.
- There are multiple lightbox solutions available as plugins and we don't want to force users to use any particular one. Furthermore, the
[gallery]shortcode is often chosen over lightbox plugins.
- Lightbox as a plugin has more options and is updated more often. Plugins' authors are focused only on this module so they are likely to make it work well on the newest versions of browsers and on the newest devices.
Removed: Custom backgrounds.
- Please use Background Per Page or Background Manager instead. The changes you will make with these plugins will remain on your pages regardless of the theme you use and both plugins have more options.
Removed drop cap and highlight shortcodes. Both are rarely used and both are doable with plugins which is preferred. - done
Thumbnails didn't have - done
post_class() added to them.
When 'Our Role' is too long, the title may wrap. - done
Theme's screenshot.png needs smaller logo. - done
Changed bold and strong HTML tags to have - done
font-weight of 700.
UL and OL lists now can be used with paragraphs inside and marings will adapt correctly. - done
SuperSlide now automatically converts projects from old structure (2012) to the new one (2013). - done
Admin panel file uploader was disregarding image size chosen by the user. It now picks the correct size. - done
SuperSlide color sampler now supports "no color" as well. Still no - done
rgba() support (only because we use WordPress' color picker and it doesn't support it yet but it should soon).
Slides shortcode has been moved from /modules/ folder to /admin/superslide/ folder. - done
Smaller thumbnails on blog don't generated line break - #5382 - done
- #3081 - done
- #3550 - done
- #4076 - done
- #4272 - done
- #4401 - done
- #4758 - done
- #4814 - done
- #4862 - done
- #4915 - done
- #4922 - done
SEO for homepage - #4974 - done
- #5273 - done
- Ship Child Theme for Daisho and make it easier to dequeue and overwrite Parent Theme functions - #5172 - done
Pagination for posts and pages - done
Blog as homepage - #2442 - done
Switching languages from compact menu - #2690 - won't fix (4 alternatives instead) (added support for language switcher as menu item which was missing)
Alt tag for portfolio images - #2512 - done
Search for mobile phones - #2763 - done
Double tap for thumbnails on touch devices - #2765 - done
Ability to put content above and below content_block shortcode - #3033 - done
- #3068 - done
- #3059 - done
- #3341 - done
- #3216 - done
- #3279 - done
- #3568 - done
- #3566 - done
- #3585 - done
- #3604 - done
- #3598 - done
- #3729 - done
- #3617 - improved
- #3771 - done
- #3818 - done
- #3826 - improved
- #3878 - done
- #3952 - done
- #3943 - done
- #4017 - improved
- #4230 - done
- #4558 - improved
Comments on Portfolio post - #3984, #3923 - can't fix
#2175 - won't fix
#4842 - improved
#4941 - improved
- #4670 - done
Add more custom fields to post editing screen - #4525 - postponed to the next version in which we'll be focused specially on this aspect
Add buttons with background - #3685 - done
Introduce simplified mobile mode for less common systems and devices - #5492, #3879, #4856 - done
- Add icons shortcode - #4181 - shifted to the next version