Subject:*
<
Name/Email:*
<
Message Icon:*
<
Select*
<
Message:*
<



Click the Preview to see the content in action.
Options:*
<
Confirmation Code*
<
1 + 9 = ?  
Input the result from the expression
Maximum attempts you can try: 10
*
<
     

Re: Upgrading problem from 2.0.10 to 2.0.14
by davidl2 on 2006/7/17 14:42:36

All sorted.. but at least your request has been "bumped" a bit further now
Re: Upgrading problem from 2.0.10 to 2.0.14
by Housefly on 2006/7/17 14:15:25

Quote:

davidl2 wrote:
Please don't repost - a simple "bump" will bring the post up again...


Sorry david12, I didn't know that I had posted twice. My connection was too slow and so I had clicked post button more than once. Please delete any extra post. Thanks.
Re: Upgrading problem from 2.0.10 to 2.0.14
by davidl2 on 2006/7/17 10:19:51

Please don't repost - a simple "bump" will bring the post up again...
Upgrading problem from 2.0.10 to 2.0.14
by Housefly on 2006/7/17 8:37:45

I followed the instruction given at http://devteam.xoops.org/releases/xoops-2.0.14.html

and I had overwritten the old files & folders with the new files and folders except mainfile.php. But I'm getting the following error message when I tried to open the homepage itself.
le="color: #000000"><?php This page cannot be displayed due to an internal error. If you are the administrator of this site, please visit the XOOPS Troubleshooting Page for assistance.


I cannot login to admin nor open any pages:

xoops_md5.php shows the followings:
le="color: #000000"><?php ./class/mail/xoopsmultimailer.php content invalid ./class/xml/rpc/xmlrpcparser.php content invalid ./images/logo.gif content invalid ./include/common.php content invalid ./kernel/privmessage.php content invalid ./modules/system/admin/mailusers/mailform.php content invalid End of files check.


Will the above problem causes error?

Additionally I've followed the instruction at https://xoops.org/modules/smartfaq/faq.php?faqid=80
About blank pages problem and specially I've paid attention to No. 3

le="color: #000000"><?php 3. If you can't get to the administration page, and don't want to mess with mysql, but don't mind messing with PHP, then edit the file "include/common.php". Near line 83, change "error_reporting(0);" to "error_reporting(E_ALL);".


But it doesn't report anything. The first error page continues to display.

Upgrade from 2.0.10 to 2.0.14
PHP Safe Mode : Off(tried switching ON using .htaccess but no help)
MySQL version: 4.1.19-standard
PHP Version : 4.4.2


I have backup of the old files and folders, should I restore the old ones or is there any other way to upgrade successfully? I'll be happy to hear any suggestions and helps.

Thanks alot.

Who's Online

111 user(s) are online (55 user(s) are browsing Support Forums)


Members: 0


Guests: 111


more...

Donat-O-Meter

Stats
Goal: $15.00
Due Date: Jul 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $15.00
Make donations with PayPal!

Latest GitHub Commits