| Re: Update 2.0.13.1 to 2.2.3 Final - Stuck on Closed For Maintenance Screen |
| by beach_defend on 2005/12/7 13:11:38 I am geeting other problems do I'll move onto another topic. Will return here if I find out what is happening. I should note here that I can access the site in Firefox but IE gets serious load errrors that seem to be Javascript related. Hard to describe, but it looks like a recursive reload of the page for a long time and then ulitmately half a page and some exposed html tags. I'll start aonther thread... |
| Re: Update 2.0.13.1 to 2.2.3 Final - Stuck on Closed For Maintenance Screen |
| by beach_defend on 2005/12/7 11:55:47 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. |
| Re: Update 2.0.13.1 to 2.2.3 Final - Stuck on Closed For Maintenance Screen |
| by beach_defend on 2005/12/7 11:15:52 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. |
| Re: Update 2.0.13.1 to 2.2.3 Final - Stuck on Closed For Maintenance Screen |
| by bsimm on 2005/11/20 19:42:00 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. |
| Re: Update 2.0.13.1 to 2.2.3 Final - Stuck on Closed For Maintenance Screen |
| by bsimm on 2005/11/20 14:54:14 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??????? |
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $15.00 |
| Due Date: | Jul 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $15.00 |
|
|