XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk


(1) 2 3 4 5 »


1
dplittle
Re: Help Recovering System

  • 2013/3/21 17:14

  • dplittle

  • Just popping in

  • Posts: 49

  • Since: 2004/9/15


At this point I have tried these things ...

1) renamed the actual module directory in the modules folder
2) Disabled the module in the modules table via phpMyAdmin

But I hadn't even thought to fix the Blocks!

That at least got my system back up and running.

Thank you.

Now I'll see if I can start over from scratch.
Topic | Forum


2
dplittle
Help Recovering System

  • 2013/3/21 16:04

  • dplittle

  • Just popping in

  • Posts: 49

  • Since: 2004/9/15


Something happened during a module upgrade and now my whole system is down.

When I try to access the main page nothing is even shown...no login screen, header, footer, etc.

If I manually type in the module admin path I can get some things to be displayed but as soon as the rown for the upgraded module is to be shown, the template engine stops out putting the page.

If I change the name of module's subdirectory I get the error that the "Module file for news Not Found!"

I really don't mind of I lose all the data in this module (it's only news items that are fairly short-lived) so if there is a way I can delete the module from the back door and then completely reistall that would be fine.

Can anyone help?
Topic | Forum


3
dplittle
Re: Broken log in for 2.0.14 Site

  • 2009/11/19 22:57

  • dplittle

  • Just popping in

  • Posts: 49

  • Since: 2004/9/15


I am completely back!

I recreated the tables that were having problems and restored data from older backups. The only thing I lost was stored private messages and we don't use thee much anyway!!

Thanks for all the help. Now I can move on to upgrading.

David
Topic | Forum


4
dplittle
Re: Broken log in for 2.0.14 Site

  • 2009/11/19 22:42

  • dplittle

  • Just popping in

  • Posts: 49

  • Since: 2004/9/15


Eureka! I was at least able to log back in after I dropped the session table and recreated it!

Does anyone know what these other tables are for?

online
priv_msgs
xoopsheadline

I can guess and I'm thinking I'll just lose saved private messages but I'm a little worried about the xoopsheadline table since I do use that module.

Since it looks like the tables were corrupt I'm guessing I''m not getting data from them now anyway. Think I can just go ahead and recreate the others and see what happens? Any other suggestions?
Topic | Forum


5
dplittle
Re: Broken log in for 2.0.14 Site

  • 2009/11/19 22:15

  • dplittle

  • Just popping in

  • Posts: 49

  • Since: 2004/9/15


So here's a little more info ... I went out to phpMyAdmin to disable the modules and see several tables listed as "in use".

xoops_online
xoops_priv_msgs
xoops_session
xoops_xoopsheadline

If I try and get info on these the error message given is

#1016 - Can't open file: 'xoops_online.MYI'. (errno: 130)

I found this file ...

http://dev.mysql.com/doc/refman/5.0/en/myisam-repair.html

and am going to run through the steps there but could this be the problem?
Topic | Forum


6
dplittle
Re: Broken log in for 2.0.14 Site

  • 2009/11/19 20:31

  • dplittle

  • Just popping in

  • Posts: 49

  • Since: 2004/9/15


Quote:

wcrwcr wrote:
Did you try a complete DB repair?
The typo you are talking aboiut is almost due to a db corruption (eg. XOOPS users)


Is this something I can do outside the XOOPS interface? I can't log into XOOPS at all so it would have to be an external executable script/etc.
Topic | Forum


7
dplittle
Re: Broken log in for 2.0.14 Site

  • 2009/11/19 14:12

  • dplittle

  • Just popping in

  • Posts: 49

  • Since: 2004/9/15


Quote:

Mamba wrote:
Just disable them from the database --> set "isactive" in the table "modules" to 0


Thanks Mamba. That's exactly what I needed.

Are there any I shouldn't disable?
Topic | Forum


8
dplittle
Re: Broken log in for 2.0.14 Site

  • 2009/11/19 0:27

  • dplittle

  • Just popping in

  • Posts: 49

  • Since: 2004/9/15


Has anyone got a way that I can bypass the first log in screen (the one that gets me stuck in a loop)?

Commenting out some code on my pages? Changing a setting in the database? A config file, perhaps?

THe other option is if I can disable modules from within the database.

I just need to get the modules disabled before I attempt the upgrade. I'd rather not mess up all my modules. I've got too many files and images stored there to have to redo them all.

Thanks
Topic | Forum


9
dplittle
Re: Broken log in for 2.0.14 Site

  • 2009/11/18 20:43

  • dplittle

  • Just popping in

  • Posts: 49

  • Since: 2004/9/15


Quote:

Mamba wrote:
You should upgrade directly to XOOPS 2.4.1. See the upgrade instructions there.


Just another quick question ... I went and looked at the 2.4.1 info and found the sections on upgrading. The two set of instructions dealing with version 2.0 seem to exclude my version ... 2.0.14. One says "Upgrading from XOOPS 2.0.* above 2.0.14 and 2.2.*" and the other says "Upgrading from any XOOPS ranging from 2.0.7 to 2.0.13.2"

Is this a typo? Should I use the first sset of instructions?

Thanks

David
Topic | Forum


10
dplittle
Re: Broken log in for 2.0.14 Site

  • 2009/11/18 20:36

  • dplittle

  • Just popping in

  • Posts: 49

  • Since: 2004/9/15


Quote:

Mamba wrote:
So before you go with the upgrade, if you still have access to Admin, you might first "deactivate" your modules (don't uninstall them, just deactivate), then upgrade XOOPS, and then activate your modules one by one, to make sure that they work.

I can't log in as admin either. When I log in I get into the same cycle or log in, get message, get sent back to log in.

Is there some way for short circuit this to still get logged in and deactivate the modules? Maybe comment out some code in log in pages?
Topic | Forum



TopTop
(1) 2 3 4 5 »



[Advanced Search]

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

242 user(s) are online (155 user(s) are browsing Support Forums)

Members: 0

Guests: 242

more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits