TOPIC: How to Remove Ccomment from the Database?

I'm doing perhaps the most tedious migration I've ever done. It was easier to go from Joomla 1.5 to 1.7 than it is to go from Joomla 2.5 to 3.1. Because traditional migration wasn't working (it only part way installed J3) I decided to try a untraditional method. I extracted the data from my backup, applied the content to a J 2.5, upgraded it to J 3.1. Once I did this to the rest of my data I created a fresh J 3.1 site (to prevent upgraded 2.5 files from being an issue) and inserted it. This is the short and sweet version of the story, but I almost completely pulled it off cleanly.

The bad news is that near the end I some how ended up with a duplicate copy of Ccomment. I turned on complete uninstall which removed the initial Ccomment but am left with a glitchy looking one. I know perfectly well how to remove the tables, but I assume there is more to it to remove. What DB tables should I look into to completely remove Ccomment?

Once I have it completely uninstalled I plan on re-installing Ccomment. The reason I want to remove this broken copy is to prevent future problems. And no worries, I have very few actual comments on my site considering that it is still a work in progress (I hope to have it finally stable some time this Fall).

Here's a screen shot of what it looks like in the backend:



For some reason it won't let me attach it in this forum.

all tables with #__comment

and then go to #__extensions and look for com_comment
and also in #__menu

That should be all.

Regards,
Daniel

Thanks for the reply. I admit I know how to work with importing and exporting tables but don't actually know SQL. So when you say #_ is that actually part of what I'm searching for? I did a search for "#__comment" and came back with zero results.

Fortunately I went ahead and searched "com_comment" in all tables and had 7 results in the menu table. I inspected them which sure enough they are the names that were familiar. After purging them Ccomment was completely removed. I re-installed it which it is now looking perfectly clean. (same for the front-end)

Hey Josh,
My bad - #__ is not a SQL thing, it is a joomla thing.

#__ gets replaced by joomla with your table prefix. So in the above example it should be read:

#__comment = yourTablePrefix_comment

Cheers,
Daniel

P.S. Glad you've sorted everything out!