Ill be adding this to my magic forum, as it will be ideal on helping magicians who need answers to an effect, or move

Uninstalling is leaving things behind that when you try to re-install spits out SQL errors because it never properly uninstalled. This is on a stock VB 2.4. Errors which have been posted previously in the past few or so pages. Is there an SQL command that can help rid the sql database of content left behind by this plug-in?

There is an issue with permissions. When set for guests to be able to ask questions, however moderate them, it post questions without moderation queue. Please resolve.

Also, would be great to have a widget for cms with latest questions.

Awesome mod though.

Ditto. It leaves behind the discuss_categories, discuss_questions, discuss_replies, and discuss_watch tables. If you don't, you will get database errors if you try to re-install, plus it isn't good to leave these tables anyway.

You'll need open your SQL manager and drop each of them.

BACKUP first!

It does not leaves back anything. A simple look in product-discuss.xml can prove it:
Just now I tried once more to install and uninstall it, checking the database with phpMyAdmin. Tables created correctly and removed after uninstallation.
Please look somewhere else to find the reason that the tables didn't removed.

Chris

Posting xml coding doesn't prove that its uninstalling anything. Especially on newer software.

Yes the software uninstalls from the forum. BUT when the software is re-installed, the sql errors are spit out because of the sql tables being left behind. It's not mine or VBulletins fault. I simply just do the uninstall from VBulletin. So who else could we talk to?

So even though mine was done on a stock version of the VBulletin 4.2 software, and obviously VB won't support this, then who else does since it's obvious you feel hassled to.

What version of VBulletin did you test this on? Is this 100% confirmed to be 4.2 compliant? For future reference.

Your post almost seems to blame us. What's funny is you are saying this is supported above, yet tell us to go somewhere else to get support. Amusing.

When mine was done on STOCK (no other mods or template edits at the time and using the stock skin) VBulletin 4.2 software I uninstalled it because the navbar link was not showing up so I figured if I uninstall and re-install it maybe it would be fixed. When I went to re-install it is when the sql errors occured. And that is when I found out from coming back here and searching in this thread that another user or 2 posted with the same problem, and I saw for myself, was the sql code was left behind.

Also, its leaving a 'discuss' in the usergroups that that SQL coding is obviously also not removing. Because if you remove those by themselves....the 'discuss' entry is still left in the Usergroups. When you delete it it stays gone. That is until you try re-adding this plug-in. Once you try re-adding this plug-in it automatically re-adds those sql.

Keep in mind this is the ONLY plug-in I have had this issue with.

Posting the xml code (and of course checking that really this code exists in your file, proves that there is no coding error.

Even a simple server down at the time of uninstallation can be the reason that uninstallation fails.

You post at 03:41am my time (hope that you're permitting me to sleep at nights), and I replied at 08:12am, which means 13 minutes after the time that I came online. So I'm supporting you.

If you give a minute to read the details, you'll find out that says: "vB Version: 4.1.11". Not even 4.1.12. So don't asking if its confirmed for 4.2 compliant.

My second reply to your questions shows that I'm supporting it. But for issues that are coming from wrong code etc. Not for issues that you maybe have in your server, or in your vb installation, or (most probably this is the issue) from the vb version that you're using.

All mods here which are using tabs and menus are having incompatibilities with 4.2 as vb is using a totally different way for navbar in this version. I'm working on this, just keep in mind that I've more than 10 mods to fix.

If the uninstallation failed, then ALL the database changes left behind. For your refference (but only if you're familiar with phpMyAdmin), there are 4 tables and 3 fields to remove:

1.- Tables

discuss_categories
discuss_questions
discuss_replies
discuss_watch

2.- Fields

a] Discuss in table usergroups
b] discuss_questions in table user
c] discuss_replies in table user

Chris

Which would be great but the server has never been down and has never experienced problems with SQL. EVER. While it's not impossible, it's pretty unlikely.
But telling us to go somewhere else for the answer is NOT supporting us after telling us it uninstalled and re-installed fine for you. Anyone can give a vague or simple answer. Especially to just go elsewhere for help.

Actually helping figure out why its only your plug-in that I have used that is experiencing this issue would be support. While 4.2 may be the issue...there are other 'not quite yet updated' plug-ins that have installed and uninstalled just fine on 4.2 for me and not experienced the same problem with them.

And I was clear in my first post that I was using 4.2 stock at the time. When you responded you never stated what version of VB you used to do your test on. And you never stated 4.2 was the likely problem. But to just go somewhere else for support.

While my issue was with 4.2....I can't vouch the others with the same issue what VB version they were using, but they at a minimum experienced the same things left on the server after uninstall. But I was not the only one.

Fair enough.

Thank you. I had already deleted the Tables...just gotta dig up the Fields but those will have to wait until tomorrow as it's too late tonight for me to get rid of them.

I don't know about all of that. I installed as instructed & then uninstalled. I then re-installed, and started getting database errors that tables already existed. I found that the uninstaller had left all 4-tables behind. Believe me or not, it's a fresh 4.2 test environment.

Please don't try it in vB4.2. I haven't checked it there. The max checked and compatible version is 4.1.12

Chris