Rss Bloggers: Anyone ever see this database error using AutoBloggerPro?

[Nismo]

I just installed ABP on some blogs that were dead and when I went to the Feeds tab in ABP, I see this error, and obviously ABP doesnt work now.

WordPress database error: [Unknown column 'link_activehidden' in 'where clause']
SELECT * FROM wp_links WHERE link_visible = 'Y' AND link_activehidden = 'n' AND is_RSS = 'Y'

[uno]

I haven't seen that one, but did you submit a support ticket?

Also, did you reinstall the program to update the database?

[Nismo]

Yes, I submitted a ticket and talked with someone from ABP. They didn't seem to care much to help me since Im using the older version of ABP.

And no, I didn't re-install anything. It was a fresh install.

[Nismo]

bump for help.

[edgeprod]

Looks like the WordPress update changes the way tables are handled.

I don't see a ticket in there right now, but thanks for the "they didn't seem to care much to help me" comment.

[edgeprod]

I haven't seen that one, but did you submit a support ticket?

Also, did you reinstall the program to update the database?

You probably didn't try to update WordPress independently of Autoblogger Pro. I wouldn't recommend doing that in any event, because A) Autoblogger Pro is NOT designed to be updated without an official release, B) The latest STABLE version WordPress is the version that the old Autoblogger ships with. We don't sell it any longer, and it can only be downloaded by users who own the old Autoblogger.

Hope this helps you to not run into DB issues.

[Nismo]

Looks like the WordPress update changes the way tables are handled.

I don't see a ticket in there right now, but thanks for the "they didn't seem to care much to help me" comment.

YOU were helpful (actually very helpful), however, i haven't seen you on IRC in weeks

I sent a ticket a couple of weeks ago and wasn't offered much help since im not using the new stand alone version.

[OzMan]

...thanks for the "they didn't seem to care much to help me" comment.

That really makes you want to go the extra mile to help him doesn't it.

[Nismo]

Looks like the WordPress update changes the way tables are handled.

Is there any thing I can do to correct this or am I SOL?

[Nismo]

You probably didn't try to update WordPress independently of Autoblogger Pro. I wouldn't recommend doing that in any event, because A) Autoblogger Pro is NOT designed to be updated without an official release, B) The latest STABLE version WordPress is the version that the old Autoblogger ships with. We don't sell it any longer, and it can only be downloaded by users who own the old Autoblogger.

Hope this helps you to not run into DB issues.

I had to update WordPress in order to login. That's where things get fuzzy and the issue started.

[edgeprod]

That really makes you want to go the extra mile to help him doesn't it.

If you saw HALF the abuse I take from people who have broken their own installation, posted on GFY instead of making a ticket, contacted my personal ICQ (or called) to demand that their ticket is answered within 2 minutes of submitting it, etc ... you'd fall over.

I just had a guy -- literally -- pick up his database, move it to another server, and forget to update his paths, etc. He yelled at me in a ticket, said the software was shit, etc, etc .. then, when I noticed it was user error in migrating it to a new server/directory without updating it .. he just went AWAY and never responded.

So, believe me when I say I've got a thick skin, and will help Nismo with his problem, no matter what -- our customers are VERY important to us, and we'll be abused a bit from time to time to make sure everyone is happy.

[edgeprod]

Is there any thing I can do to correct this or am I SOL?

The old Autoblogger Pro *cannot* be used with the new WordPress. What version did you upgrade to, and what method did you use? We *might* be able to reverse it. If not, we can perhaps re-install ABP, not run any upgrades, and migrate the post database to "salvage" it.

Alternatively, I can pull your feed with my new version of ABP, and re-post it to your blog (the new one posts OUT, not pulls IN).

[mattz]

whenever i get errors i just reinstall

if its wordpress your talking about just deleate all wordpress file except wp-config.php and reupload all the files and everything will be back to normal

just dont overwrite the wp-config.php file

[Nismo]

I apologize if I came off as an asshole, but im just frustrated as you can imagine. I've been working on this issue for about 2-3 weeks now to no avail.

I've worked customer service before and I know, firsthand, it sucks. HEH

[edgeprod]

YOU were helpful (actually very helpful), however, i haven't seen you on IRC in weeks

Well, thanks, I try.

I don't know if you saw Chio's thread, but I had a complete PC failure. I am using a "backup" PC until my main one is salvaged or replaced. My backup PC didn't even have an IRC client until yesterday, so ... you are unlikely to see me there much. I withdrew our SlashNET application in the meantime, as well.

[Nismo]

The old Autoblogger Pro *cannot* be used with the new WordPress. What version did you upgrade to, and what method did you use? We *might* be able to reverse it. If not, we can perhaps re-install ABP, not run any upgrades, and migrate the post database to "salvage" it.

Alternatively, I can pull your feed with my new version of ABP, and re-post it to your blog (the new one posts OUT, not pulls IN).

Can I just hit you up on ICQ?

[edgeprod]

I apologize if I came off as an asshole

You didn't, but you have to understand: when someone sees a thread like this (instead of someone ICQ'ing me or Chio to get it straightened out), it looks like shit for us. We bend of backwards for our users, and there have been multiple threads applauding our service -- I think it's some of the best in the industry for a small company, personally, since I spend HOURS on even user-created problems, which is MUCH more than most companies would feel $299 entitles you to. Heck, we still support the OLD Autoblogger, even though the technology has moved WELL beyond it.

, but im just frustrated as you can imagine. I've been working on this issue for about 2-3 weeks now to no avail.

I've worked customer service before and I know, firsthand, it sucks. HEH

We'll get it solved one way or another, then. WP asks you to upgrade, but it's not usually a good idea with the old Autoblogger. Because ABPSA (the new one) is unattached from WP, it would fine with the new one.

The guy who developed the old one is no longer with the company, and it puts a dampner on future development in that line of the product.

[edgeprod]

Can I just hit you up on ICQ?

Of course. Most people end up using my personal ICQ as a support interface anyway ...

But I'm here, feel free.

[Young]

rss blogger = oxy moron

[edgeprod]

rss blogger = oxy moron

And yet ..

traffic++;

So, as usual: *yawn*

[Cory W]

Edgepro is one of the most helpful people in the business.

[edgeprod]

Edgepro is one of the most helpful people in the business.

Between him and his brother Edgeprod, they rock!

Haha, thanks Cory.

[More Booze]

No, but I have another problem with ABP. I got 3 blogs on the same server as ABP. ABP can post to one of them. But it says "Connect error: No route to host (113)" for the other two.

Anyone know what to do?

[tenderobject]

If you saw HALF the abuse I take from people who have broken their own installation, posted on GFY instead of making a ticket, contacted my personal ICQ (or called) to demand that their ticket is answered within 2 minutes of submitting it, etc ... you'd fall over.

I just had a guy -- literally -- pick up his database, move it to another server, and forget to update his paths, etc. He yelled at me in a ticket, said the software was shit, etc, etc .. then, when I noticed it was user error in migrating it to a new server/directory without updating it .. he just went AWAY and never responded.

So, believe me when I say I've got a thick skin, and will help Nismo with his problem, no matter what -- our customers are VERY important to us, and we'll be abused a bit from time to time to make sure everyone is happy.

lol that guy is harsh he can throw me his copy of your script man.. when will you have a promo for ABP stand alone?

[Mike Semen]

If you saw HALF the abuse I take from people who have broken their own installation, posted on GFY instead of making a ticket, contacted my personal ICQ (or called) to demand that their ticket is answered within 2 minutes of submitting it, etc ... you'd fall over.


So, believe me when I say I've got a thick skin, and will help Nismo with his problem, no matter what -- our customers are VERY important to us, and we'll be abused a bit from time to time to make sure everyone is happy.

That's pretty much the nature of software support right there bro.

[edgeprod]

No, but I have another problem with ABP. I got 3 blogs on the same server as ABP. ABP can post to one of them. But it says "Connect error: No route to host (113)" for the other two.

Anyone know what to do?

That sounds very odd, like a network routing problem. Autoblogger *itself* has no such error, so I'm guessing network connectivity, or the configuration of the network itself. Who's the host? What's the environment like, generally?

Where does it SPECIFICALLY give you the error? During step 3 (posting)? Can you submit a ticket with a screenshot? It'd be interesting to take a peek.

Also, we should try posting to those blogs from *my* copy of ABPSA, so that we know Autoblogger works fine, and we can narrow it down to a problem with one of the blogs (this is usually the case).

You should *never* get a bad route to the *same* box, but I'm sure you know that.

lol that guy is harsh he can throw me his copy of your script man.. when will you have a promo for ABP stand alone?

Yeah, well. To each his own. ABPSA is $249 right now for the holidays.

That's pretty much the nature of software support right there bro.

Agreed, but I want our users to be taken care of, so I'm willing to be a punching bag from time to time. We give a LOT of support for a $299 purchase, which usually extends to helping people fix server misconfiguration by their hosts. You'd be amazed how many "problems" go away when a server is set up correctly .. or maybe you wouldn't be.

[edgeprod]

Also, as a follow-up, do you get *any* error message for the blog is has no problems with? And they're all WordPress, same version, right?

[More Booze]

Also, as a follow-up, do you get *any* error message for the blog is has no problems with? And they're all WordPress, same version, right?

Hi, I just did open a support ticket. You'll find screenshots from "Step 3" and login-info to one of the blogs so you can try to post to it.

They're all Wordpress Blogs. One of the blogs did still run WP 2.0.4. I did upgrade to 2.0.5 but I still get the same error.

[Nismo]

Edge, are you going to be on ICQ today?

[edgeprod]

Hi, I just did open a support ticket. You'll find screenshots from "Step 3" and login-info to one of the blogs so you can try to post to it.

They're all Wordpress Blogs. One of the blogs did still run WP 2.0.4. I did upgrade to 2.0.5 but I still get the same error.

Ok, thanks. I'll take a look at the screenshot, then we'll try posting from my ABP. If that fails, "Houston, we have a problem," and we'll smack your host around to find out what's wrong with the networking.

Edge, are you going to be on ICQ today?

Yep. I just woke up (got up in the middle of the night to answer tickets, though, then went back to sleep). I'm going to pop on ICQ to check for "emergencies," go take a shower, then I'll be back. Feel free.

[edgeprod]

Hi, I just did open a support ticket. You'll find screenshots from "Step 3" and login-info to one of the blogs so you can try to post to it.

Ok, I posted 20 posts successfully.

It would seem to me, then, to be a routing problem with the host. I can't imagine what specific type of misconfiguration would cause you not to be able to reach an IP on the same machine, but stranger things have happened. Because we can reach it fine from the "outside world," it would seem the host isn't doing something odd like blocking XML-RPC (because my posts went through).

It seems to be a networking problem unrelated to Autoblogger Pro, but that doesn't mean we won't continue to help you, of course. If the host fails to solve the problem in the long run, please bump the ticket or give them my contact information. Barring that, I can suggest a number of hosts that have been verified to A) know what they're doing, B) have good support, and C) have experience with Autoblogger Pro.

[chronosafe]

Edge & Co. rock. There product is solid and support is outstanding.

Now all they need is to be able to post to Joomla as well as Wordpress and they'd be godlike.

[edgeprod]

Edge & Co. rock. There product is solid and support is outstanding.

Now all they need is to be able to post to Joomla as well as Wordpress and they'd be godlike.

Haha, thanks. What's the Joomla API like?