Zikula Community

• mesteele101
  
  

  • Rank: Helper
  • Registered: Sep 19, 2003
  • Last visit: May 25, 2010
  • Posts: 611

  Posted: Jul 20, 2008 - 08:10 PM

  I have a module that refuses to delete the tables from the databas and becuse of that it refuses to remove itself from the modules applet in Zikula.
  
  How do you manually do the process of removing a module in the event that a module deactivates, but wont delete itself???
  
  The module is PNphpBB2, if it make a differance. This is a quirk in PNphpBB2 running on Zikula and a new install of Zikula and PNphpBB2 has the same effect.
  
  TIA...

  • 
  •  
• AmmoDump
  
  

  • Rank: Team Member
  • Registered: Dec 07, 2003
  • Last visit: May 09, 2010
  • Posts: 2703

  Posted: Jul 20, 2008 - 08:24 PM

  While it is deactivated:
  
  Remove the module files.
  Remove the the tables from the DB (they should be prefixed, and easy to find)
  
  This should be done after Backing Up DB and Files systems.
  
  --
  David Pahl
  Zikula Support Team

  • 
  •  
• Guite
  
  

  • Rank: Team Member
  • Registered: Jan 19, 2003
  • Last visit: Apr 06, 2010
  • Posts: 442

  Posted: Jul 20, 2008 - 09:55 PM

  If it really should be clean, you might also remove the module variables in the prefix_module_vars table.
  
  --
  Guite | ModuleStudio

  • 
  •  
• mesteele101
  
  

  • Rank: Helper
  • Registered: Sep 19, 2003
  • Last visit: May 25, 2010
  • Posts: 611

  Posted: Jul 21, 2008 - 01:42 AM

  So, doing a removal of a non-core module is as simple as:
  
  1) removing all the relaited database tables
  2) Remove any files and folders that were originally installed
  3) remove the variables in the prefix_module_vars table
  
  Should the module be deactivaed first?
  
  By removing the variables in the prefix_module_vars table, does this remove the listing in the modules app?

  • 
  •  
• AmmoDump
  
  

  • Rank: Team Member
  • Registered: Dec 07, 2003
  • Last visit: May 09, 2010
  • Posts: 2703

  Posted: Jul 21, 2008 - 01:51 AM

  the active/nonactive/not-initialized state should be stored in the module variables tables. So deleting that line should eliminate it.
  
  Personally, I would remove it as far as possible in the admin, before proceeding. And having a full backup ready should give you full confidence to proceed
  
  --
  David Pahl
  Zikula Support Team

  • 
  •  
• mesteele101
  
  

  • Rank: Helper
  • Registered: Sep 19, 2003
  • Last visit: May 25, 2010
  • Posts: 611

  Posted: Jul 21, 2008 - 01:57 AM

  With all that said, I'm reverting to a backup PRE 1.0.1 and see if 1.0.1 was the culpret. I read some old postnuke posts about core modules could cause this to happen?
  
  Thanks...

  • 
  •  
• mesteele101
  
  

  • Rank: Helper
  • Registered: Sep 19, 2003
  • Last visit: May 25, 2010
  • Posts: 611

  Posted: Jul 24, 2008 - 12:14 PM

  Ok, the problem relaited to REMOVING PNphpBB2 once after its installed persisted after a clean install.
  
  I removed the module:
  
  1) From the modules I deactivated PNphpBB2
  
  Note: You can try to trash the PNphpBB2 folder at that point but all it would do for me was loop.
  
  2) Delete all the tables related to PNphpBB2 in the database
  
  3) Go back into the modules and trash the PNphpBB2 module.
  
  That did it for me.
  
  --
  Kindest regards,
  Michael...
  
  WINSNORT.com Management Team Member
  --
  Pick up your FREE Windows Snort installation guides
  mailto:support@winsnort.com
  Website: http://www.winsnort.com
  Snort: Open Source Network IDS - http://www.snort.org

  • 
  •  
•  
•  

Users on-line

• 0 users

This list is based on users active over the last 60 minutes.