Support Forums - All Posts - XOOPS Web Application System

61

Changing module directory names ?

2004/3/1 8:58
amok200
Just popping in
Posts: 68
Since: 2004/2/23

Hi,

If I choose to change a standard core module directory name from say, news to latest or whatever (I guess I will have to re-install the module, which is OK since Im just starting out my site) will this be an issue when I want to upgrade to the next release of XOOPS ? Since I presume the upgrade script will look for certain directories for the core modules ...

Or will it be only a problem for non-core modules like xfsection etc ?

Thanks,

amok

62

Re: How do you uninstall a broken module ?

2004/2/26 23:17
amok200
Just popping in
Posts: 68
Since: 2004/2/23

Wowsers !

Thanks ! Everything looks clean now. I really appreciate your time and help - I really feel like I have learned a lot about XOOPS from all of this, and feel much better about using it.

I have two lessons I learned from this experience to pass onto the XOOPS new users like myself

1) Read all installation instructions carefully (twice) !
2) Don't be afraid to ask questions because you can find really helpful decent folks here !

Cheers again hsalazar,

Amok

63

Re: How do you uninstall a broken module ?

2004/2/26 18:40
amok200
Just popping in
Posts: 68
Since: 2004/2/23

Hi Horacio,

Im grateful for your response ! Actually I was thinking along the same lines .. I looked thru the table list with phpmyadmin and found xoops_modules which is where I figured the module admin got its list from. I removed the two blank entries, but then was stuck on how to 'clean up' the rest of the entries until I got your mail !

I still need some advice however on how to proceed.. I did as you suggested and got the following:

Quote:

Creating tables...
Table xoops_xfs_article created.
Table xoops_xfs_broken created.
Table xoops_xfs_category created.
Table xoops_xfs_config created.
Data inserted to table xoops_xfs_config.
Table xoops_xfs_files created.
Table xoops_xfs_votedata created.
Module data inserted successfully. Module ID: 30
Adding templates...
Template xfsection_article.html added to the database. (ID: 164)
Template xfsection_article.html compiled.
Template xfsection_topten.html added to the database. (ID: 165)
Template xfsection_topten.html compiled.
Template xfsection_htmlart.html added to the database. (ID: 166)
Template xfsection_htmlart.html compiled.
Adding blocks...
Block XF-Section Article Links added. Block ID: 80
Template xfs_block.artmenu.html added to the database. (ID: 167)
Template xfs_block.artmenu.html compiled.
Block XF-Section Menu added. Block ID: 81
Template xfs_block.menu.html added to the database. (ID: 168)
Template xfs_block.menu.html compiled.
Block XF-Section Topics added. Block ID: 82
Template xfs_block_topics.html added to the database. (ID: 169)
Template xfs_block_topics.html compiled.
Block XF-Section Big Article added. Block ID: 83
Template xfs_block_bigstory.html added to the database. (ID: 170)
Template xfs_block_bigstory.html compiled.
Block XF-Section Top added. Block ID: 84
Template xfs_block_top.html added to the database. (ID: 171)
Template xfs_block_top.html compiled.
Block XF-Section Recent added. Block ID: 85
Template xfs_block_new.html added to the database. (ID: 172)
Template xfs_block_new.html compiled.
Block XF-Section downloads added. Block ID: 86
Template xfs_block_newdown.html added to the database. (ID: 173)
Template xfs_block_newdown.html compiled.
Adding module config data...
Config com_rule added to the database.
Config option added. Name: _CM_COMNOCOM Value: 0
Config option added. Name: _CM_COMAPPROVEALL Value: 1
Config option added. Name: _CM_COMAPPROVEUSER Value: 2
Config option added. Name: _CM_COMAPPROVEADMIN Value: 3
Config com_anonpost added to the database.
Setting group rights...
Added admin access right for Group ID 1
Added user access right for Group ID: 1
Added block access right. Block ID: 84 Group ID: 1
Added block access right. Block ID: 86 Group ID: 1
Added block access right. Block ID: 85 Group ID: 1
Added block access right. Block ID: 83 Group ID: 1
Added block access right. Block ID: 82 Group ID: 1
Added block access right. Block ID: 81 Group ID: 1
Added block access right. Block ID: 80 Group ID: 1
Added user access right for Group ID: 2
Added block access right. Block ID: 84 Group ID: 2
Added block access right. Block ID: 86 Group ID: 2
Added block access right. Block ID: 85 Group ID: 2
Added block access right. Block ID: 83 Group ID: 2
Added block access right. Block ID: 82 Group ID: 2
Added block access right. Block ID: 81 Group ID: 2
Added block access right. Block ID: 80 Group ID: 2

Module XFsection installed successfully.

Which tables or directories do these entries all go into ? I'd like to clean up without reinstalling everything (have lots of things in XOOPS now) so that my installation is clean and secure.

Thanks !!

amok

64

Re: How do you uninstall a broken module ?

2004/2/26 15:15
amok200
Just popping in
Posts: 68
Since: 2004/2/23

Hi Richard,

Thanks for the reply. I've tried the above steps, unfortunately they did not work. I've discovered my error now.. I was supposed to rename the module folder from xfsection-104-2 to xfsection before uploading it, I suppose module installation doesnt like the dashes or numbers or something.

When I did the above, it installed fine, but now I still have 2 modules with 'blank' name that refuse to uninstall.

Do you know what the database tables and columns are where this data is held ? Perhaps I could remove them manually.

Thanks much,

Amok

65

How do you uninstall a broken module ?

2004/2/26 6:43
amok200
Just popping in
Posts: 68
Since: 2004/2/23

Hi,

I tried to install a module (xfsection 1.04) and it didnt install properly - I get "Module File for Not Found!" in the module list, and it's name is blank. Now, when I try to unistall it nothing happens. Actually since I tried to install it twice, I have two of these. Clicking uninstall gives:

http://mysite.com/modules/system/admin.php?fct=modulesadmin&op=uninstall&module=

As you can see the names is an empty string.

How can I remove these entries from the Modules Administration ?

Thanks !

Amok

66

Re: Help, cannot install any themes -> blank screen

2004/2/24 15:30
amok200
Just popping in
Posts: 68
Since: 2004/2/23

brash,

thanx for responding - the problem is solved ! I had extracted the folders incorrectly - silly me, so I had for example

themes/themename/themename

instead of

themes/themename

something to watch out for when ftping !

thankx again

67

Help, cannot install any themes -> blank screen

2004/2/24 4:26
amok200
Just popping in
Posts: 68
Since: 2004/2/23

hi,

anytime i've tried to use a downloaded theme I get a blank page when I hit 'home page'. the included themes all work fine. im using 2.0.6. ive tried uploading both as auto and ascii with no success.

please help !

thx

Stats
Goal:	$100.00
Due Date:	May 31
Gross Amount:	$0.00
Net Balance:	$0.00
Left to go:	$100.00

Forum Index

Changing module directory names ?

Re: How do you uninstall a broken module ?

Re: How do you uninstall a broken module ?

Re: How do you uninstall a broken module ?

How do you uninstall a broken module ?

Re: Help, cannot install any themes -> blank screen

Help, cannot install any themes -> blank screen

Login

Search

Recent Posts

Re: Rebuilding and Updating a 20 years old Xoops Website from 2.0.18? to 2.5.11

Rebuilding and Updating a 20 years old Xoops Website from 2.0.18? to 2.5.11

Re: NewBB v 5.1.0 b 6

Re: NewBB v 5.1.0 b 6

NewBB v 5.1.0 b 6

Re: XOOPS 2.5.11 search user is not working

Re: oledrion

Re: oledrion

Re: oledrion

Re: oledrion

Who's Online

Donat-O-Meter

Latest GitHub Commits

{{ record.sha.slice(0, 7) }} - {{ record.commit.message | truncate }}