XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk
  1. Board index / 
  2. XOOPS Community Support forums / 
  3. Beginner's Corner 
  4.  / Broken log in for 2.0.14 Site
Register
1
dplittle
Broken log in for 2.0.14 Site

  • 2009/11/18 19:35

  • dplittle

  • Just popping in

  • Posts: 49

  • Since: 2004/9/15


For some reason my site has just broken. Whenever a user logs in, they get the "Thank you for logging in" screen but then it immediately reloads the log in page.

I'm still running 2.0.14 so I thought maybe starting an upgrade process would help fix the problem. I downloaded the 2.0.14 to 2.0.15 files and uploaded them but I can't even log in to start the upgrade. When I do, it just goes straight back to the log in screen.

I've looked though all the files and don't see any "rogue scripts" or any .htaccess files in the directory so I don't think the pages have been hacked.

If someone can help me get past this issue I can go ahead and start the upgrade process to the current version.

Thanks

David
2
Mamba
Re: Broken log in for 2.0.14 Site

  • 2009/11/18 20:08

  • Mamba

  • Moderator

  • Posts: 11409

  • Since: 2004/4/23


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

Of course, you might need to update all the modules as well to newer versions. 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.

If any of them doesn't work, you will need to update them to a newer version, if such exist, or look for replacement.
3
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?
4
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
5
DonCurioso
Re: Broken log in for 2.0.14 Site

dplittle,

"Upgrading from XOOPS 2.0.* above 2.0.14 and 2.2.*"

This is for you.
6
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
7
Mamba
Re: Broken log in for 2.0.14 Site

  • 2009/11/19 0:53

  • Mamba

  • Moderator

  • Posts: 11409

  • Since: 2004/4/23


Just disable them from the database --> set "isactive" in the table "modules" to 0
8
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?
9
Mamba
Re: Broken log in for 2.0.14 Site

  • 2009/11/19 14:38

  • Mamba

  • Moderator

  • Posts: 11409

  • Since: 2004/4/23


The "System" - that's the only one that you need to keep active.
10
wcrwcr
Re: Broken log in for 2.0.14 Site

  • 2009/11/19 18:11

  • wcrwcr

  • Home away from home

  • Posts: 1114

  • Since: 2003/12/12


Hi all

@dplittle

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

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

373 user(s) are online (251 user(s) are browsing Support Forums)

Members: 0

Guests: 373

more...

Donat-O-Meter

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

Latest GitHub Commits