CMS Made Simple Forums

Hi,

I'm pretty new to CMSMS. I've been checking out CMSMS for about a month and I really like how easily it makes it to customize.

The thing is that I didn't know that the FeedbackForm module is not compatable with version 1.0.6 and it never said anything about that in the ModuleManager when I was installing it. Now that I've installed it, it is now telling that I should use FormBuilder instead and doesn't give any means to uninstall it.

Cna anyone tell me how to uninstall this FeedbackForm module?


Thanks in advance,

Winchester

Go to "Extensions -> Modules", there you can select "uninstall" behind eery module listed. Afterwards you can also select "remove", that removes the files in the folder, the first one only deletes it inside the DB.

Ronny

Thanks for such a quick reply.

The problem is that that "Unistall" link is not there.  All that is there is the name of the module, FeebackForm. Followed by a message that says, "Maximum CMSMS Version Supported: 1.0.5" and then only the "Help" and the "About" comes at the end of that line. No link - like the other modules listed - for "Unistall".

I've read in the German board earlier a statement on where to change it...

http://forum.cmsmadesimple.org/index.ph ... l#msg59936

Ronny

I think that topic is talking about preventing it, but nothing there to help remove the FeedbackForm module.

I think I'm just going to reinstall CMSMS.

Thanks for you help.

What I did was to right click one of the "Uninstall" links for one of the other modules, copy it, paste it in the address bar, but replace that module name with FeedbackForm, or whatever it was called.

Alternatively, right click the name of the module, copy the link, paste it into the address bar and replace "showmodulehelp" with "uninstall" (without the quotes.)

I hope this isn't too late!

Lo ppl,

Got the same problem here. Unfortunately the solution PrezPenguin suggested didn't work for me.

Will search for a solution and let you people know if I found any.

Gr.

EDIT:

The problem with the suggestion of PrezPenguin is that the module isn't installed :p

SOLUTION:
-open the file FeedbackForm.module.php (located in modules/FeedbackForm/) in your favorite editor
-goto line 122 and change this:

function MaximumCMSVersion()
{
  return '1.0.5';
}

into this:

function MaximumCMSVersion()
{
  return '1.1';
}

-now you can delete the module in your module manager

Hope this helps...

Another way may be to go to your site, FTP, and delete the folder for that module, no folder no module...

@Haller

Did you delete the folder before you tried to uninstall using the Module Manager?  That's what I initially tried, but the FeedbackForm entry remained in the manager window, therefore the FeedbackForm databases were still intact.  If you deleted the folder first, maybe the system couldn't access the uninstall script or whatever it uses?
I swear that my method worked flawlessly for me, but then again, I've only had to do this once.  Plus, that link to the uninstall script is what changing the maximum CMS version to gets you to eventually, right?

Which brings us to Mark's suggestion, which, as I said before, was my first attempt at dealing with this problem. The system still thinks it's installed, so it will stay in the Module Manager forever, adding to the clutter.  This probably isn't ideal if you want to maintain a working site with other active users, and you don't want to have them confuse FeedbackForm with FormBuilder.

@PrezPenguin
Nope, I did not delete the folder before uninstalling. The module never installed because of the version check :p

After changing the MaximumCMSVersion the links for deleting and installing the module came forward.

@mark

True


The "big problem" for me is that if I install a module via XML the owner of that directory will be the apache or www-data user and that makes it imposible to delete with the ftp user. So I first have to change the permissions/user/group with a superuser/root account and then I can modify MaximumCMSVersion or (as mark suggested) delete the directory. So in my case its an flaw in CMS MS and my hosting setup...