Jamie Kite's dashboard

A comment on the problem "Claim Blog error - code not found" in IZEA:

Hi Mark Anthony, This is a similar issue as N. Khan above, which was introduced with the new blogger signup process. We're working on fixing it for everyone else but it should be fixed for you as well. I am going to check in on both of your blogs during the next couple of days to make sure that it doesn't reset back to "uninstalled" again. Sorry for the inconvenience and thank you for reporting this! – Jamie Kite, on February 07, 2010 20:04

A comment on the problem "Claim Blog error - code not found" in IZEA:

This is caused by a known bug in SocialSpark, which we are actively working to fix. I have reset your blogs' ITK installed statuses and synced them with IZEARanks, which should fix the problem for you. If you continue to experience this issue please respond to this topic. – Jamie Kite, on February 07, 2010 19:57

Jamie Kite started following the idea "accessibility for the blind" in IZEA.

Jamie Kite replied on February 05, 2010 12:51 to the problem "Claim Blog error - code not found" in IZEA:

Your main site was forwarding to "/wordpress" so where our script was looking for the code on http://www.blogsense.ws it was getting a redirect response instead. I updated your blog URL and the claim went through fine. It is now in the reviewer queue.

Jamie Kite replied on February 05, 2010 12:42 to the idea "How do I make a post/thread "sticky" in Get Satisfaction?" in Get Satisfaction:

Just got a similar request from one of our users.

http://getsatisfaction.com/izea/topic...

Jamie Kite set one of Jamie Kite's replies as an official response to "Blog Statistics are all set to zero!" in IZEA

Jamie Kite replied on February 04, 2010 15:12 to the question "Blog Statistics are all set to zero!" in IZEA:

The ITK code you have installed on your blog is deprecated. This script will no longer correctly report your traffic to us:

<script src='http://tinyurl.com/2b5ojn' type='text/javascript'></script>
You must go to your My Blogs page and click the "Install ITK" link to get the correct ITK code for your blog:





When you're done with that, click Verify ITK and SocialSpark will tell you whether your ITK code has been properly installed.

Jamie Kite set one of Jamie Kite's replies as an official response to "Claim Blog error - code not found" in IZEA

Jamie Kite replied on February 04, 2010 12:50 to the problem "Claim Blog error - code not found" in IZEA:

Okay, it looks like there was a problem with your blog on IZEARanks, but I've rearranged a few things in the database so you should be able to claim now. You'll need to replace this code (click to enlarge):



With this one provided in your SocialSpark account:



Just a reminder, you can get that code by clicking on the "Install ITK" link next to your blog on the My Blogs page. Once you've installed the correct code, click the big "Claim Blog" button at the bottom of the screen.

Jamie Kite replied on February 04, 2010 12:39 to the question "Blog Statistics are all set to zero!" in IZEA:

Hi Mark Anthony, It would really help us if we had some way to find your account or your blog to see if we can determine what's causing your problem. As soon as you provide us with your username or blog URL we'll be happy to help!

Jamie Kite replied on February 03, 2010 12:40 to the problem "Claim Blog error - code not found" in IZEA:

Hi N. Khan! It would really help us if we had some way to find your account or your blog to see if we can determine what's causing your problem. As soon as you provide us with your username or blog URL we'll be happy to help!

Jamie Kite replied on January 28, 2010 19:28 to the question "Not able to take opportunities I qualify for!" in IZEA:

Hi Bellesouth, can you give an example or two of a specific Opp you feel you should be qualified but are not? That would really help nail down what the problem is.

Thanks!

Jamie Kite
Product Owner, SocialSpark

Jamie Kite replied on January 27, 2010 19:08 to the problem "URL doesn't match...?" in IZEA:

Hi Amy,

Sorry about that! You weren't doing anything wrong; there was just a glitch in the system. We went ahead and submitted your post for you, so as long as all of the requirements are met you should be good to go!

Thanks for your patience!

Jamie Kite
Product Owner, SocialSpark.com

Jamie Kite replied on January 27, 2010 12:48 to the problem "Money Due Not depositing" in IZEA:

Hi Keith, which site are you waiting for payments from? PayPerPost? InPostLinks? SocialSpark? SponsoredTweets? That information will help us help you!

Jamie Kite replied on January 25, 2010 12:51 to the question "Trouble Adding Claim Code to Blogger/Blogspot template" in IZEA:

Hi christinanpr,

It looks like you had some trouble pasting your claim code into your blog. I tested claiming a Blogspot blog once more this morning without a problem. Are you sure you copied the entire code? The code for your blog is this:

<script name="60c7b8a6-078b-11df-a780-123139069a14" src="http://izearanks.com/itk/show/runningfoodie-blogspot-com" type="text/javascript"></script>

You'll also need to make sure that you are not pasting the code into a post but into the blog template. In Blogger, this is typically done by clicking the "Layout" tab and "Add a Gadet" at the bottom of the preview page.







Make sure you've grabbed the whole code, from the opening <script> tag to the closing </script> tag.

I hope that helps you get your blog claimed! By the way, the photos on your blog are beautiful!

Jamie Kite replied on January 22, 2010 14:41 to the problem "IZEARanks not showing my blog traffic accurately." in IZEA:

Whatever the problem was it seemed to have resolved itself or you fixed it.

Jamie Kite set one of Jamie Kite's replies as an official response to "Post getting auto-rejected for "Blast Off!" Opp" in IZEA

Jamie Kite replied on January 21, 2010 14:18 to the problem "Post getting auto-rejected for "Blast Off!" Opp" in IZEA:

Dani and kissmykitty,

We just deployed this fix to production and both of your posts passed AutoReject. Thanks for your patience and sorry for the inconvenience!

Jamie Kite replied on January 21, 2010 12:51 to the problem "Post getting auto-rejected for "Blast Off!" Opp" in IZEA:

Hi kissmykitty,

It looks like the advertiser put straight double-quotes in their disclosure message, which Wordpress turned into HTML entities for curly quotes when you posted. We've remedied a similar issue before, but it looks like we missed the numbered HTML character entity for a double-quote. We're going to get this fixed this morning (since you absolutely won't be the only one experiencing this). Until then, you can try to get Wordpress to stop converting your quotes:

• Use WP-No-Format plugin in combination with special comment tags to disable the Wordpress texturize filter for certain parts of a post, OR


• Disable Wordpress's "smart quotes" feature site-wide using the technique described in here: Wordpress, Stop Changing My Quotes!

If you're not 100% comfortable installing a plugin or editing your template's PHP, you should wait for our fix to go out. I just see your frustration and want to empower you to have a way to prevent it in the future!

Thanks for your patience.

Jamie Kite
Product Owner, SocialSpark.com

Jamie Kite reported a problem in IZEA on January 21, 2010 12:51:

Post getting auto-rejected for "Blast Off!" Opp

Dear SocialSpark: the post DOES contain the damn disclosure sentence. Let's not start this auto-reject bullshit again...