9seeds

Building Custom WordPress Solutions | Plugin Development

 

justin

WP Affiliate Manager version 1.5

Posted on

We’re glad to announce the release of WP Affiliate Manager version 1.5.0.  This version initially centered around a bugfix having to do with a namespace conflict in the latest (3.8.9.x) versions of WP e-Commerce.  However in the process, we were able to add several minor enhancements that will enhance WP Affiliate Manager for the future.

gettext translation wrappers

While not all screens have had the gettext translation wrappers applied (notably the settings and paypal pages in wp-admin), everything else has been added.  Expect a 1.5.x release early in 2013 that will be fully translatable.

As such, we’re putting out a call for translators.  We are willing to offer free one-year licenses (with support & upgrades) for WP Affiliate Manager to anyone who contributes a full translation in their own language. We have a couple of people already talking to us about certain languages, so if you’re interested, please fill out the form on our translation page and let us know what language you’d like to help us add to WP Affiliate Manager!

money_format() for Windows

money_format() is a native PHP function, but it does not exist on Windows platforms.  We added a simple one for those hosting in Windows environments which should get the job done.

PayPal enhancements

First, the sandbox PayPal URL has been fixed.  This is mostly used for development/testing purposes, but none-the-less is important.

Also, we removed the requirement for needing the PHP cURL module requirement.  Instead, WP Affiliate Manager uses WordPress’ native HTTP request methods.

jQuery UI Tabs + cookies + mod_security bugfix

An interesting sidenote… we discovered a bug where if you went to the 2nd tab on WP Affiliate Manager’s “My Affiliates” screen on our test server, your next navigation point in WordPress would either result in a 404 error, or an endless loop of 302 redirects.

Turns out the bug was caused by a perfect storm of Apache’s mod_security (which is enabled on our test server) and the use of jQuery UI Tabs with a cookie save option.  What was occurring was the cookie name was being saved as “ui-tabs-1” and if your last visited tab was the 2nd tab (index 1) the cookie was saved as “ui-tabs-1=1”.  This would be passed with each HTTP request as a cookie header.  Since mod_security doesn’t like anything where “1=1”, it was changing the request, causing WordPress to become all sorts of confused.  You can see a bug report about it here: http://bugs.jqueryui.com/ticket/8027

The solution was to name the cookie, so the automatically generated name wasn’t used:

jQuery("#tabs").tabs({
    cookie: {
        name: 'wpam_detail_tab'
    }
});

Enjoy all of the fixes!

Stealing math from Wikipedia

Posted on

WordPress + Jetpack + LaTeX = Awesome

On my personal WordPress website I wrote about an Arduino device I built to help brew beer.  Being my first foray into electronics, I wanted to document my experiences.  One of my difficulties centered around turning electrical values (voltage, resistance) into real-world values (temperature) using math.

As part of my documentation, I wanted to re-create some equations that I had found on a Wikipedia page about thermistors.  While in the process of grabbing their images and putting them into the media library, I remembered something…

One time while on the main Jetpack screen in the WordPress dashboard, I noticed a tile that advertised “Beautiful Math.”  So I looked into it.  Jetpack has a LaTeX module that can accomplish this.  LaTeX is a rather old-school markup/typesetting language that has been very popular in academia, especially in regards to math.

So Jetpack and LaTeX can do math, but I didn’t really want to learn a new markup language, I just wanted to quickly copy & paste the equations into my post.

Good Authors Borrow, Great Authors Steal

So then I wondered how Wikipedia is storing the images or if they’re doing something similar.  Guess what?!?  They use LaTeX too!  Putting the same equation into WordPress is as easy as clicking “Edit” on the Wikipedia page and copying the text between <math> and </math> and pasting it in-between [latex] and [/latex] in WordPress.

Native vs. Shortcode formatting Tricks

Jetpack supports using the $latex $ native format instead of the shortcode, but there are a few noted (and undocumented) differences between using the two methods. For instance, if you want to increase the size of your rendered LaTeX text, you can use the s (size) parameter in your LaTeX equation as such:

$latex \LaTeX&s=4$

Where size in this example is “4.”  However if you try to do this using the shortcode as such:

[latex] \LaTeX&s=4[/latex]

it will render as: [latex] \LaTeX&s=4[/latex] – Not exactly what you’d expect 🙁 The trick is that the following LaTeX parameters need to be fed in as shortcode parameters:

So if you want to have “LaTeX” rendered as:

$latex \LaTeX&bg=ffcccc&fg=cc00ff&s=4$

You can either do:

$latex \LaTeX&bg=ffcccc&fg=cc00ff&s=4$

or  move the size & color parameters into the shortcode tag like this:

[latex bg=ffcccc fg=cc00ff s=4]\LaTeX[/latex]

Converting Blogspot / Blogger to hosted WordPress

Posted on

First Try

Migrating your Blogspot or Blogger weblog to a hosted WordPress installation should be easy.  But you may run into some problems along the way, so here are some quick ways to make it less painful.

When I first attempted this, I used the Blogger Importer plugin found in the “Tools” → “Import” menu of a new WordPress installation.  It went OK.  The importer pulled in all of the posts and the comments, but there seemed to be some extra markup that made it’s way into the posts.  All of the post titles now started with “>”:

>Why Hello There!

Also, while images in the content seemed to be fine, none of the media was actually imported into WordPress, they were still being hosted on blogspot.com.

Resetting the WordPress installation to start over

So now WordPress has a bunch of content that I want to delete so that I can start over and hopefully get it right the next time.  For this I used WordPress Reset.  I was able to use it to remove the (bad) imported content and reset it back to a new installation.  It’s multi-site friendly and only restored the one site and left all the content from the parent and sibling sites alone – although I can’t vouch for what it would do if you ran it on the parent site of a network installation.

A 2-Step Approach

Now that I was back to square one it was time for a different approach.  After some reasearch, someone on the WordPress Forums mentioned using WordPress.com to do the Blogger import, then exporting from WordPress.com as a native WordPress export file (WXR / XML), and import that file into your new WordPress installation.

Importing Blogspot / Blogger to WordPress.com

So over at WordPress.com, everything is like a normal WordPress installation, except they have turned it up to 11.  They have powerful servers, and a dedicated staff that make amazing additions to the most popular free plugins – one of which is the Blogger import.  On WordPress.com you have an additional option to import a Blogger export file:

Rather than authorizing the plugin to get everything from the site, we’ll export it to a file. Log into your Blogger account. When you’re logged in and viewing your blog there’s a “Design” link in the upper right menu bar, click that. Once you’re at the Blogger administration page click the “Settings” menu, and then “Other.” You will have an option under “Blog Tools” to “Export blog”:

Take that file and import it into a new WordPress.com site. You’ll want to make sure that this blog is public (but not necessarily indexed by search engines) as our hosted WordPress installation will need to be able to pull media files from it, but we don’t want it to wind up on Google, as it’s only temporary. It might take a while to fully complete, but WordPress.com should bring in all your Posts, Comments, and Media just fine. Once you’re sure that it’s done, export the WordPress.com site through the “Tools” → “Export” menu, selecting “All Content.”

Importing WordPress.com’s export into a hosted WordPress site

Before we begin importing the content from WordPress.com, two things should be changed in the WordPress Importer plugin‘s wordpress-importer.php file, which can be done through the plugin editor.

Just so we know when the importer runs into issues, change IMPORT_DEBUG to true:

/** Display verbose errors */
define( 'IMPORT_DEBUG', true );

Then to make sure we get everything, find the line that starts with:

$post_exists = post_exists( $post['post_title'], ...

This was on line 539 for me.  Comment it out using slashes:

//$post_exists = post_exists( $post['post_title'], ...

Then just below that line add:

$post_exists = false;

I did this because when WordPress.com imported images from Blogger, it gave them the same name as the post title, So if a post was called “Why Hello There!” and it had 5 pictures in it, all 5 pictures also had the title “Why Hello There!” This was preventing the importer from getting everything. Plus I already reset the installation, so there’s no content to duplicate or overwrite anyway. And I reasonably trust that I want to retrieve everything contained in the WordPress.com export file.

Run your import and everything should go smoothly. After you’ve verified you have everything in your new hosted WordPress installation, you can delete your WordPress.com site or make it private. You may also want to undo the WordPress Importer changes for future imports.