Download: Ahimsa 3.1 for WordPress
February 9th, 2010 by ravi

If you are an Indianapolis Colts fan, take heart. All is not wrong with the world, for now there is a new version of the Ahimsa theme for WordPress. Alright, okay, a new version of some WordPress theme does not equal a SuperBowl ring, but remember, you don’t get to wear a SuperBowl ring but you do get to decorate your blog as you desire!

If you have performed any customisation of Ahimsa (by creating or editing skins, or creating a custom stylesheet custom.css or custom footer footer-custom.css) then please, PLEASE read the section below on Saving your Ahimsa Customisations before you click on the Download button.


Saving your Ahimsa Customisations

This version has some new features and a few very important fixes. One problem with theme upgrades in general is that when they are performed using the WordPress Dasbhoard, WordPress removes the current theme, thus destroying any customisations you might have made (in its defence, WordPress pops up a message warning you of this upcoming disaster). This is a particularly problematic issue for the Ahimsa theme since I support various user customisations in the theme and save that information to the theme directory, and such customisations can be part of what is lost as a part of the upgrade process.

To avoid this problem for future releases, I have moved the Ahimsa customisation files to a different location. This will save you for future upgrades. But what about this one? For that I have written a little plugin that you should install and run before you upgrade the theme. It all sounds very complicated, I admit, but it’s not! See the steps below:

1. Backup your theme

It may be a good idea to backup your theme files, just to be safe

2. Download and install the Ahimsa Fix plugin

Download the plugin zip file and install it via:
Dashboard → Plugins → Add New → Upload

3. Run the Plugin

Run the plugin via:
Dashboard → Settings → Ahimsa Custom Fixer
(yeah, I could have come up with a better name ;-)). Let it do its thing, until you see a greenish box saying All Done. The plugin assumes that your web server has write access to various parts of your WordPress installation. If that is not true, it will print out an error message. You can now safely Deactivate and Delete the Plugin, and go ahead with the upgrade of the Ahimsa theme.

4. Update your Skins

If you created any skins, please update them via:
Dashboard → Appearance → Ahimsa Options
Select “Update Skins” and click on “Save Changes”.

  • Tested: Safari4, Chrome Beta for Mac, Firefox 3.6, IE7, PHP 4.3 and above, WP 2.8 and above
  • Left, Right and No sidebars
  • Quick Fancybox Gallery shortcode
  • FAQinway: FAQ shortcode
  • Use of “theme store” outside theme directory to avoid losing customisation files on theme upgrade
  • Option to disable action/feed box for pages
  • Fix for Firefox 3.6 title alignment issue
  • Updated fade in/out effects to jQuery (fixes flicker issue)
  • Various other fixes

If you are curious about how to use the shortcodes mentioned above, stay tuned for a post coming up shortly. You can see an example of the Quick Fancybox Gallery in the instruction images (clickable thumbnails) above.

Two fixes (the Firefox 3.6 title issue, and a fix for comments code for older WordPress versions) identified by Ahimsa users. I wish I could give them the attribution but I have forgotten who they are. My sincerest apologies to them. I am searching through the comments to find their names.

UPDATE with CREDITS: Caleb Adam Haye deserves credit for identifying and fixing the comments code for old WordPress versions. Mike identified a bug (and the fix for it) in the skin edit code. TheJuice, Nakke, Geakz and Chris Kaczor identified the Firefox 3.6 title rendering issue (Chris took the additional step of filing a bug at GitHub, and Geakz and BigLeague tested Ahimsa 3.1 before release); John Campbell figured out the cause of the problem (an IE specific CSS specification). My thanks are due to all of them, and those I have forgotten to mention (this latter group also deserves my apologies; please identify yourself in the comments), as well as all of you who have found this theme useful and encouraged me with your comments and feedback.



10 Responses  
  • M Ward writes:
    February 16th, 2010 at 11:40 am

    First of all – LOVE this theme. I’ve used it several times and find it to be both visually pleasing and easy to use. However, I have an issue where my blog is stretching so that I have to scroll left and right to read things – which it didn’t used to do. I’ve changed nothing and I experimented with using 3.0 vs 3.1 and that isn’t making a difference.

    The only thing that changed is I have 3 posts saved as drafts, but not published? Could that be doing it?

    Thanks for your help!

    • M Ward writes:
      February 16th, 2010 at 11:45 am

      And it’s working on other people’s computers just fine. I cleared my cache on my computer. So strange.

      • M Ward writes:
        February 16th, 2010 at 2:13 pm

        And (sorry to be such a bother!) the sidebar isn’t working. It won’t disappear/reappear.

  • lango writes:
    February 21st, 2010 at 11:56 am

    hello,

    thx for your work!

    i try a new installation of ashima 3.1 (not a update/upgrade). so i become 2 warnings on the ‘Ashima Option’ page, in a right field in the ‘Ahimsa Skins’ section:

    Warning: array_merge() [function.array-merge]: Argument #2 is not an array in [...]/wp-content/themes/ahimsa/utils.php on line 10

    Warning: Invalid argument supplied for foreach() in [...]/wp-content/themes/ahimsa/functions.php on line 620

    [...] = delete from me

    also under these 2 warnings comes “Unable to read skin file:”

    could you help me?

    lango

  • M Ward writes:
    February 21st, 2010 at 7:31 pm

    After seeing the comment below, I figure it would be more helpful if I told you if there were any errors like that.

    When I both upgraded it and did a fresh clean reinstall, I received these errors:

    Warning: fopen(/[...]/wp-content/themes/ahimsa-3.1-3/style.css): failed to open stream: No such file or directory in /[...]/wp-includes/functions.php on line 3598

    Warning: fread(): supplied argument is not a valid stream resource in [...]/wp-includes/functions.php on line 3601

    Warning: fclose(): supplied argument is not a valid stream resource in /[...]/wp-includes/functions.php on line 3604

    Again, thank you for your work on this! I know it’s not easy and recognize that sometimes errors can occur. You were so quick updating with the Firefox issue – much appreciated!!

  • Chris Kaczor writes:
    February 23rd, 2010 at 12:30 pm

    Thanks for the update – looks much better in Firefox.

    My only issue is the “Ahimsa Options” section is blank now. Maybe I did something wrong when applying the new version.

    • Chris Kaczor writes:
      February 23rd, 2010 at 1:46 pm

      Did some digging through the code and found out what was going on.

      The issue is with the check_store_mksymlinks function in the functions.php file. My web host is using Windows Server 2003 and PHP doesn’t support the symlink function on that version of Windows. It is only supported with Windows Server 2008 or higher.

      I commented out the function for now and I can see the theme options. Everything else seems to be working fine.

      • ravi writes:
        February 23rd, 2010 at 1:50 pm

        Chris, I was just going to respond to your original comment with the suggestion that the symlink might indeed be the culprit. It is fine to comment that symlink creation out. The [only] downside is that you cannot edit your custom files (custom.css, footercustom.css), if any, using the WordPress Dashboard Editor.

  • valkiro writes:
    February 28th, 2010 at 7:47 am

    Hi,
    the first thing I want to compliment the theme, it’s beautiful, I wanted to report a problem with Internet Explorer 8, the central part of the theme too widens going to end up superimposed on the right side column, someone can help me solve my problem?
    I made a screenshot that you can look up http://yfrog.com/5mtemplateproblemp
    Chrome with Firefox and there are no problems, everything is ok

    Sincerely
    Charles

  • Jack writes:
    March 1st, 2010 at 1:19 pm

    Yes, I have the same problem. On Firefox and Chrome the skin looks nice, but on IE it looks awful.

    What is the problem with that on IE?

    Jack


Leave a Reply

»
S
I
D
E
B
A
R
«
»  Substance: WordPress   »  Style: Ahren Ahimsa