Jishnu 1.1.0 released

Just uploaded the latest version of the theme. Here are a few of the changes:


1. Long title/tagline support (smaller font size option)

Jishnu 1.1.0 - New header text sizes


The first is an optional “small” title/tagline size, configurable in the customizer. Here’s the gist:


2. Changed comments from “Written by” to “Comment from”

Jishnu 1.1.0 - Change to comment text.

I wasn’t thrilled about having to make this change (“Written by” sounded more like a tight-knit community to me), but this was to address an issue in Google’s handling of “Authorship” detection for Google Plus. When the comments said “Written by”, Google’s Structured Data tool would get confused and think that one of your commenters was actually the author.

Previously, if Jack Bauer commented on your post, his comment would be prefixed with Written by Jack Bauer, and the output from the tool would look like this:

Email verification has not established authorship for this webpage.
Email address on the website.com domain has been verified on this profile: Yes
Public contributor-to link from Google+ profile to website.comYes
Automatically detected author name on webpage: Jack Bauer.
Error: Author name found on the page and Google+ profile name do not match.


The change to “Comment from” (as seen in the picture above) should hopefully address the issue.


3. Flexibility in author link.

Jishnu 1.1.0 - Flexibility in the author link

You can find this in the Jishnu Advanced Options.

One of the downsides to the way Arjuna X (and Jishnu) showed the author was it would automatically link to that author’s posts. For example, in the situation below…

Jishnu 1.1.0 - previous author behaviour


…clicking on that circled part would bring you to //www.website.com/author/johndoe/

That led to a few issues:

  1. If this was John Doe’s personal blog (no other users), it was usually a useless link because for most bloggers, the results are exactly the same as going to the main page and browsing through all the posts that way.
  2. Because of #1, search engines would often see this list of posts as “duplicate content”.
  3. That /johndoe/ part by default is usually the same as John Doe’s login-name. So for the bots that go around to WordPress sites trying to break in and hack the site, they now don’t have to guess the username! They’ll just use johndoe as the username and only have to guess the password now! WordPress sets up that #3 part by default, and they don’t make it easy to change (you usually have to edit the database or find a plugin to make your user_login different from user_nicename).


Because of the potential security issue and other pitfalls, if you already had “Include the author of a post/page” enabled, upgrading to Jishnu 1.1.0 will just use the TEXT for the author name (no link). You can change it back to the old way in the Jishnu Advanced Options if you want, but I strongly suggest making sure your password is VERY strong if you go that route. Alternately, you can edit the user_nicename in your WordPress database so that it isn’t the same as your login (although a strong password is still a good idea too!).

You may have noticed in the image that it can also link to a website. The link in that case will be whatever you have set in the WordPress Users/Your_Profile section. It’s the easiest way to add your Google Plus profile link to the page. Just remember to set it as https://plus.google.com/000000000?rel=author where the 0000 stuff actually points to your google plus profile.

It’s not just for Google Plus though – if you have multiple contributors, it’s a nice way to let them have control over where clicking their name will go. They can set it to a personal website, or if they’d prefer it links to their posts, they can manually put in the website.com/author/johndoe bit.

Finally, for the “Text before author name”, it’s completely optional. Having “by” in there is supposed to be helpful for Google Plus detection, but leaving it empty looks a little cleaner. What you use is up to you.

4. More CSS in the head (technical)

Jishnu 1.1.0 - more CSS in the head

Ok, this isn’t really a feature…

It’s good if people only visit 1-2 pages on your blog per visit (less data).
It’s bad if people visit lots of pages on your blog per visit (more data).

So why do it…? Due to the way most CSS/JS combining plugins work, the spritesheet that Jishnu uses (to keep total images for the theme at a grand total of ONE which is under 5KB in size… /flex), well… that image sprite is often lost in translation. It can’t be addressed directly within the CSS file, but WordPress itself can spit out the absolute paths necessary. So that’s what I’ve done.

Since I’m already spitting out so much in the head at this point, I moved everything to do with the fancy CSS headers there too so that people don’t have to download ALL that code via the CSS file – they only have to download the code for the stuff that YOU have enabled, although that ends up in the HTML of every page.


5. A little more under-the-hood cleanup

I had submitted the theme to WordPress, but quite a few changes have to be done for them to accept it as a theme they’d put up. Things were quite a bit less strict when the original Arjuna X was available on the WordPress theme section, and so I’m slowly working through it all. You’ll probably see some of the changes come about with additional versions of Jishnu, although if I run into any major snags, I’m ok with it being something only available on my site.


Final note

As the theme becomes more and more complex, it’s becoming increasingly advantageous to use:

Serving compressed content is probably the most important part, because pages are quite large without it which can make it a little slow for anyone on cellular or dialup. Most web hosts have it enabled, and caching plugins often enable it when possible too.

The caching plugins themselves are going to be very helpful as well. Without them, every time someone visits a page, Jishnu has to check to see what options you’ve enabled as it generates the file. There are hundreds of decisions that are made by the theme (never mind all the ones WordPress itself and your plugins have to make!) before each page is generated for each visitor. This only takes a few milliseconds on most servers, but on a slow overloaded server it can actually take a bit of time. Using a caching program, it only has to do this once, and then it can serve the file to dozens, hundreds, or even thousands of visitors.

Autoptimize isn’t an absolute critical necessity, but here are some fantastic things about it:


Download Jishnu 1.1.0

You can grab this version of Jishnu here:

jishnu-1.1.0.zip – Jishnu v1.1.0 (Jan 7, 2014)

If it’s way past Jan 7 2014, check the main Jishnu page for the latest version.

Be sure to back up your existing install (and database) before upgrading.

The safest way to upgrade your install is usually to rename the existing jishnu folder to something like oldjishnu and then (quickly) upload/unzip the new one to your site. Log in to the admin section and make sure everything looks ok. That way if something went amiss, you can usually just delete the new jishnu folder and rename the old one back to jishnu.

Another way to upgrade is to delete the existing Jishnu theme and then upload the new one through WordPress. Normally your settings all stay the same (they stay in the database and are upgraded when you activate the new version), but make sure you remember what your old Jishnu settings were just in case!

Leave a Comment

You can use an alias and fake email. However, if you choose to use a real email, "gravatars" are supported. You can check the privacy policy for more details.