I've tried to submit my site to the marketplace but it keeps getting an error saying "Please enter a valid Purchase URL". I've no idea what's wrong.

Would you mind helping me to check on this?

Purchase URL: http://www.imkevintan.com/wp-content/plugins/oiopub-direct/purchase.php

Thank you.

Hi Simon,

Thanks for your respond. Yeah I don't have Bad Behavior plug-in installed.

Is there an alternative way to submit to the marketplace?

I don't wanna waste time figuring out which plug-in blocks the process.

Thanks Simon! Your respond above made my day!

When you say doesn't work - do you mean OIO stops functioning correctly when wp-minify is used, or that OIO scripts don't get minified?

I found out why the purchase page wasn't validating - you've got a "BOM" issue. Essentially it's when a file is encoded using UTF-8 (eg. when saving it in notepad), but also includes 3 extra hex characters at the beginning of a page. More info about it and Wordpress here.

It won't show up in browsers like FireFox, but the extra characters can cause problems trying to read data from a web page. I'm not sure what would be causing it - it could be a theme file or possibly a plugin (since it's happening when loading an OIO page too).

I've added some code on the OIO side to remove these hex characters when making the validation, so you should be able to submit your site now.

-----------

I've also checked out wp-minify, using the default Wordpress theme and OIO. It all seemed to work ok, so I don't think there's much I can do about it. Combining css / javascript files like that always has the potential to stop them functioning correctly.

You could try excluding the OIO css file in the wp-minify config page, if it's the combining causing the problem.

All recommendations welcome. ;)

Unfortunately I've no idea what's causing the BOM issue, as the characters are "invisible" (you won't see it if you open any of the blog's files in a text editor). It only exists because of the way a file has been saved.

For example, if I created a plugin called "wp-helpful.php" and saved the file incorrectly in my text editor, then you activated it on your blog, it may cause the same problem. But there's no way to tell unless you can find the file(s) causing it.

I wouldn't worry too much about it though, as it only becomes an issue in very rare circumstances (like this one).

-----

If you did want to have a go at finding it, you could try eliminating your plugins first (seems like the most likely cause to me). If you de-activate them all, then run your home page through this scanner (it looks for BOM characters), you'll be able to see whether the BOM characters still exist:

>> http://people.w3.org/rishida/utils/bomtester/

If it says no BOM found, then you'll know one of the plugins was causing it and you can go from there.

It'll be the same cause as before, I'm afraid. The BOM characters will cause the validation to fail.

For the moment I'd say don't worry about the API key - OIO's functionality won't be compromised if you don't enter it. I'll look into compensating on my end at some point, but it's a bit more complicated that the submission process (potential knock on effects etc).