Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

All other Modules /

Discuss all other Modules here.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

remove module 3-0-2

Go to End

4 Posts   1795 Views


Community Member, 10 Posts

15 November 2012 at 3:08pm

Edited: 15/11/2012 3:15pm

What is the correct way to remove a module?

For example, if i have the module folder in the root, delete this folder, and run dev/build, the module will be removed, also the database fields?

Or there is a specific folder where the modules are installed ? What i want is a full cleanup of a specific module.


Community Member, 187 Posts

15 November 2012 at 10:08pm

The module should be in the root folder, simply delete the folder and do a dev/build, possibly a ?flush=1 if you get any template errors.

I'm not sure if the database tables are actually removed, I would guess that SilverStripe keeps them and renames them to _obsolete_<tablename> or something, the same way it does with page types. Leaving the 'obsolete' database fields there won't cause any problems, unless they contain really sensitive information and you want to remove them.

Matty Balaam

Community Member, 74 Posts

15 November 2012 at 11:20pm

Database fields will hang around unless you remove them manually.


Community Member, 10 Posts

16 November 2012 at 2:36am

Edited: 16/11/2012 2:38am

My question is related with this situation:

I report as a bug, but i am not sure what is really happening.

I also tried remove the old tables created by the model (querying the information_schema and date of creation), but the situation still happen.

Any idea?

Ps: I think there is no obsolete name in the tables of the module that is deleted.