10446 Posts in 2223 Topics by 1719 members
|
Page:
1
|
Go to End | |
| Author | Topic: | 268 Views |
-
remove module 3-0-2
15 November 2012 at 3:08pm Last edited: 15 November 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.
-
Re: remove module 3-0-2
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.
-
Re: remove module 3-0-2
15 November 2012 at 11:20pm
Database fields will hang around unless you remove them manually.
-
Re: remove module 3-0-2
16 November 2012 at 2:36am Last edited: 16 November 2012 2:38am
My question is related with this situation:
https://github.com/silverstripe/silverstripe-userforms/issues/71
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.
| 268 Views | ||
|
Page:
1
|
Go to Top |
