1
mannyo
Problem upgrading from 2.0.18 to 2.0.32b Help!
  • 2008/12/18 3:04

  • mannyo

  • Just popping in

  • Posts: 25

  • Since: 2008/12/18


I copied all the folders as instructed and when I go the upgrade folder as specified I get this message error can someone help?
"Error: Smarty error: the $compile_dir 'XOOPS_VAR_PATH/caches/smarty_compile' does not exist, or is not a directory."

Can someone help please?

2
mannyo
Re: Problem upgrading from 2.0.18 to 2.0.32b Help!
  • 2008/12/18 4:17

  • mannyo

  • Just popping in

  • Posts: 25

  • Since: 2008/12/18


Sorry for my ignoramus request... found the fix in another section of the forum by hard coding the path in the template.php file. Upgrade worked...
However, my homepage is gone and it's a blank page... nothing displays... I can get into the admin section but that's it. All the data appears to be in the modules...
Any ideas

3
sailjapan
Re: Problem upgrading from 2.0.18 to 2.0.32b Help!

Of course, you backed up the site and db before attempting the upgrade.

Go back to your backed up version and do the upgrade again. Judging by your error report, I'd say you either didn't follow instructions regarding mainfile.php or the files you've uploaded to your server are incomplete.
Did you run the file checker (checksum.md5 & checksum.php)?

Never let a man who does not believe something can be done, talk to a man that is doing it.

4
mannyo
Re: Problem upgrading from 2.0.18 to 2.0.32b Help!
  • 2008/12/18 7:52

  • mannyo

  • Just popping in

  • Posts: 25

  • Since: 2008/12/18


Dude, I'm soooo new at this stuff... it's 2:30AM and my eye balls are about to come out of my eye sockets. Ok... I backed up the site, but not the database... I can access all the modules by going directly into mysite/modules/newbb or whatever and the site works that way. All the modules work. With my theme and all. I think it is a protector issue.. I believe this is what happened... I had kept my Old Protector module in the modules dir and I had two proctectors running somehow...
Didn't realize there was another one in the my root/xoops_lib/modules/protector.
So I deactivated and uninstalled proctector all together and deleted it from my original module folder.
Still doesn't work, the home page that is, and now I have no Core/Protector so to speak although the files are still where they should be root/xoops_lib/modules/protector
I need help guys pm me if you can or here but I need to bring my site back up... what a nightmare...should have left it alone....aghhh
Don't know where or how to run the file checker either.
Thanks for your help.
Site is http://www.eastcoastrcclub.com/xoops to view just add the /modules/newbb

Site config:
XOOPS Version - XOOPS 2.3.2
PHP Version - 4.3.11
MySQL Version - 5.0.67-log
Server API Version - cgi-fcgi
OS Version - Linux


safe_mode - Off
register_globals - Off
magic_quotes_gpc - On
allow_url_fopen - Off
fsockopen - On
allow_call_time_pass_reference - On
post_max_size - 8M
max_input_time - 60
output_buffering - 0
max_execution_time - 30
memory_limit -
file_uploads - On
upload_max_filesize - 2M

5
mannyo
Re: Problem upgrading from 2.0.18 to 2.0.32b Help!
  • 2008/12/18 9:21

  • mannyo

  • Just popping in

  • Posts: 25

  • Since: 2008/12/18


went back to my backed up version now my site is not working any more. Lost all my pictures, no user login, no admin login... Just gonna have to spend another 200hrs redoing everything... this really really blows...

6
ghia
Re: Problem upgrading from 2.0.18 to 2.0.32b Help!
  • 2008/12/18 10:46

  • ghia

  • Community Support Member

  • Posts: 4953

  • Since: 2008/7/3 1


Quote:
it's 2:30AM and my eye balls are about to come out of my eye sockets.
Work only on websites when you are fresh and sharp.
Quote:
I backed up the site, but not the database
This is bad! 95% of your site is your database. I hope you have a recent copy. Try to make at least every month a backup.
Quote:
I had kept my Old Protector module in the modules dir and I had two proctectors running somehow...
Didn't realize there was another one in the my root/xoops_lib/modules/protector.
The Protector is a 3d module and has two parts one in the normal module directory and a second part in a protected directory (outside of the web root).
Quote:
Don't know where or how to run the file checker either.
This is explained in the release notes.

7
mannyo
Re: Problem upgrading from 2.0.18 to 2.0.32b Help!
  • 2008/12/18 13:37

  • mannyo

  • Just popping in

  • Posts: 25

  • Since: 2008/12/18


Quote: "this is bad"

... indeed this is bad, what I nightmare... My site is my Pride and Joy ) and my members depend on it...
Just woke up after a 2 hour nap and starting from scratch....
Database is fairly recent may 2 months old. I'm just gonna loose the recent forum and news activity on the site. If am able to clean restore (wont keep my modules folder on the server)

Ok Restored my old files the site comes up but can't login and I get an error message HTTP 404 page not found when attempting http://www.eastcoastrcclub.com/xoops/user.php


Is there anyway to manually rebuild the site? Or at least have admin access to it? Or Can I do a clean install "import" my files from my 2.0.18 site?

Can anyone really help? Yahoo Messenger,
phone, heck I'll even spend my Chistmas money...sniff...sniff...any guns for hire?

8
mannyo
Re: Problem upgrading from 2.0.18 to 2.0.32b Help!
  • 2008/12/18 14:07

  • mannyo

  • Just popping in

  • Posts: 25

  • Since: 2008/12/18


Also if I try to re-run the upgrade, the upgrade login page comes up but I get an error message if I try to login.


extas/login.php gives me this.

Warning: main(/path/to/xoops/directory/mainfile.php): failed to open stream: No such file or directory in /home/content/e/a/s/eastcoastrc/html/xoops/extras/login.php on line 7

Warning: main(/path/to/xoops/directory/mainfile.php): failed to open stream: No such file or directory in /home/content/e/a/s/eastcoastrc/html/xoops/extras/login.php on line 7

Warning: main(): Failed opening '/path/to/xoops/directory/mainfile.php' for inclusion (include_path='.:/usr/local/lib/php') in /home/content/e/a/s/eastcoastrc/html/xoops/extras/login.php on line 7

9
ghia
Re: Problem upgrading from 2.0.18 to 2.0.32b Help!
  • 2008/12/18 15:42

  • ghia

  • Community Support Member

  • Posts: 4953

  • Since: 2008/7/3 1


It seems running now.

10
mannyo
Re: Problem upgrading from 2.0.18 to 2.0.32b Help!
  • 2008/12/18 16:09

  • mannyo

  • Just popping in

  • Posts: 25

  • Since: 2008/12/18


ouuuuffff....
Ok I found that I was missing a couple of files...
Went back to the old install folder and grabed three files that I was missing and copied them to my root folder...
It is working now... although I am missing a few pictures from my upload folder... due to the interval from last backup...

So I'm gonna try this one more time...
Backup my database first
Backup my XOOPS folder
copy the protector file as stated in the release notes or uninstall protector completely before performing the upgrade?
I'm still gonna need to change that template.php file for the path to xoop_data

Anything else?

Help...help...I do not want to screws this up again... I'm going on 2 hours of sleep in the past 26 hours...

thanks

Manny

Login

Who's Online

319 user(s) are online (252 user(s) are browsing Support Forums)


Members: 0


Guests: 319


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