Kontera Control Being Updated: Would you like me to test with your theme?

October 22nd, 2007

I’m updating Kontera Control to work with Wordpress 2.3 and address pesky issues that Tricia of Feverish Thoughts and Loren of Today’s Gizmo’s alerted me to. Guess what? You can help me.

If you use Kontera Control and have experienced any problems or observed any strangeness, please:

  1. Describe the problem.
  2. Tell me the name of your theme.
  3. Describe any widgets or other plugins you use — comments and categories widgets and plugins are usually the most crucial ones for me to know about. (If you don’t know your plugins and widgets off hand, I’ll ask you by email.)

Why will this information help me? Consider what happened with Tricia’s Theme.

Tricia had an issue with Kontera ads appearing in posts in the ‘Sponsored Category’ after she widgetized her site using the Raindrops theme — the plugin had worked before widgetizing.

Deactivating the widgets did not cause the error to go away. (It’s odd the error doesn’t go away when you de-widgetize … but… whatever.)

By testing Kontera Control using Tricia’s theme on my test blog, I discovered the precise incompatibility which is: The Rainbows widget somehow fills the global “comment variable” (called $comment) in a way that causes it to be “true” even outside comments.

This is a bit pesky, and caused my Kontera Control to fail, because I anticipated that “$comment” would be “false” outside comments. Silly me. :)

(Turns out it’s very, very easy to work around this. But, I need to figure out precisely what went wrong first.)

Anyway, if you are having an issue, give me as much detail, and as soon as possible. That way, I can get the fixed version of KC out by Friday, (which will make Tricia very happy!)

Ten Useful Rules for Buying Paid Links: How to get good ROI for your campaign.

October 21st, 2007

Have you ever thought about what you would want if you were buying a paid review through a service like the Pay Per Post marketplace? It’s worth thinking about if you ever considered paying to advertise your blog.

In the PPP marketplace an advertiser does not hand select from the 70,000 available blogs. This saves time and cost. But if an advertiser doesn’t hand select blogs, can they come up with effective ways to filter out blogs that provide a poor ROI?

I don’t know. But, I’ve been thinking about what I consider to be “best practices”, which I group by function:

Rules about posting frequency

  1. At least 2 posts in the seven days prior to my paid review.
  2. No more than 3 posts on the day my review runs.
  3. No more than 14 posts in the seven days before my review.

Why? I want some minimum posting frequency to ensure that the blog is active; at least 2 posts the previous week should do this. I also want to ensure my post remains visible for a reasonable period of time; fewer than 3 posts they day my post runs will generally ensure this.

But why no more than 14 posts in the week before my article runs? The PPP marketplace is restricted to single author blogs; many of high quality. It also contains quite a number bloggers who also blog for PayU2Blog, V7N, Smorty, and a large variety of different services.

I may be mistaken, but I believe some of these sneak back-to-back paid posts run past the PPP reviewers; one of the hall-marks of those running back-to-back-to-back paid posts is a very high posting frequency. I also believe these blogs will give poor ROI. I think restricting an OPP to blogs with fewer than 14 posts/week will eliminate most of these blogs.

External Rank Guidelines

  1. Alexa rank below 500,000.
  2. If blog existed at the time of the last Google Toolbar rerank, PR 2 or greater.

Why? Well, let’s face facts. Any blogger who is monetizing is trying to apply SEO practices at least a little. PPP already requires blogs to be at least 3 months old. Posties know other posties, and all install Alexa toolbars. If a blog in in the PPP system and has an Alexa above 500,000, there is a serious risk it has no traffic at all (or it’s a very inexperienced blogger.)

If their PR is less than 2 after a Google Toolbar rerank, there is a serious likelyhood the have no quality back links and very, very few people value that blog.

Rules related to links

  1. No sitewide ‘Postie Roll’ link.
  2. No sidebar or footer links to “PayU2Blog”.
  3. No more than 2 links to gambling, mortgage, loans, credit cards or insurance sites on any pages displaying my post.
  4. Post before and after mine may not link exactly one external domain.

Why? I would want to create rules about links that either a) minimize the number of bloggers who have achieved their PR almost exclusively by gaming the system or b) riddle their blogs with paid links.

The “Postie Roll” is described at the PPP boards, and is simply an agreed on link exchange with a large number of other posties. It’s appearance on a sidebar may suggest that blog’s Google PR is gamed to higher than truly deserved.

The other three rules pertain to a blogger running constant paid links.

PayU2Blog is a service that emails bloggers a list of links to include in blogs. The posts need not be relevant, there is no requirement to space out posts. The result is loads and load of paid links which devalues the values of any individual link.

Likewise, ads for mortgages, loans, credit, casinos, poker or anything associated with those industries are the hallmark of heavily monetized blogs.

And why the curious requirement that the post before and after mine not contain links to exactly one external domain? When advertisers do pay for a link, they generally insist on specific links pointing only to their domain. Zero external links, quite obviously, is not a paid post. But, strangely enough, two or more external links is almost never a paid post.

Rule about categories

  1. Post must be placed in at least one ‘non-sponsored’ category that maintains a “followed” archive.

Why? Heck, I want to be maximize the likelyhood that my post remains visible on the web and ends up in an archive with other decent posts. So, I insist it goes in a category that, hopefully, contains some unsponsored posts!

What would you ask for?

Well, it’s Sunday. So, with some luck, readers have a bit of time to tell me what criteria they might insist on in a PPP post. Or, maybe debate whether or not these criteria are either over-restrictive or under-restrictive.

Then, if I figure out the best set of criteria, I may someday actually buy some reviews through PPP. :)

Five Important Tips When Upgrading to WP 2.3

October 19th, 2007

Like many bloggers, I’m in the process of upgrading their Wordpress to the new version: WP 2.3. For many bloggers, upgrading will be a snap. Others will find their upgrade is technically just fine, but some plugins and widgets don’t work. Finding substitutes will take time.

So, it’s probably a good time to learn some tips for ensuring that you can maintain full functionality while you upgrade Wordpress. I’ll include steps the WP developers don’t tell you!

  1. Most plugins that deal with Categories and Tags will break.
    WP 2.3 totally restructured the way it deals with categories and tags. Nearly any plugin that uses categories and tags in any way will almost certainly break.

    If you absolutely one of these plugins to work, do not upgrade until after the plugin author announces that specific plugin works with WP 2.3.

  2. You should create a “test blog”.
    A test blog is nothing more than a near duplicate of your regular blog. Create it at your host; its own database so you don’t “stomp” on your main blog when you test upgrading. Then install the same theme and plugins you use at your regular blog. Write a few “test” posts just to have something in the database.

    How is this used? I pre-test every plugin or widget I download on my test-blog. That way, I can identify any incompatibilities without risking taking my real blog down.

    The test-blog is especially important during major upgrades, because there is a strong possibility that a few of the plugins you use will no longer work as advertised. If you upgrade the test blog first, you maintain your old blog while testing all plugins, widgets, theme changes and pretty much everything before upgrading your public blog. This helps you identify incompatibilities, and also gives you time to identify substitute plugins for your real blog.

  3. Wrap all ’special’ ‘template tags’ calls in “if/else” blocks.
    During upgrade, you will often turn off plugins. When you do, you may see a big black mysterious error messages like this:

    Fatal error: Call to undefined function utw_showrelatedpostsforcurrentpost() in /home/…/upgradeTest/wp-content/themes/ygo-assorted/Post.php on line 38

    These blog killing errors are nearly always due to missing special purpose “template tags” a plugin developer wrote. When the plugin associated with any ’special’ template tag is active, the special template tag calls a different block only available in only when the plugin is activated. Otherwise, you get the skanky error.

    To avoid this problem, wrap all special template tags- like ‘utw_showrelatedpostsforcurrentpost();’ in “if/else” structures similar to this:

    if(function_exists(’utw_showrelatedpostsforcurrentpost’)){
    utw_showrelatedpostsforcurrentpost();}
    else{echo(’activate plugin ‘); }

  4. Anticipate difficulties and delays with major upgrades.
    If you use very vew plugins, your upgrade will probably be a snap. Many bloggers just click the “one click update” and they are done.

    However, if you use loads of plugins, you could have difficulties. For example, one blog visitor tells me “adSense Deluxe” doesn’t work in WP 2.3. Also, some of the various “tag” plugins with WP 2.2.X, you may need to run a script to restore functionality. So budget some time.

    Because I’m in the process of upgrading plugins, I am also aware that quite a few “hooks” available prior to WP 2.3 have simply vanished; (one of my favorites is gone!) “Hooks” are used to pull in plugin functionality at a certain point in WP; when the hook is vanishes, a plugin that uses that hook doesn’t work at all. So, in this case, you fiddling with your theme won’t help.

  5. Let the plugin developer know if a plugin breaks.
    If a plugin breaks, let the developer know. If you can’t find an email address, post about the problem at your blog and leave a trackback to the blog post where you can get the plugin.

    The big advantage to informing the plugin developer is they may be able to save you time by either confirming that a) It’s not you, it’s the plugin, b) they may point you toward the fix or c) they may schedule some time to fix the issue.

    In anycase, even though the developer may be busy and unable to look or fix the issue quickly, they will want you to let them know. They are the best person to help you!

Meanwhile: Good luck with your upgrade. Mine will be slower than most because I’m updating my plugins in parallel. I think I have “HideSponsoredCategories” finished, and “KonteraControl” is next. I’m on schedule to finish my upgrade in.. how many weeks was that? Well, soon.

With luck, and effort, a new version of Kontera Control will be available next week.