Category Archives: Featured

Chrome Rendering Bug

There is a rendering bug in the Google Chrome browser that makes Ryuzine nearly unusable causing pages to display in blocks with some parts missing, some parts of the pages are transparent, and pieces of the User Interface are missing.

Whatever is causing it appears to only be affecting a very, very small number of websites and webapps, Ryuzine being one of them.  The bug has been present in Chrome for at least the last 10 versions.  It’s probably safe to say Google is never going to fix it.  The problem *only* exists in Chrome and the “blink” based Opera browser.  IE, Edge, Firefox, and Safari all render Ryuzine without issues. However, Chrome users represent a not insignificant number of people on the Internet, so at this time we are recommending turning some Ryuzine features OFF in order to better accommodate them.

Our best guess at this point is that layering too many CSS effects on top of each other triggers the problem, as disabling certain effects seems to minimize the problem or make it go away entirely.


  • iScroll – there is an issue with iScroll being “sticky” and for left/right mouse clicks to have become reversed after a recent Chrome update.

A number of other issues with iScroll have also arisen in recent browsers.  Until these are addressed you should disable it in your publications.

In your static Ryuzine publication “Config File” remove those two Add-Ons from the ones being loaded.  In Ryuzine Press you can do this from the Ryuzine Press –> Options –> Add-Ons section, simply uncheck iScroll in the list and Save the settings.

Note: iScroll is a third-party script created by Matteo Spinelli and maintained by  Ryuzine simply supports iScroll integration.  Ryu Maru is not involved in the development of iScroll, and the iScroll developers are not involved in Ryuzine development.

If you still notice problems with Ryuzine rendering, also consider disabling:

  • 3D Page Turns
  • Page Shadows
  • Depth Effects – the added layer of CSS shadows makes the Chrome rendering problem worse.

Ryuzine Version 1.1 is in the works and will completely change how the pages are handled, reducing the number of layered CSS effects, which will hopefully address this problem once and for all.  Until then, please use the work-around above or inform your visitors they should turn off those features themselves after loading your Ryuzine publications.

Next version of Ryuzine?

“When will the next version of Ryuzine be released?”

This is a question that has come up a couple of times recently, especially from those who’ve noted that none of the files on GitHub have been updated since August or September of 2015.

Well, the simple answer is, “when it’s necessary.”

We don’t follow the software development idea of “release early, release often.”  Ryuzine updates have historically been driven by updates to the web browsers in which it runs, either to fix something the browser update broke or to take advantage of a new browser feature.  Since the release of Ryuzine 1.0 we haven’t become aware of any browser updates breaking the webapps, nor have any “killer” features been introduced that we think Ryuzine should take advantage of.

Furthermore, Ryuzine 1.0 heavily modularized the webapps, with more formerly integrated features now made optional in add-ons.  The flexibility of the Add-Ons API would allow the webapps to utilize new browser features without requiring the core code to be updated.

In conclusion: If it ain’t broke, don’t fix it. 😉

Ryuzine + Chrome + Mac = System Freeze [FIX!]

There is an issue being experienced by some users of Chrome on Mac OS X when viewing a Ryuzine publication.  What happens is the publication displays with glitchy graphics and any attempt to interact with it will cause the entire screen to glitch and the system to freeze, requiring a hard reset.

This is a known, recurring bug in Google Chrome involving hardware acceleration on some versions of Mac OS X, beginning with Mavericks.  Note that this is not a problem with Ryuzine or exclusive to viewing Ryuzine publications.  Other hardware accelerated web content can also trigger this problem.

Here is the work-around to prevent it from happening in the future:

  1. Type “chrome://settings/” in your browser’s address bar.
  2. Scroll to the bottom and click “Advanced Settings” to expand it.
  3. Find the “System” section and UNCHECK the “Use hardware acceleration when available” if it was already checked or CHECK it if it wasn’t (in other words try it both ways).
  4. Restart Google Chrome
  5. Return to the Ryuzine that crashed your system, it should no longer cause screen freezing.

However, the display of the Ryuzine publication may still be very blocky/glitchy!  This has also been observed in Google Chrome for Android.  Here’s how to fix that:

  1. Open the “Options” panel and look for “Depth FX” in the Add-Ons section.
  2. Make sure the switch is set to “OFF”
  3. If it’s still glitchy turn “Page Shadows” off as well.
  4. If it’s still glitchy turn “3D Page Turns” off too.
  5. The absolute last ditch effort is to turn off “Page Animations” as well.

You may need to change these settings for multiple publications if they are on different domain servers.


Purple for Prince

Music legend Prince sadly passed away yesterday.  At the time of this writing an autopsy has been performed but a cause of death has not been made public, all we know for sure is he was found unresponsive in an elevator and couldn’t be resuscitated.  Around the world landmarks like the Eiffel Tower, Niagara Falls, the Empire State Building, as well as many peoples’ social media profiles, are being redressed in Prince’s signature color: PURPLE.  Ryu Maru is temporarily going purple as well.


Ryu Maru is headquartered in the Minneapolis-St. Paul area of Minnesota.  Prince Rogers Nelson (June 7, 1958 – April 21, 2016) was from Minnesota, and though such a huge star who literally could’ve lived and worked anywhere, he chose to live here and he chose to build his studio here.  This is where he helped create the “Minneapolis Sound” in the 1980’s and solidified Minnesota’s place on the musical map.  He then spent the decades after not only on his own art but nurturing other artists, writing songs for them, producing them, and giving many of them exposure at parties he’d occasionally hold at his studio estate named “Paisley Park.”

Unless you were living under a rock in the 1980s you likely remember when his landmark “Purple Rain” hit, but it’s all too easy to forget just how HUGE a hit it was.  At one point he had the top album, top single, and top movie in America all at the same time!  He was the first artist to ever achieve such success.  “First Avenue,” the club in Minneapolis, is in many ways a historic venue because of Prince, having gained world-wide notoriety in the film “Purple Rain,” but it wasn’t just a movie shooting location – Prince actually performed there many, many times (however, despite popular misconceptions, he didn’t actually own the place).

Comic book fans will remember his amazing soundtrack to Tim Burton’s 1989 “Batman” film, fittingly titled simply “Batman.”  The scene with Jack Nicholson as “The Joker” defacing famous artworks wouldn’t be the same without Prince’s music blasting from the very 80’s “boom box” of a henchman character, incidentally, named “Prince.”

However, Prince’s music video for the song “Partyman,” in which he appears as “The Joker” himself, in many ways outdoes Nicholson’s performance in the movie.  (You may want to enjoy that video above before it gets pulled, Prince was notoriously protective of his work online and there’s no reason to believe his Estate will be any less so after his death).

He later performed what many consider one of the best Super Bowl half-time shows ever, in the middle of a Miami downpour.  Where other artists may have cancelled the show or waited for the rain to stop, Prince reportedly said “can you make it rain harder?”  When he performed he was always “all in” and many music fans agree he was arguably the best live musician of their lifetime.

He never forgot his roots, never thought he was so important he had to travel everywhere with security or an entourage (in fact the day before his death he was seen by himself riding his bike near his home on a trip to the drug store), and he never acted like he was too big to encourage the talent of others.

But Prince WAS a “big deal” to many people, especially here in Minnesota – not just because he was a rockstar, but because he was one of us, he chose to remain one of us.  You couldn’t grow up here or live here without knowing who Prince was, or without hearing at least some of his music.  When the Minnesota Twins baseball team’s new stadium opened they played Prince’s “Let’s Go Crazy” after every home run.  It’s a tradition for veteran players on the team to make sure rookies know all the lyrics to “Little Red Corvette.”  In 2010 the Minnesota Vikings football team streamed “Purple and Gold” on their website, it was a “fight-song” Prince wrote to support his local team in the NFL playoffs. That same year he let 89.3 “The Current” premiere his new single “Cause and Effect” as a gesture of support for independent radio, as the station is part of Minnesota Public Radio.  According to disc jockey Mary Lucia the station would occasionally get calls from Prince asking what artists he should try to book for his next Paisley Park party?  Prince performed multiple times at the radio station’s annual “Birthday Party” held, of course, at First Avenue.   But Prince was also enigmatic, somewhat reclusive, very private, and had this “magical” air about him, possibly best summed up when he dubbed himself “The Purple Yoda” in the lyrics to “Laydown.”

It’s fitting that his actual given name was “Prince” because he was regarded as “Rock Royalty” in Minnesota, and obviously not just in his home state – as the tributes to him from around the globe attest.  He will be missed, though perhaps nowhere more deeply than here in the place he called “home.”

Ryuzine 1.0 is HERE!


It has been a long time in the making, but Ryuzine 1.0 is finally HERE!  Not only is is practically a complete rewrite of all the Ryuzine apps, they are now completely OPEN SOURCE and FREE for personal and commercial use.



Almost 100 Changes!

This massive update has been in the works since February 2014 and fixed or changed so many things we decided to just skip over a bunch of “beta” versions and jump right to version 1.0 – in total there were nearly 100 changes to the three Ryuzine webapps and the Ryuzine Press plugin.  For more details make sure to check out the individual product pages:

Ryuzine Reader
Ryuzine Writer
Ryuzine Rack
Ryuzine Press



The Write Stuff

The biggest changes came to our Ryuzine Writer authoring webapp bringing it more in line with the features you’d expect from a page layout program.  Not only is there better handling of styles and stylesheets, the new “Page Manager” makes it easy to add, delete, and rearrange the pages of your publications.  The “RackBuilder” can also now preview newsstand catalogs in the Simulator, the Simulator has been updated with profiles for newer, popular devices, and when everything looks the way you want the “Package Builder” has more and smarter options than every before.

The Ryuzine Press plugin has also seen some improvements that make it easier than ever to turn curated blog posts into engaging Ryuzine Press Edition publications.  The plugin has also been updated and tested with WordPress 4.3.  The Ryuzine Reader and Ryuzine Rack webapps are now bundled with the Ryuzine Press plugin download from our website – you are no longer required to do a separate installation of the webapps.


Publishers can learn all about how to use either the stand-alone Ryuzine Writer or the Ryuzine Press plugin by reading the manuals – which were written WITH their respective programs and presented in Ryuzine format:

Ryuzine Press 1.0 Publishers Manual
Ryuzine Writer 1.0 Publishers Manual

Refined User Interface

All of the Ryuzine apps now have a much simpler user-interface that no longer requires users to “slide” through multiple toolbars to get to the button they want.  Those buttons all now use an “icon font” instead of images for crisp display regardless of the device resolution.  Ryuzine Reader has better swipe detection and the “Page Slider” has also been improved.

Updated Phone UI Nav Bar

Updated Phone UI Nav Bar

New Themes

Ryuzine Rack with custom theme and branding.

Ryuzine Rack with custom theme and branding.

All the changes to the User Interface required rewriting the existing themes and creating new ones.  The “Urban” Windowsand “Mobile Fruit” iOS themes got much-needed updates, and Android gets the new “Paperbot” theme.  Some of the older “Platform Themes” have been dropped since they not only looked outdated but few people even use those devices anymore.

Ryuzine Writer also now gets its own themes and theme creators can choose whether or not they want to support Writer with their themes or not.  Moving the Writer styles into their own stylesheet allows the Reader/Rack themes to be simpler and the smaller files load and render more quickly than the old themes did.

The theme system now also supports creating “child themes” that build upon another theme, so you don’t have to write styles for everything in your custom themes.

New Add-On API

In the beta versions only Ryuzine Writer had optional add-ons.  In version 1.0 the Add-Ons API has been completely rewritten and is now part of both Ryuzine Reader and Ryuzine Rack too!  Features that were previously “baked in” have been broken out into optional add-ons and it’s never been easier to extend and customize Ryuzine.

Free & Open Source

One of the biggest changes to Ryuzine is that now everything is completely open source.  Ryuzine Reader, Writer, and Rack are released under the MPL 2.0 license, Ryuzine Press is under a GPL 3.0 license.  All the code is available for developers in our GitHub Repository.  Non-Developers can continue downloading preconfigured, bundled versions from our website.

Ryuzine 1.0 Update Later in 2015


This post is to reassure you that we haven’t forgotten about the promised major update to the Ryuzine webapps – in fact they are well on their way for a release sometime later in 2015!  Instead of releasing the incremental changes this upcoming release will jump right to version 1.0!

Above you can see the app icons have also undergone a visual overhaul, but the webapps themselves are all undergoing massive rewrites – with so many changes and new features the change-log already goes on for pages.  What sort of changes?  Well, for starters the User Interfaces have all undergone a lot of simplification.

User Interface Updated

You’ll no longer need to hit the “More”  and “Less” buttons to slide controls left and right – all the buttons are now presented on one Navigation Bar:

Updated Phone UI Nav Bar

Updated Phone UI Nav Bar

Behind that “Share” button is also a completely rewritten social media sharing widget, and in addition to still being able to drop in your own widget the third-party “Add-Ons” API from Ryuzine Writer has been completely rewritten and will also available in both Ryuzine Reader and Ryuzine Rack.  That means adding your own custom dialogs and panels, but previously built-in features like the “Lightbox” are also going to be broken out into optional add-ons, making it easier for third-party developers to expand or replace them.

Page Manager & More

One of the biggest changes coming to Ryuzine Writer is the new “Page Manager!”  Here’s a look at it in action:

"Page Manager" panel in Ryuzine Writer's Editor

“Page Manager” panel in Ryuzine Writer’s Editor

 Professional page layout programs used in the print media industry allow the designer to easily see how their pages lay out in relation to one another, and easily add/delete and drag-to-reorder the pages.  All of those features will be available in the new Page Manager panel, as well as the ability to change the size of the page thumbnails, show individual or facing pages (either left or right bound), and a “continuous” view in the editor that is a much better representation of the same view within Ryuzine Reader.

The editor will also support “Master Styles” which can be changed without having to refresh the browser and reload Ryuzine Writer.  Issue-specific styles can also be loaded, previewed, and unloaded within the editor.  If you are using PHP File Operations in the editor the Image Insert no longer creates a pop-up window that may be blocked by browsers.

The “Package Builder” has also undergone a major rewrite and will also offer the option of packaging into a plain folder instead of a ZIP archive.  This is useful if you want to make manual additions or changes to the package or plan to immediately FTP it up to a website for viewing rather than offering it as a downloadable publication.

We could literally go on and on listing everything in the change-log but we’ll hold off until the actual release.

Ryuzine is Going Open Source!

We’re still looking through the various open source licenses to find the one that fits us best, but you read that correctly – version 1.0 of all the Ryuzine webapps will be released under an open source license.  This will completely replace the current  Commercial and Non-Commercial Use licenses.  That means with version 1.0 there will no longer be a requirement to purchase a license for commercial use!  ALL of the source code will eventually be available on GitHub, with each webapp and add-on in its own repository.  Once that has happened anyone and everyone can contribute to making Ryuzine even better!  Since it will be a little confusing for non-developers to grab and assemble all the files from multiple repositories, will remain the place to download the pre-packaged webapps.

So When Can You Get It?

One of the factors in deciding to take Ryuzine open source is that, since the beginning, there has only been ONE developer working on it as a side-project, even as the “family” of webapps has grown.  The first step was a “code audit” to make sure all the code that will be released CAN be released under an open source license.  Then there were all the UI changes, updating themes broken by the UI changes, bug fixes, adding new features, breaking built-in functions out into add-ons, rewriting the Add-On API, and lots and lots more that still needs to happen.  Our best guess is that it will be ready sometime in the Spring or Summer of 2015.  Until then you can still download version of Reader/Rack and Writer and of the Ryuzine Press plugin for WordPress.

Ryuzine Press Already?!

Yep, that’s right, another update!  This one has some pretty neat stuff in it too that make it worth the update.

The biggest change this time around is that you can create a “Custom Configuration” that is applied to a specific Edition.  This over-rides any settings on the “Options” page.  For example you can have some Editions that are right-bound and other that are left-bound, or offer Editions in different languages – with the entire webapp UI customized for that language.

Editions now also support attaching a “Featured Image” to them, which can be used as the cover image both for automatically generated covers and within Ryuzine Rack or the standard custom post-type Archive page.

The templates no longer have to be installed/uninstalled from the active theme.  They are now implemented as dynamic templates regardless of what theme may be activated.

And the last big change is new support for another webcomics plugin, Manga+Press 2.7.5 – a nice and simple comic management plugin with a bundled child theme.

If you already have Ryuzine Press installed, look for the update notice on your Dashboard or Plugins page.  If you haven’t installed it yet go get it here  😀

Full Changelog:

  • Hiding of cover headers and footers wasn’t working properly, that has now been fixed
  • Reset settings on deactivation option wasn’t working correctly, that has been fixed.
  • Install to theme no longer necessary, now uses automatic template substitutions.
  • Ryuzine Rack is now enabled by default. Control has been moved from Tools > Update tab to Options > Ryuzine Rack tab.
  • Ryuzine Rack stylesheet errors have been addressed.
  • “Featured Image” for Editions is now supported, however, it doesn’t offer the same level of control over how displays the image:
      • “Featured Image” does not support cover “bleed” settings. It is always included as a regular image, not a background image.
      •  If “Cover Image” is set to Ryuzine Reader always look first for the short code, but if it doesn’t find one it will fallback to “Featured Image.”
      • If “Cover Image” is set to “Featured Image” Ryuzine Reader will ignore any shortcode and always use “Featured Image.”
      • Ryuzine Rack always looks for a shortcode first, if it doesn’t find one it will then look for a “Featured Image” and if it doesn’t find one it uses the “Image Not Available” placeholder.
      • “Featured Image” and can be different images.
      • Standard Ryuzine post archive (if Ryuzine Rack is disabled) will only use “Featured Image” (if attached) as Edition thumbnail.
  • Ryuzine List Widget updated to support “Featured Image” for cover.
  •  Custom Configuration can now be done per Edition, which over-rides default configuration under Ryuzine Press > Options tabbed pages (however not all the options are available under each Edition, just the ones you’re most likely to want to change).
  •  Ryuzine Press > Options > Addons now uses drop-down lists to select webapp themes from those that are actually installed (prevents you from entering an invalid theme name). You can modify this list by adding/removing themes from the ~wp-content/plugins/ryuzine-press/ryuzine/theme folder (you will need to do so via FTP or your web host file manager).
  • Support for another webcomic plugin has been added for Manga+Press Comic Plugin version 2.7.5.
  • Back-end now uses the WP 3.5+ Media Manager instead of the old “thickbox” one.
  • Fixed problem where changing slug name in Comic Easel caused Ryuzine Issues column to vanish from comic post management page.
  • Fixed “fopen failed to open stream” error on Tools page “Plugin Details” that occurred before the webapp was installed to the plugin.

Update Notes:

If you are updating, and not installing fresh, you should go to “Ryuzine Press > Tools > Update” and see if you need to manually uninstall the files from your current theme.  Updating a plugin does not fire the activation or deactivation hooks, so it won’t have run the function to automatically detect and remove the files.  Alternatively you can manually deactivate and immediately reactive the plugin from the “Plugins > Installed Plugins” screen to fire the hooks for the automatic removal function.

You do not need to reset your settings, but there is a new one on the “Options > Ryuzine Rack” tab for enabling or disabling Ryuzine Rack.  Select one or the other and save to update your settings database.

Ryuzine Press Update

Here’s what is in this update:

  • This release fixes an integration problem with the Comic Easel plugin that prevented the “Ryuzine Issues” column from being added to the Comic Easel “All Comics” bulk edit post management screen, and then added two instances of the drop-down filter list.
  • Another incompatibility issue with Comic Easel was that Ryuzine Press automatically created a “Ryuzine Rack Category” taxonomy with the slug “comic,” which is also the custom post-type used by Comic Easel. Rather than force Comic Easel users to change the default post-type for their comics, Ryuzine Press now creates that taxonomy as “comic-book” (and changes it to that if you had already defined it). This only automatically happens when the Ryuzine Press plugins is activated, otherwise you will have to manually edit the slug on the Ryuzine Press > Rack Categories screen.
  • The minimum WordPress version supported by the plugin is now 3.5 and a compatibility check has now been added with an admin message if you are running something too old.
  • This version of Ryuzine Press was also tested with and is compatible with ComicPress 4.1
  • The plugin itself used to be a single file, which has been getting crazy long which was both bad for load times and maintenance. That has been broken up into multiple files now with more attention paid to what NEEDS to load in a given context.
  • The “Ryuzine Press Editions” widget now has an option to restrict the size of the latest edition cover thumbnail, and the image is coded with a classname so you can custom style it with CSS if you want full control.
  • The link to the official forums was also fixed on the Tools page.

Updating from

  1.  Go to your WordPress admin “Updates” page.  If it doesn’t show the update for Ryuzine Press you may need to manually have it “Check Again” to see it.
  2. Once you see that the update is available use the automatic update function to install it.
  3. Immediately after you install the update you will have to go to Ryuzine Press > Tools > Update Ryuzine and reinstall the Ryuzine Webapp to the plugin.
  4. Uninstall and reinstall the files to your theme.
  5. If you are using external issue-specific stylesheets use the bulk regenerator to rebuild them.

Updating from earlier versions:

  1. Download the ZIP file, unzip it, and FTP it to your ~/wp-content/plugins/ folder and overwrite the existing one.
  2. Go to Ryuzine Press > Tools > Update Ryuzine and install the Ryuzine webapp to the plugin.
  3. Uninstall and then reinstall the files to your theme.
  4. If you are using external issue-specific stylesheets use the bulk regenerator to rebuild them.
  5. From now on you won’t have to FTP updates, you’ll get automatic updates like any other WordPress plugin. 🙂

Note: there is not yet a update for the Ryuzine webapp, but the version numbers of the plugin and the webapp do not need to be the same.

Ryuzine Update Available!

Yes, we had said this update was going to get skipped but there’s just too much good stuff in it (particularly for Ryuzine Press users) to make you wait until the major update is ready.

The “iScroll” script injection has also been removed from Ryuzine Reader.  This was only ever intended to help auto-update existing publications produced before Ryuzine had “iScroll” support.  That was quite a while ago, plus the injection didn’t always work properly, so it has been removed.  If you still have an old configuration file, though, this version of Ryuzine will just ignore it.  Please load any old publications into Writer and update them, but if you don’t those publications will just go back to their original “native” (default) scrolling.

Ryuzine PDK

Go get it on the DOWNLOAD page!

The PDK includes the stand-alone versions of Ryuzine Writer, Ryuzine Reader, and Ryuzine Rack.  This is a maintenance update incorporating all the post-release patches from the previous version including:

04 October 2013 Patch
* Bug fix that prevented new installations of Ryuzine Press from running the web app
* Fixed bug that made Options switches and most in-page links unclickable in IE 10+

28 October 2013 Patch
* Fixed “Save” and “Package” failures in Ryuzine Writer

01 November 2013 Patch
* Patched Ryuzine Writer and ePub Add-Ons

07 December 2013 Patch
* Ryuzine Rack unclickable options switches in iOS 6 and 7 fixed.

The “short page” error in Chrome has also been fixed (same fix as previously applied to Opera and Internet Explorer).  The problem is that the browsers process the javascript that calculates the page height faster than they reflow the CSS, so the pages ended up showing pages that were usually too short (though sometimes too long, but regardless the height calculation would be wrong).  Now it recalculates after the CSS reflow for the browsers that have been messing it up.

Ryuzine Press Plugin

AUTO-UPDATING – yes, we now have a plugin update server in place to notify and deliver updates to Ryuzine Press just like any other WordPress plugin.  You won’t have to manually FTP updates to your blog site anymore.  However, the auto-update process does wipe out your Ryuzine Webapp intallation, so you’ll have to go to the Ryuzine Press > Tools > Ryuzine Update page and re-install the webapp to the plugin and you should also UNINSTALL and then re-install the single-ryuzine.php and/or archive-ryuzine.php files to your current theme (to make sure they are in sync with the plugin update).

Ryuzine Press > Tools > Resources now has an info-box with a summary of the installation version and status.

“Ryuzine Issues” replaces “Categories”
This plugin no longer uses the regular Blog categories to organize what goes into each Edition. A quick explanation of the difference between  “Issues,” “Editions,” and “Collections” :

Ryuzine Issues – this is a hierarchical taxonomy just like the blog categories, but separate from it. A blog post can belong to multiple issues.

Ryuzine Press Editions – this is a type of blog post that includes one or more “Ryuzine Issues” within it. Typically it should only be one issue per edition, but you could create an Edition that collects a number of issues.

Ryuzine Press Collections – this version now allows Editions to be assigned to more than one Issue, which means you can collect multiple issues into a single Edition forming a “Collection.” Keep in mind, however, that this can potentially create very large publications that may take longer to load than most people are willing to wait, could have load times exceeding the standard 30 second server timeout (returning an error), and “Collections” can easily exceed the browser cache limits of mobile browsers on phones and tablets (which, by design, automatically crashes the browser on iOS devices). So, yes, Collections are now possible. With great volume comes great responsibility!

This new taxonomy is added to the regular Posts and also Comic Easel (if activated).

A new drop-down is added to Posts, Ryuzine Press Editions, and Comic Easel Comics admin management lists so you can FILTER by Ryuzine Press Edition.


“Tags” have also now been enabled for Ryuzine Press Editions.  This can be used for searches and filtering from the “blog” side of your site.  The tags, however, are completely ignored by the Ryuzine plugin and webapps.

The single-ryuzine.php file now performs fewer database query loops, which (in testing) sped up load times by 3x on average.

Better ComicPress & Comic Easel Integration

Thanks to some help from the author of those great plugins Ryuzine Press now works even more seamlessly with them:

No-Click Pages – in prior versions if you had “Click to Next” or the lightbox feature turned on in either ComicPress or Comic Easel all the comic pages in the Ryuzine Press Edition were also clickable, which was a usability nightmare on touch devices constantly mis-firing. The only fix before was to turn those features off, but that was a site-wide change. Now Ryuzine Press grabs the comic image directly without any link wrapped around it.

No ComicPress or ComicEasel Flash/Motion comics, galleries, or Lightboxes – these were never tested in Ryuzine Press and most likely wouldn’t work. Ryuzine has it’s own built-in lightbox system, galleries would use jQuery that doesn’t load with Ryuzine, and Flash is a unsupported format on mobile devices Ryuzine targets. Rather than have them display but not work properly they are now simply unsupported.

No code hacks – The code hacks to Comic Easel should no longer be necessary. The plugin attempts to handle it automatically, and now it uses a custom taxonomy instead of “categories” anyway.

The ComicPress 2.x “Comic” column is no longer added to the Ryuzine Press Editions management list (it served no purpose there anyway other than taking up space).

Auto-generated Cover Featured Links Fixed

These used to be off by one page, which is now fixed. They still use the regular Blog “Categories” to determine what is considered “Featured” – so if a post belongs to the current Ryuzine Issue and is also in the Featured category selected in the options it will be used as a auto-generated cover link. In other words the “Featured” category is independent of the Issues taxonomy.

NEW WIDGET – in previous versions if you wanted to show a list of Ryuzine Press Editions in your blog’s sidebar or footer you had to use a third-party plugin. The one we were recommending is apparently no longer being developed. So now Ryuzine Press has it’s own custom Widget for displaying a list of Editions. It can also display a link to the Ryuzine Rack Newsstand (if you’ve installed it to the theme).

NEW SHORTCODE – there is now a shortcode for embedding a Ryuzine URL in a post or page just like you embed videos from YouTube. It also features a dialog box from which visitors can copy and paste an <IFRAME> embed themselves. You can also use this to embed your Ryuzine Rack newsstand. Just use format or and that’s all you need! However you can also set the size=“small|medium|large” or set the height and/or width in pixels or percentage. Lastly, you can also embed the link so it automatically goes to a specific page with page=“n” where “n” is a page number. Embedding Ryuzine Rack is as easy as – neat huh?

Mobile Banner Ad setting was apparently broken for a while, now fixed.

Language Localization has been updated to take advantage of the newer, simpler language selector and offers more languages from which to choose (this had been changed in the stand-alone Ryuzine apps a while back and got overlooked in Ryuzine Press until now).

Ryuzine Rack for Ryuzine Press Improvements:

Media Categories now works properly and uses a custom “Rack Category” taxonomy. You are also no longer limited to the six predefined categories. Replacing the “Media Category” label edit boxes is now a drop-down list of all the Rack Categories from which you can pick a “default” one that will be assigned to a Ryuzine Press Edition when published (you can over-ride this on the Ryuzine Press Edition Post Edit screen).

This same drop-down list also appears on the Tools > Rack Builder for each entry in your custom Rack Catalog.

The aforementioned “Rack Categories” has its own section where you can edit and customize these non-hierarchical categories. On the “All Editions” post management screen there is also a new column showing you what Rack Category each Edition is assigned to (if any) and a drop-down allowing you to filter by Rack Category. These categories are only used by Ryuzine Rack. If you aren’t using Ryuzine Rack you can just ignore them.

Ryuzine Press Migration Assistant Plugin (NEW!)

If you have been using previous versions of Ryuzine Press you probably have a bunch of Editions already published.  When you install version it will break all your existing Editions!  You need to “migrate” existing Editions from the old “Categories” system to the new “Ryuzine Issues” taxonomy.  However, that can be a lot of work if you have a lot of Editions and/or Editions with a lot of posts assigned to them.

So we have also created a “Migration Assistant” plugin! << DOWNLOAD IT!

Download, unzip, and install it via FTP to your ~/wp-content/plugins/ folder and then activate it.  You’ll see the “Categories” column re-appear on your Editions management page and there will also be a new “Migrate” option on the bulk processing drop-down.  Simply tick the checkbox next to the Edition(s) you wish to migrate, select “Migrate” from the drop-down, and press the “Apply” button.  It will automatically create a new “Ryuzine Issue” entry, transfer the Edition and all the posts to it, and (optionally) delete the old Category.  Once everything is migrated you can deactivate/delete the migration plugin.

+Comic Easel Autofix

If you have a WordPress powered site for a webcomic and have switched to the Comic Easel plugin and/or updated to ComicPress 4.x you may have noticed that your Ryuzine Press Editions that should include comics no longer include comic posts after the upgrade.

This is because Comic Easel uses a custom category type called “Chapters” that are only associated with the custom “comic” post-type.  Pages are assigned to Ryuzine Press Editions by being included in the same category as the edition, and since Comic Easel/ComicPress 4.x comic posts never exist in normal categories there is no way to assign them to editions without “hacking” the Comic Easel files to allow it.  Two different hacks are outlined in the Ryuzine Press manual, but now there is an (experimental) automatic fix!

Go get the latest Ryuzine Press ZIP file.  If you just want to patch an existing installation (which is likely if you’re reading this) all you need to do is overwrite:


with the same file in the ZIP archive you downloaded.  You do not need to update the Ryuzine webapp, nor do you need to reinstall anything to the theme (unless you just installed ComicPress 4.x or a new child theme, then you will need to go to Ryuzine Press > Tools > Update Ryuzine  and install to your theme.  If the files are not in the currently active theme it will prompt you to install them).

What this does is check for the custom post-type “comic” and then checks to see if the “Comic Easel” plugin is activated and then attempt to automatically add the regular “Category” selector to Comic Easel so you can assign comics to a Ryuzine Press Edition.  Please be aware this is experimental, it may not work if Comic Easel initiates later than Ryuzine Press, it won’t work if you have set a different custom post-type in the Comic Easel settings.  If this auto-fix doesn’t work for you then you will need to do the manual hack outlined in the Ryuzine Press Manual, which unfortunately needs to be repeated after every Comic Easel update.  If the auto-fix does work for you it should continue to work even after a Comic Easel update.

If you are still using ComicPress 2.x you do NOT need this update!

Note: ComicPress and Comic Easel are developed by Philip M. Hofer (aka “Frumph”).  Please do not direct any bug reports or support questions to him regarding how Ryuzine Press works (or doesn’t) with his plugins and themes.