Blank pages invasion.
Submitted by simic on Thu, 03/13/2008 - 00:26.
Hello everyone.
What I have is nothing new, blank page instead of a login.
I was working with PP ver version 0.8.0.2 one on the local
WAMP 1.6.x platform - and had editing some new funcionalities
for my own ideas, but then I had to format...
I've installed the new: WampServer (2.0b), which includes :
- Apache 2.2.8
- MySQL 5.0.51a
- PHP 5.2.5
copied PP to /www/ folder and got blank page on the login.
OK, so I did another installation and got:
- so everything was fine (I guess).
When debugging switched true, I've got probably known
problem of DB NOT loading
So what went wrong?
Maybe I need to turn on particular apache modules, PHP extensions...
but in the install screen, all options were green. So what's the problem?
There's something weird with the error screenshot:
it tries to open a file on drive C: but actually looks for a file that is on drive D:.
Do you have a symlink between the two folders?
It seems that you've reinstalled from on old installation: did you check that config/config.php is correct regarding your new location? Can you try an installation from complete scratch? (that is in a new folder with a new download)
-
Tim
I would agree with Tim about trying a fresh install.
Also, this might be a cache issue. Try deleting the cache/autoloader.php and see if that helps.
I just had this same problem when trying to move from one server to another. PP was trying to include files from the server path of the old server and thus getting a fatal error.
Deleting hte autoloader.php file fixed the problem, but it seems that that info shouldn't be only stored in that file. If even 1 include doesn't work, the script should try to freshly figoure out the path again rather than giving up (at least it seems that should be possible to me). I guess I can see the benefit of caching the work done to determine the path, but there's no reason to be totally dependent on the potentially out of date information in the cache.
Another useful tool would have been a potential line in the config file to set the server path manually and override any other sources for it (I looked through the db and the config file carefully for a server path setting before checking the forum).
I agree, the snapshot error indicates the problem.
When the script is registering global values it sets there
absolute path. I've changed it to relative. And that's it.
But, why use absolutes there?
Thanks
I'm also having a blank pages problem. It started today when other users started using the sytem. I had also ugraded PHP to 5.2.5 on my server the night before. Anyway, I did a fresh install and used acSimple instead of the Marine skin, but the blank pages started again after about an hour.
Caching has been mentioned as a possible cause. I am wondering about this too.
>simic - has the problem recurred since changing to a relative path? If not where did you change this.
was:
[root_of_PP]/cache/autoloader.php
The absolute patch to the globals
since first install occurs 219 times
in this file.
I suggest changing:
this: "'[Drive]:/[Folders]/[root_of_PP]/"
to that: "'"
nothing else,
regards
simic, thanks for posting your fix. Unfortunately it didn't work on my system.
Seemed ok after I made the change yesterday, but today no one on my team is able to access any pages.
Looks like we are going to have to move on and try another solution.
1) if the problem is intermittent, make sure that you have allocated enough php memory for the system to run.
2) Also, make sure that you have not corrupted the installation files. Often when people upload the files to a server they get corrupted in the process. It is best to upload the zip file and then unzip and install from the server.
If a fresh installation is still causing blank page errors, please report back with more information about your setup. You can also try turning on the debug setting in the config file, which might expose where the problem is.
Thanks for your suggestions. I have 32M allocated for php. Should that be sufficient?
Today Project Pier is working again. None of us were able to load any pages yesterday. I did change the autoloader paths back to absolute.
32M is probably enough - but it really depends on what else might be running on your server. I would also suggest looking at your apache logs and php error logs for any hints if the problem persists.
I am getting blank pages now and I found out today that one of the users has only gotten blank pages on Project Pier since Thursday...even when other users have been able to access pages intermittently.
The users have lost confidence in this system so we are going to have to try something else. It is great when it works.
Hi cmc,
is there anything else running on the server? If you have another PHP application, does it cause any problems?
I have done a few installations but never ran into your problems (except for when I was working on the code or had a bad configuration). I'm running Apache2.2, PHP 5.2.5 and MySQL 5.0.45.
Also, have you noticed any kind of pattern for when it doesn't work? Are there many users connected? are they connected on a different network maybe?
There's one thing you can check besides PHP logs and Apache logs: the ProjectPier logs in cache/logs.php. If ProjectPier is called and encounters the error, it should be logged there. If PHP stops before that, maybe not...
One last thing you can try is to look into what Ryan said and increase the memory allocation if possible.
Good luck!
-
Tim
Thanks for the suggestion Tim. I get this error over and over in the ProjectPier log. All of say Session "default". There are only 3 users right now. All on different networks.
Session "default" started at 2008-03-17T19:23:00+0000
#1 ERROR: Error: require_once(application.php) [function.require-once]: failed to open stream: No such file or directory in '/var/www/vhosts/lab208.com/httpdocs/projects/init.php' on line 129 (error code: 2)
Time since start: 0.0046839714050293 seconds
have you moved your installation at any point?
Is that path the correct place for your files?
Is this a new/fresh installation that is giving you problems?
is it possible your installation files got corrupted during an upload?
Have you modified any of the files with patches or other hacks/changes? are you using any translations?
What other software is running on your server?
Can you also turn on the debug flag in the config.php file and see if that provides any additional error messages?
Also, feel free to come chat in the IRC channel and someone might be abel to help you directly.
This is a fresh install in this location. I did move project data from the DB of a previous installation.
The require statement in init.php is calling 'application.php'. Relative to init.php the path is 'application/application.php'. The absolute path is '/var/www/vhosts/lab208.com/httpdocs/projects/application/application.php'.
It is possible that the files were corrupted, but the system worked fine when I was the only one using it.
No hacks or patches. My first install used Marine, but I did not install it this time in case it was related to the problem.
There are other php/mysql apps running. Or did you mean software like Tomcat or Coldfusion?
I turned the debug flag back on and I will see if I can get some other errors.
Thanks again.
ok - lets address 2 points first.
lets make sure your installation files weren't corrupted. did you unzip the package on your server? or did you unzip locally and then upload all the files individually - this is often very error prone.
I meant - What other php/myls apps are running? but if you're running other things besides A/M/P that might also be useful to know.
I applied the temporary fix in this thread last night
- http://projectpier.org/node/523
Everyone has been able to access Project Pier today with no errors AFAIK.