I'm trying to make a new install on a different webserver. After making some files writable the installation goes well and the necessary table are made in the database (I checked). Then the screen jumps automatically to the login page, and after that the blank plogger/admin/plog-upload.php follows.
Checking with some echo's I can see that something goed wrong right in the first line of that plog-upload file:
I've tried over and over but with no succes. Safe-mode is off, register globals is on.
Like I said this is an install on another server, not which hosts my site (plogger runs ok there). I also noticed after deleting all cookies etc. that it doesn't matter what I use for username or password. I still get that same blank plog-upload.php screen...
Hmm. Are you sure you didn't modify any of the code before uploading it? I can't reproduce this problem anywhere although I have seen it before. It is usually blank if there is some sort of parse error on the page. Try editing the page and putting error_reporting(E_ALL); at the top.
Before doing this, I downloaded a fresh beta without changing anything to the code ;).
If I understand you correctly, I put the error_reporting(E_ALL); as the first code to be executed at the top of my plog-upload.php file. I even put it in the plog-globals file in the /admin folder and a few other files :) but still a blank screen. Again I put echo "test" right after your code and before the lines: require("plog-globals.php"); require_once("../plog-load_config.php"); include("plog-admin-functions.php");
'test' is shown in the page but nothing else. Strange. Any suggestion for further testing? or things I could check in the phpinfo.php page? My mysql host isn't localhost (as most of the time), but 'mysql.your.name'. Could that have an effect? (your.name is not something that should be changed in my own name: yournamewebhosting is the name of the hosting provider :) The database works ok and is filled with the right tables).
-----------------------------------
I've experimented a bit more. I used the echo to find out where it stopped appearing, testing each include/require from the start. It stopped when I arrived at plog-globals.php in the rootfolder of Plogger, so NOT the plog-globals.php in the /admin folder. So the plogger/admin/plog-globals.php calls for plogger/plog-globals.php and when using the code you gave me this gives me these 3 errormessages:
Notice: A session had already been started - ignoring session_start() in /home/sites/site29/web/plogger/plog-globals.php on line 5
Warning: main(plog-config.php): failed to open stream: No such file or directory in /home/sites/site29/web/plogger/plog-globals.php on line 15
Fatal error: main(): Failed opening required 'plog-config.php' (include_path='') in /home/sites/site29/web/plogger/plog-globals.php on line 15
It sais that plog-config.php doesn't exist, but it does exist and I mod changed it into 777. Also deleting the file has no effect.
Mike, have you had a chance to think about this problem I'm having here? I don't know what to do with it. On my personal testsite it's working great, but I'm also testing for a friend and can't get it to work on his server.
I prayed that you get struck with that Jack(because its hard to understand unless you see it yourself). I was trying to fix it for Lyn and there was no way out.
As it turns out Plogger requires PHP4.3.0 (because of the mysql_real_escape_string that is used all over the code). Trying to run it on older versions might actually cause this bug.
Okey, there a quite a few error_reporting() calls sprinkled all over the code. Try to comment them all out and see if having error_reporting(E_ALL) as the first line of plog-upload gives any meaningful error messages then.
This is some extra info from phpinfo.php. It also includes some things about magic quotes, because I remember trying some program that got stuck on the 'on' setting of one of those magic quotes.
safe_mode Off Off safe_mode_exec_dir no value no value safe_mode_gid Off Off safe_mode_include_dir no value no value
magic_quotes_gpc On On magic_quotes_runtime Off Off magic_quotes_sybase Off Off
and get this error: Parse error: parse error in /home/sites/site70/web/plogger/admin/plog-upload.php on line 12
which is the following code:
require("plog-globals.php");
,but then yournamewebhosting is running PHP 4.1.2, so following this thread I do read that I'd better ask them to upgrade... but you're the only one that still use GD 1.x as they run on 1.6.2 or higher,... No clue what that means but probably not GD 2.x
Mike, if you read what I wrote above (about echoing and following the files until where it went wrong), this means I put your line "var_dump(get_include_path());" right at the top of plog-globals.php in the plogger root directory.
Mike, would it help if I send you the complete page that phpinfo.php spits out? Or is there some information content there that some 'outsider' should not see/know because it could be used to hack the site or something? I just tried a new install for another friend who also has an account at this same provider, but same problems here :(.
Mike, a strange thing happened in this continuous story about the blank screens :). I just tried a third installation, same provider, different account, and this time a got as far as creating two collections. But when clicking on one of those collections or on the 'options' button on the top of that manage page... everything blank again. So it's not just plog-upload.php I think. It's something else, because like I said, clicking towards the options.php page the same thing happens again. :(
This is frustrating because their is really a limited amount of things I can do to determine this problem just by hearing your description. I can't reproduce the error, so it is obviously a server specific setting that is throwing a monkey wrench into the cogs.
Maybe you could send me your login information for the website and Plogger admin via email and I could investigate personally?
I think it's a PHP bug, but I'm not sure why it happens.
Sometimes PHP loses the value of include_path (which defaults to "." or the current directory). If that happens, then include() fails to load any files with relative paths.
Workaround: add the following:
ini_set('include_path', ini_get('include_path'));
as the very first line of plog-globals.php (the one in Plogger folder, not admin folder)
Well done Anti! I just tried your solution in the two other installations, and in both cases the problem was solved. I hope for the others on this page as well.
Is it harmfull to add this line to the next beta, just to be sure?
I've done (plog-globals.php downloaded from the trunk etc.) that but unfortunatly i still got a blank page at plog-upload.php. My hosting services uses: php 5.0.3
Mixing files from the current codebase into Beta2 is a recipe for disaster. If you are going to use the new files, you need all of them.
BTW, I don't think Plogger is compatible with PHP5. Sorry! I guess the only thing that isn't compatible with PHP5 is PHP shorttags, which are used in a couple of places (The Exifer Library comes to mind). <? should be replaced with <?php globally.
I give up really this time. If you search in the forum with "blank" you will get 5 threads with more less the same problem. So what is goes wrong and above all where?
Same problem here, but i try to do different and only the administration dosent function, because i have install here im my localhost first and then upload de files and base to web and the navigation on site is normal, only administration is bugged..., im not sure if the problem is the PHP v., because why the client side works and the back end no????, sorry about the bad english im Brazilian, and if someon want the Brazilian traslation i made it, and i send ...leave ur mail here... plz guyz lets resolve this.....
Guyz only one more thing... the PHP version isnt the problem... becouse in my localhost im running the PHP v.5.0.4, and on my web host is PHP 5.0.4 too!!!!!!
Localhost its works normal with no bugs and on web host have this..... version isnt a problem.... lets go guz lets resolve this.....
i found some mistakes on the sessions too, im working on it now... , but the pĀ“roblem to my host was resolve putting the global path to files testing inm yours...
For those of you who don't have access to your php.ini and are not running safe mode, you can accomplish the same thing by placing this code in your /admin/plog-globals.php file.
It wouldnt surprise me that there is a problem with the paths just like Tubadc says. I still have a blank screen at the admin-side and not at the client side 'cause that works fine. Gonna try the solution of Tubadc and let you know if it works for me.
I made probably a small mistake with the absolute paths "/usr/etc " instead of "usr/etc " but now i got the message:
Fatal error: Call to undefined function connect_db() in usr/home/web/snl58239/plogger/plog-globals.php on line 18
btw. all this blank screen stuff after the admin screen has definetly something to do with paths. Maybe it is helpfull to know what the php configuration, etc of my webhost is, you can find it on: http://web11.talkactive.net/phpinfo.php
My plogger installation has been running for over a year with no problems. On 12-28-06 I wanted to add some new photos and encountered the blank screen plog-upload.php problem. I added @ini_set("memory_limit", "64M"); to my /admin/plog-globals.php file to fix the problem. Thank you mike for the code.
hey I've tried it all having some serious probs uploading, some pics work fine while others go to a blank screen, then i have to use an ftp program to delete them so i can then go into manage and delete the empty pic there.
I am also experiencing the blank screen on the admin screen. There are a long list of possible fixes on here and althought I havent had time to read through them all, I will do so when I get home from work this evening.
My question is this... Is anyone running plogger on a system with PHP5.0.4 and MySQL 4.1.2? If so, are you having any problems? I thought maybe this was happening because I had php5, but I didnt see anyone else list that has their specs.
I found that by changing this global: $config['basedir']
...to a relative path the problem was resolved.
I think the overall issue is with trying to set global root relative paths. I work at a university and we have a convoluted apache configuration making it easier to develop with paths relative to the working directory or using absolute urls.
This file: plog-admin-functions.php
Calls the following files: require_once("plog-globals.php"); require_once("../plog-load_config.php"); require_once($config['basedir'] . "/plog-functions.php"); require_once($config['basedir'] . "/lib/exifer1_4/exif.php");
I changed $config['basedir'] to a relative path and the blank screen issue was resolved. I did a search and found 28 instances, I'm thinking it's best to just manually alter the script in those places??
The blank screen happened to me - I am hosting on Plesk 8 on linux - the problem seemed to be with the open_basedir restriction which plesk puts on all sites and subdomains by default. To change this on a plesk site you have to create a file called vhost.conf in the sites conf/ directory which is usually located at /var/ww/vhosts/[domain_name]/conf/
in the vhost.conf you need something like the following:
After creating the file you need to restart plesk - if you have command line access the command for this is /usr/local/psa/admin/sbin/websrvmng -u --vhost-name=[domain_name] and then restart apache