1
danistell
500 internal server error after upgrading from 2.2.0 to 2.2.3
  • 2005/8/28 10:50

  • danistell

  • Just popping in

  • Posts: 27

  • Since: 2005/5/19


Hello,
I get 500 internal server error when I try to access to some pages of my XOOPS site after upgrading from 2.2.0 to 2.2.3.
Modules affected:
AMS
WFLINKS
PROFILE
So I get 500 error when I try to access to any AMS article, to some WF links, to userinfo.php in PROFILE.

What about this?
Thank you,
Danistell

2
danistell
Re: 500 internal server error after upgrading from 2.2.0 to 2.2.3
  • 2005/8/28 11:10

  • danistell

  • Just popping in

  • Posts: 27

  • Since: 2005/5/19


I get also this warning XOOPS on readable pages:
Warning [Xoops]: Smarty error: unable to read resource: "db:system_block_online.html" in file class/smarty/Smarty.class.php line 1084

3
rowdie
Re: 500 internal server error after upgrading from 2.2.0 to 2.2.3
  • 2005/8/28 11:13

  • rowdie

  • Just can't stay away

  • Posts: 846

  • Since: 2004/7/21


In admin 'modules adminstration' did you update the system module?

4
danistell
Re: 500 internal server error after upgrading from 2.2.0 to 2.2.3
  • 2005/8/28 11:23

  • danistell

  • Just popping in

  • Posts: 27

  • Since: 2005/5/19


When I tried to update system or ams or profile or wflinks module, i got 500 internal server error.
In admin pages, i got a module.textsanitizer.php warning php.
So I replaced 2.2.2 version module.textsanitizer.php with older 2.2.0 version of the same file.
Now, it seems that all modules work and I can update successfully system module.
And warning XOOPS also disappeared.

Now, will I have problems whith older module.textsanitizer.php version runinng on my site?

Thanks to all,
Danistell

Login

Who's Online

216 user(s) are online (48 user(s) are browsing Support Forums)


Members: 0


Guests: 216


more...

Donat-O-Meter

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

Latest GitHub Commits