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. Installation Troubleshooting 
  4.  / Update 2.0.13.1 to 2.2.3 Final - Stuck on Closed For Maintenance Screen
Register
1
bsimm
Update 2.0.13.1 to 2.2.3 Final - Stuck on Closed For Maintenance Screen

  • 2005/11/19 15:11

  • bsimm

  • Just popping in

  • Posts: 31

  • Since: 2003/4/13


I've already updated 2 of my other sites to 2.2.3 successfully. I updated my 3rd site to 2.2.3, ran xoopsupdate.php, went to my site and got the Site Closed for Maintenance screen. I logged in with my admin ID password, and it says incorrect password. I reran xoopsupdate.php, and the normal update screen doesn't come up. I get the Closed for Maintenance screen still. Can't run xoopsupdaet, can't login, and can't get to the admin screen to update the system module. I found the info about the hotfix for some upgrade problems, and tried uploading that. Then I run xoopsupdate.php, but I'm still just getting the closed for maintenance page. I have verified that this isn't something due to my browser cache, too, because I get the same thing from another PC that I haven't visited the site from. I've also cleaned out the template_c directory. This makes no sense. What have I overlooked?
2
jdseymour
Re: Update 2.0.13.1 to 2.2.3 Final - Stuck on Closed For Maintenance Screen

Look in your database under "yourprefix_config" check and change two items if necessary. There is a setting to open the site here, and make sure gzip is set to off.

HTH.
3
bsimm
Re: Update 2.0.13.1 to 2.2.3 Final - Stuck on Closed For Maintenance Screen

  • 2005/11/19 16:09

  • bsimm

  • Just popping in

  • Posts: 31

  • Since: 2003/4/13


Part way there. That got me into the site. Now I'm missing menu items on the admin screen. Namely the Administration opiton under the Modules menu. The Blocks and Users menus are missing, and the Misc Tools menu has nothing under it. So I can't update the System module, or turn on my blocks at this point. But other than that, the site is working, let's me log in, etc. I cleaned out template_c again, but didn't help. Reupload the 2.0.13.1-2.2.3 patch files?
4
jdseymour
Re: Update 2.0.13.1 to 2.2.3 Final - Stuck on Closed For Maintenance Screen

Try reuploading the full version files. Maybe there was some corruption during transfer.
5
bsimm
Re: Update 2.0.13.1 to 2.2.3 Final - Stuck on Closed For Maintenance Screen

  • 2005/11/20 3:09

  • bsimm

  • Just popping in

  • Posts: 31

  • Since: 2003/4/13


I downloaded the zip file for 2.2.3 final, complete install (all I had before was the patch). I uploaded all the files. I deleted templates_c again. And I reran xoopsupdate.php. Now I go into the admin page, and am still missing the menu items mentioned before, so I cannot modify blocks, or update the system module.
6
jdseymour
Re: Update 2.0.13.1 to 2.2.3 Final - Stuck on Closed For Maintenance Screen

Did xoopsupdate.php run successfully a second time. It normally should not, because it creates new tables if they do not exist in the database. I am at a loss, hopefully someone else will know what to do from here.

I would check your database for any double entries, since you say that you ran the script more than once.
7
bsimm
Re: Update 2.0.13.1 to 2.2.3 Final - Stuck on Closed For Maintenance Screen

  • 2005/11/20 14:54

  • bsimm

  • Just popping in

  • Posts: 31

  • Since: 2003/4/13


I can't find any dup entries, but I'm not 100% sure where to look pertaining to this admin menu. It looks like the menu gets loaded in theme_adminnav.html, in the themes/default/navigation directory. But I'm not yet sure what file is calling that, and where the smarty variables are getting set.

Everything in the XOOPS setup seems to work. I manually put in the links for the block settings page, and some of the other pages that the links are missing for. They all worked fine. I just have to manually link to them. Everything else seems to work

So, does anyone know about how the admin menu is built, and where I should look for corruption that would limit the items that are showing up in this menu???????
8
bsimm
Re: Update 2.0.13.1 to 2.2.3 Final - Stuck on Closed For Maintenance Screen

  • 2005/11/20 19:42

  • bsimm

  • Just popping in

  • Posts: 31

  • Since: 2003/4/13


My problem has kinda changed since I first posted. I am going to post a new question specifically about the admin menu. Maybe someone will be able to give me some pointers about how this is generated so that I can find what has been corrupted.
9
beach_defend
Re: Update 2.0.13.1 to 2.2.3 Final - Stuck on Closed For Maintenance Screen

hi,
I have just tried to upgrade my company site (2.0.X->2.2.3) after practising on an internal XOOPS upgrade (which went very well!).

I hadn't closed the site but I get the same issues as near as I can tell as bsimm.

When I first ran the update script, I got an error in trying to create 'xoops_profile_category'. I dropped this table and another that it complained about next time and then got a white screen (even though PHP Debug is on) - might be our error_reporting setting, I knoe display_errors is set to 0 in php.ini.

So then I refreshed the site (hpfm.com.au) and I get the default starting module/block but with no menus, login etc.

When I try to go user.php, I get the expected login page, but I cant log in with any username/passwd combo. I tried to use the password reminder, but was told that the email address is unknown.

I looked in the xoops_user table and all the entries are correct down to the md5'd passwords.

I'm a bit phazed now because I've effectively killed off my web-site. I will keep looking but any help would be muchly appreciated.
10
beach_defend
Re: Update 2.0.13.1 to 2.2.3 Final - Stuck on Closed For Maintenance Screen

Hi again,
I added
ini_set('display_errors','1');
error_reporting(E_ALL);

and get


Fatal error: main(): Failed opening required '....../class/smarty/core/core.load_plugins.php' (include_path='.:/www/includes:/www/includes/phpreports:/usr/local/php/includes:/usr/share/pear') in /www/html/xoops-2.0.7.3/html/templates_c/db%3Aprofile_admin_fieldlist.html on line 3

So I uploaded the new Smarty directory contents and it seems to have worked, though there are some permission issues with wiwmod.

I'll go back now and try to figure out what to do next.
(1) 2 »

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

195 user(s) are online (159 user(s) are browsing Support Forums)

Members: 0

Guests: 195

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