Ok, this one is tricky:
I have a production site running on a windowsXP box running xampp and Zikula 1.1.0. It has so many customizations (core hacks, I know!) and old modules running with asstons of important data that I can't advance beyond 1.1.* at this point. Every upgrade is a butt pinching nightmare and the site has been running for years. It's an upgraded .760 site and it has worked pretty flawlessly.
The problem is the hardware it runs on is slow and out of warranty and I've been forced to upgrade hardware. I got to choose my own specs this time and have a very beefy server running Ubuntu 10.04 Server, MySQL, PHP5, and Apache. It's a real solution to the slowness we've experienced by running on xampp.
I have tested Zikula 1.3.0 on the server and it works without a hitch. It's F!#^&ng fast in fact. I won't be able to move to 1.3.0 for a very long time due to Pagesetter, pnphpbb2 and postcalendar. I have tried to move my current site over to the new system and am having difficulties and have tried everything. Surely there is something that I'm not thinking of so I am coming to you guys for help:
I exported my database using phpMyAdmin on the old server and imported it into a database named the same using phpMyAdmin on the new server. I made sure the charset was the same and everything. The import was successful and the data seems fine on the new server.
I packed up the files on the old server using zip and unpacked them on the new server in a test location using CL unzip. Everything seemed to extract ok and file permissions were normal. There didn't appear to be any files missing.
I modified the config.php file to account for the new mysql password, the username is the same. The password was verified in a base64 converter. It's not the issue as far as I can tell.
When I browse to the test location/index.php I get a Blank Page. Nothing. Nada. When I make the password incorrect in the config file, I get the "Problem in database connection" page.
I have verified that PHP, MySQL and Apache work as the 1.3.0 install works perfectly. I have tried a number of troubleshooting steps all to no avail.
HELP PLEASE! :)
Watch
GitHub Core
Show your support for Zikula! Sign up at Github account and watch the Core project!
GitHub Modules
- rgasch created topic »Using PageUtil::addVar() to load script code« 11:48 AM
- michiel responded to »password problem« 10:01 AM
- mazdev responded to »Hide "Register new account" and change template to 3 col« 07:50 AM
- mesteele101 created topic »Zikula 1.3.3 - Site Search 1.5.2 - Unable to turn off plug-ins« 07:48 AM
- mesteele101 responded to »ERR (3): E_USER_ERROR: Smarty error: [in pagesvar:pagesitem2en line XXX]…« 25. May
- mazdev responded to »Pages 2.5.0 and updating - Page not found« 25. May
- mesteele101 responded to »Zikula 1.3.3 - Selecting a category in Pages not working« 25. May
Zikula Blog
- Anatomy of Open Source Projects on Mar 07
- Continuous Review on Mar 01
- Not Invented Here on Feb 24
- How to Contribute Your Code at Github on Jan 13
- 10 Steps to Coding-Nirvana: Tips for Successful Module Writing on Nov 12
- Submitting Bug Report Tickets That Get Results on Aug 17
- Cozi Tricks #1: Syntax Highlighting on Aug 07
Login
Site Move: Blank Page Nightmare
-
- Rank: Moderator
- Registered: Mar 15, 2005
- Last visit: May 30, 2010
- Posts: 1077
-
- Rank: Moderator
- Registered: Mar 15, 2005
- Last visit: May 30, 2010
- Posts: 1077
I should add that I just tried a successful install of Zikula 1.2.3 on another test location and it is working fine using the same DB credentials. I am truly stumped. The only thing different is the DB charset and the files.
Also, Turning on PHP error reporting yields no information. -
- Rank: Developer
- Registered: Feb 23, 2005
- Last visit: May 09, 2010
- Posts: 399
I've had the very same experience a couple of times. I never found an explanation for what happened but I did get around it. What I did: Using the backed up code base run a new install (still got your install files?). When its installed ok, drop all the DB tables and import the DB backup.
I've had to do that when I've moved a site from my dev server to the live server because I kept getting the same BLANK SCREEN you got. It's a long winded way to do it I know but I couldn't think of any other way, and it did work for me.
The only other thing I can think of is to disable any plugins in you theme. I've found they can sometimes give a BLANK SCREEN if there is a problem with one.
Denis -
- Rank: Developer
- Registered: Jun 16, 2003
- Last visit: May 29, 2010
- Posts: 1966
Quote
I won't be able to move to 1.3.0 for a very long time due to Pagesetter, PNphpBB2 and postcalendar.
I can't speak for the other modules, but PostCalendar has kept very current with Zikula releasesfor the last 18 months or so. I expect to have a fully compliant and OOP-based version of PostCalendar available within days of the final release of Zikula 1.3 so PostCalendar will not slow you down.
-
- Rank: Moderator
- Registered: Mar 15, 2005
- Last visit: May 30, 2010
- Posts: 1077
-
- Rank: Developer
- Registered: Jun 16, 2003
- Last visit: May 29, 2010
- Posts: 1966
jaenosjelantru
I'm using PostCalendar 4.0.2.
Hacked to pieces I might add.
well - that's going to be difficult. If you ever choose to try to upgrade - let me know and I'll try to give some guidance. But to be fair - PostCalendar and all these other modules aren't what's hold you back - its the fact that you've hacked things to pieces. You'll just have to bite the bullet and upgrade what you can and ditch the rest. -
- Rank: Developer
- Registered: Jun 16, 2003
- Last visit: May 29, 2010
- Posts: 1966
BTW - rereading your OP and wonder if you are trying to upgrade directly from .760 to 1.3 - if so, you are a lunatic.
you will need to upgrade to .764 then use the migration distribution to 1.1.2, then to 1.2.x then to 1.3. there are no direct routes. BTW - you will need to do a similar thing with PostCalendar. upgrade to 5.x on 1.1.2 then to 6.x on 1.2.x and then to 7.x (SVN ATM) on 1.3.
probably similar routes on the other mods. -
- Rank: Moderator
- Registered: Mar 15, 2005
- Last visit: May 30, 2010
- Posts: 1077
The version of Zikula I'm running is 1.1.0. I'm not trying to upgrade; just move it from one server to another.
Also, I have learned from my past errors on hacking things. Submit bugs/features and wait. Thats the way to do it.
I'll eventually move all stuff off of the old modules and onto newer/better ones, but I'm waiting for 1.3.0 + PM .9 for that. -
- Rank: Developer
- Registered: Jun 16, 2003
- Last visit: May 29, 2010
- Posts: 1966
if you get it moved, you should try upgrading to PostCalendar 5.5.3 and see if it works. that version still requires Topics though... -
- Rank: Moderator
- Registered: Mar 15, 2005
- Last visit: May 30, 2010
- Posts: 1077
Ok, so after turning on PHP errors, I finally found a few depreciated functions in the debug, header and footer. I replaced them with their appropriate PHP 5.3 replacements and I'm still getting a general system error. Coincidentally, I searched google and found a post from a few months ago where I apparently experienced the exact same issue:
http://community.zikula.org/module-Forum-viewtopic-topic-56842-start-0.htm#pid255525
Quote
System Error
Non critical error
An unknown error has occured. The following error message was returned by the system
Function eregi() is deprecated -
- Rank: Moderator
- Registered: Mar 15, 2005
- Last visit: May 30, 2010
- Posts: 1077
I guess I still have a few things to fix:
Quote
[06-Jul-2010 21:45:45] PHP Deprecated: Assigning the return value of new by reference is deprecated in /
var/www/tulsa-ops/test2/system/SecurityCenter/pnincludes/safehtml.php on line 608
[06-Jul-2010 21:45:45] PHP Deprecated: Assigning the return value of new by reference is deprecated in /
var/www/tulsa-ops/test2/system/SecurityCenter/pnincludes/HTMLSax3.php on line 161
[06-Jul-2010 21:45:45] PHP Deprecated: Function eregi() is deprecated in /var/www/tulsa-ops/test2/includes/debug.php on line 114
[06-Jul-2010 21:45:46] PHP Deprecated: Assigning the return value of new by reference is deprecated in /
var/www/tulsa-ops/test2/system/SecurityCenter/pnincludes/safehtml.php on line 608
[
root@win:/var/www#
-
- Rank: Developer
- Registered: Jun 16, 2003
- Last visit: May 29, 2010
- Posts: 1966
-
- Rank: Moderator
- Registered: Mar 15, 2005
- Last visit: May 30, 2010
- Posts: 1077
Apparently. I tried using preg_match to replace eregi in includes/debug.php and now I'm getting a new error:
Quote
[06-Jul-2010 21:52:15] PHP Warning: preg_match(): Delimiter must not be alphanumeric or backslash in /va
r/www/tulsa-ops/test2/includes/debug.php on line 114
Is the only solution to this downgrading to PHP 5.2? -
- Rank: Moderator
- Registered: Mar 15, 2005
- Last visit: May 30, 2010
- Posts: 1077
So I've just talked to drak. Upgrading to 1.2.3 will work under PHP 5.3 and I'm going to do it.
It will be painful to lose all of the core hacks I should never done in the first place but this will teach me a lesson. -
- Rank: Softmore
- Registered: May 30, 2005
- Last visit: May 31, 2010
- Posts: 340
The good news is, it's a lesson learned. I remember a programmer that was hired to do part of powerplant (a metrowerks c++ framework). He was supposed to write a text engine for it, but instead of subclassing the framework and leaving the core alone, he started hacking it to bits. It made a mess and once his boss found out, he did not last long there.
From what you have said so far, upgrading to 1.2.3 will fix your issues, but make sure you follow the suggested upgrade path. It is tedious, but my experience is, it works like a charm.
- Moderated by:
- Support
Users on-line
- 0 users
This list is based on users active over the last 60 minutes.
