Blank Pages in Section - not resolved to date - please help

Mann Zaph -- le 6 juin 2007

Problems with blank pages in parts of the site after install

Propriétaire

Mann Zaph

Avancement

Workflow

Besoin d'aide

Statut

Le problème a été enregistré

Envoi le 6 juin 2007 par Zaphmann

APPENDED June 11: This install gives strange errors in a host sitethat runs other CMSs OK. Still not resolved - can anyone help?

Hi, First thank-you I installed and a site where I could work on content inside three hours - amazing! This promises to be the best CMS I have seen.

But I seemingly have something set up slightly wrong:

After setting up my site, I populated it with the first option that puts in sample articles, blogs etc.

Then in Files · My blog · My jive discussion board · My manual · My Section I clicked on cover section. It gave me a blank page with the URL pointing to a php in section with an ID=.

THIS also happened when I clicked on my site map (balnk page).

THEN I clicked on modify this one - that took me to an editor space, into which I typed a basic article. When I hit SUBMIT once again I got a blank screen with this URL: http://www.morethanoil.com/articles/view.php?id=1

However, opening another tab in my browser I see the submit was taken??

What have I got wrong?

Thanks Zaph

PS: This CMS is amazing!

Manu	le 11 juin 2007 Nothing new, it is exactly the same as before: - Impossible to remove Sites/_yacs_to_remove. - Sub folders of _yacs_to_remove are owned by www/wheel with 775 rights and morethan/wheel has no rights on them ! - Sites/yacs/control/setup.php shows the same writing errors as my screenshot (your host service can look at it). - Your other folders as JoomlaSites are not in the same group : morethan/www (www group, not wheel) ! Can they try to take a look for these users and groups in the diffrent configurations (Unix, Apache, PHP, MySql, Ftp) ? I put the .htaccess (apache configuration file) but every commands are commented (disabled) so it doesn't change anything at this time. I am sorry to take all this time but this users/groups trouble is the last way for me to help you, after that i won't know what to do else. Zaphmann - le 11 juin 2007 GnapZ: OK here's the mix-up cause. Even when both ftp and cms (yacs) were set to the same group 'wheel' with 775 permissions -the webserver itself is a differnt group, so when a write is attempted to (for example) parameters folder, it is denied. When I first installed you may recall in an earlier message I mentioned that I had to set parameters folder and temporary folder to 777 (without knowing why). This got it installed but didn't fix the basic problem. Now everything has been changed to the same group as the webserver and it will install (I did the check but didn't go further). THIS Creates a different problem (maybe). because now any files created by the application will be owned by the webserver and I may not be able to manipulate them if I need to. The fact that yacs writes files sets it apart from Drupal and Wordpress which both keep everything in the database. However Xoops also wrote some files (and I had the same issues I now* realise) and Websitebaker not only writes files it INSTALLS from the interface (no ftp) so it owns everything and the user cannot access by ftp! It should now install, then we can see what's working, then when I come to change the skin later I don't know if I will be able to get into the files to do it, I think it might work. Hope so. So, over to you, unless you want me to install and update. Best Zaph GnapZ - le 12 juin 2007 Zaphmann : Ok, so we are back at the begining: nothing works as it should ! I have to stop here because i don't know what to do else. My knowledge is too limited to help you more. For any other helpers: - I saw that layouts of sections (boxesandarrows and yahoo) had a call to sectios/sections.php and not the others. I comented these lines and the sitemap came but no other section (empty skin or blank page). I did this to try to not re-declare sections.php . - At least, i put a 7.5alpha23 but it is all the same issue. - I disabled cache of yacs and my browser cache at every test. - Since they put the user morethan/www, there is no problem for yacs to write everywhere and by ftp too. - All PHP fatal errors return the line of the declaration of the classes but never we never known whitch scripts made the call. - I could get the sitemap then nothing. The same for the section Articles and some other pages. - In the control panel, i can access to everything but sections and smileys. Sorry and thanks to you Zaph Zaphmann - le 12 juin 2007 GnapZ: Thanks so much for trying so hard. I think there must be 2 or 3 things in error and one is solved. That is the ability for yacs to write wherever it needs (permissions & groups). That may have confused some earlier analysis. Gnapz: shall I delete the /yacs_to_delete/ folder now? Is there any way to proceed? Can anyone else help? I am pretty devastated but can't help thinking that this must be a simple, yet fundamental thing. What assumptions can be challenged? Has someone else installed this current yacs on a similar host? Is it broken code? All PHP fatal errors return the line of the declaration of the classes but never we never known whitch scripts made the call. Is it the combination of one particular s/w with another - for example this MySQL or this PHP version with yacs?? I do so hope it's not goodbye to yacs... GnapZ - le 12 juin 2007 Zaphmann : Yes of course you can remove this folder but i couldn't (not the same user/group) so maybe you will ask to your host service. Maybe i didn't see a very simple thing but as i know, it is the first time we have these problems and i am still not shure that it is because of Yacs. I hope that it will resolved, at least to understand what was the problem ! Thanks to your host service too.
Mann Zaph	le 11 juin 2007 Gnapz: Answers - All files are now set to 775 and the two users (my ftpname) and yacs (www) are in the same group, so now files should be able to be manipulated by both. The htaccess file is now 'switched on', although I can't see it with my ftp client I am assured that it is there. They had no insight on a PHP global parameter - if this is still important please give me more detail to talk to them about it. Do you want me to install now, or do you want to do it? And what do you want to do with the Sites/_yacs_to_remove folder? And finally, thank-you, again. Zaph GnapZ - le 11 juin 2007 Zaphmann : Ok, do not modify anything, i will continue my tests. You do not see any .htaccess file because you couldn't upload them before (automaticaly removed).
Manu	le 11 juin 2007 I have just finished to upload and start the installation. As you can see , yacs has no rights to write. So how did you install before I forgot to say that your site looks to run behind a proxy and i don't know if that makes troubles or not. Zaphmann - le 11 juin 2007 GnapZ: I installed by changing the permissions with my ftp s/w to 757. I have reset the permissions to 777 for the /yacs/ directory temporarily but I couldn't reset the Sites/_yacs_to_remove/ because I (ftp) don't own them. These other points you made: " .htaccess are not allowed. " I don't know what a .htaccess file is, how I set one up or what it does. I didn't have one there as far as I know. " Found some re-declarations in sections layouts but works on every other host service ... Maybe a PHP global parameter? " I'll ask my host " The user of ftp is different than the user of php. So what script can do has the user www/wheel and what you can do by ftp has the user morethan/wheel. These two users do not have the same rights! " and " Ask your host service about this two different users and how to remove by ftp the files and folders done by scripts ? I think that this is a big problem because yacs (www/wheel) cannot write on his files uploaded by morethan/wheel if this one doesn't give all rights (777). That's could be the reason of all your problems. " With other CMS I changed some files to 777 (a few only), after installation it was fine with 755 for folders and 644 for files. What settings & ownership does yacs require? " As you can see, i am uploading yacs from scratch but all done by the old installation (scripts) connot be removed or changed with the ftp user (see Sites/_yacs_to_remove). Do you have a "webmin" access? " I don't, I call them to get anything I can't do done. I'll talk to my host about these things and see what they say, they have other CMS running (like drupal) so they should know what to do. GnapZ - le 11 juin 2007 Zaphmann : Yacs works perfect with 775 folders and 644 files and doesn't need any special user or group but when yacs scripts wants to make changes, it should be with the same user/group as ftp user or the different users should have the same rights. This only on the host side, not due to any CMS. I wait for their answer.
Manu	le 11 juin 2007 Zaphmann : Summary of the weekend: - .htaccess are not allowed. - Found some re-declarations in sections layouts but works on every other host service ... Maybe a PHP global parameter ? - The user of ftp is different than the user of php. So what script can do has the user www/wheel and what you can do by ftp has the user morethan/wheel. These two users do not have the same rights ! - As you can see, i am uploading yacs from scratch but all done by the old installation (scripts) connot be removed or changed with the ftp user (see Sites/_yacs_to_remove). Do you have a "webmin" access ? Ask your host service about this two different users and how to remove by ftp the files and folders done by scripts ? I think that this is a big problem because yacs (www/wheel) cannot write on his files uploaded by morethan/wheel if this one doesn't give all rights (777). That's could be the reason of all your problems.
Mann Zaph	le 10 juin 2007 Gnapz - ultimately (when this problem is resolved, is there any advantage/disadvantage to having the yacs solution directly under my root, verses having a directory folder /yacs/ under my root? I ask because if your patch is specific to one or the other I should probably set it up the way it would stay. Not knowing where to go with this at the moment I am tempted to reinstall, but there's no particular logid to that. Bernard - any new ideas? thanks Zaph GnapZ - le 10 juin 2007 Zaphmann : You can install Yacs directly at your root ou in "yacs" sub-folder. If you want to use a different sub-folder, you will need to use "http://YourSiteName/YacsSub-folder/" or make a specific index.php. To continue tests, i will need to access to your yacs (associate id + password) + Ftp (URL + id + password). If you agree, send them to me by mail. Zaphmann - le 11 juin 2007 GnapZ: I sent you the details in mail, I got a copy in my mail, at least I hope it was a copy and that I didn't just send it to myself! Zaph
Mann Zaph	le 9 juin 2007 Hello there, I added the two files unzipped - they are small anyhow. The file loader rejects certain types of file (including php) so here are the contents of control.include.php as it is at the site: My root is /Sites (plural) My yacs folder is /yacs If I typed yaks (with a K) somewhere in a message that was a typo only. Hope this all helps - I'll be waiting! GnapZ - le 9 juin 2007 Zaphmann : Ok, please do not create files anymore, you just have to edit them and upload a new version. I thought that your yacs root was /yaks that is very important for the path_to_root. That i fix in the patch if to say to Yacs to enforce $_SERVER['DOCUMENT_ROOT'].'/yacs/' and there is no other script where this var is defined. The only thing i want to change is the $context['path_to'root'] = '../' with the good one who is fully used everywhere in Yacs. Let's test this one after what i don't know where this var is changed. Zaphmann - le 9 juin 2007 GnapZ: Thanks, there is some minor progress. First I wasn't sure where you wanted the latest patch: I tried at Sites/yacs/global.php first - no change - Then I tried at Sites/yacs/shared/global.php (renaming the original) and although I still get the blank page on site map the test data has changed the ../ in context path to this: $context['path_to_root']=/Volumes/XRAID01/Users/morethanoil/Sites/yacs/ The problems remain, blank pages if I try to go certain places like site map, pages... just blank pages. It's consistent that if I try to go to certain pages they work, while others blank - always the same: For example: Home » Site Map - blank » Categories - OK » Users -OK » Help - OK webmaster » » My profile - blank » Create a page - OK » Post an image - blank » Share a file - blank » Bookmark a link - blank » Review queue - OK » Logout - OK I think » Control Panel - OK » Help - OK A separate issue perhaps: With index.php at the same level as is /yacs/ if I click on home I get a 404 because it's looking for /yacs/index.php. I replaced the two files with the latest data (both XML)... I'm learning - hadn't noticed the tiny edit button Thanks Zaph GnapZ - le 9 juin 2007 Zaphmann : Good ! We have the good vars now. Another tip: when i give you patches to apply, it is allways to be extracted to your /yacs/ directory (sorry to forgot this). Now it looks like a cache problem. Take a look at ...Sites/index.php and ...Sites/yacs/index.php, they should both have the same size (version) that is : 9 995 bytes. I don't remember whitch version of yacs we are talking about, can you confirm that it is the 7.4 ? I rebuild the same shared/global.php just now based on the 7.4 to be shure that i didn't give you a 7.5alpha version. So please re-upload it and purge the caches (yacs 1st option and your browser). Then give back the log and the test page (as usual) and i would like the control.include.php (rename it as .txt file to upload here). I will have to go in 30mn so i will continue tomorow. Zaphmann - le 10 juin 2007 GnapZ: " Sites/index.php and ...Sites/yacs/index.php, they should both have the same size (version) that is : 9 995 bytes. " I had only 1 index.php file as I had earlier 'moved' it, not duplicated it. Now I have two the same - they both derive from the 7.4 download last done on 7 Jun from yacs site. The size I report is 43,905 bytes in each case (at server and locally after download). I'm getting the hang of this now I think. Installed new patch after purging caches. No apparent change - I have updated the log and testpage output files and added the control.include.php. " Now it looks like a cache problem. " Cache problem? How & where - at the server? Thanks for all your help, I'll try to get some sleep and look again tommorow. Zaph GnapZ - le 10 juin 2007 Zaphmann : You a re right, file size of index.php is 43,905 bytes. I don't know what i do at this time so i will go to bed too ... hope tomorrow will be better ! I downloaded your control file and removed it for security. One last thing: could you send simple text files instead of xml files who are very difficult to read for me in my text editor ? You don't need word for this, just rename files with .txt extensions. Good night (2:00 am here).
Manu	le 9 juin 2007 Is your installation at ...Site/yacs or ...Site/yaks ? I connot read the zip archives, the files included are extracted at 0 byte. Whitch software do you use ? i have 7-Zip. Can you send me your paramters/control.include.php hee too ?
Manu	le 9 juin 2007 I made a new modification on the patch who will work only in /yaks/ for your installation. Is there any /control or /global directories at your root (...morethanoil/Site/) ? Rename them if any. Do you have a .htaccess at yout root ? If yes, rename it too. Put the patch and go directly to the test page or the sitemap. If it doesn't work, stop tests and tell us. Zaphmann - le 9 juin 2007 GnapZ: Thanks for the new patch, which, as I understood it, I placed just beneath Sites/yacs/ - this seemed odd to me as the calls would surely go to the old file in shared by normal logic, but perhaps php steps its search through directory heirachy? There are no /control or /global directories at my root /Sites/ - just that index.php files and /yacs/ No .htaccess at root either, although I was going to ask how to get one there if I hadn't hit this problem. Using two browsers to keep access I went in a cleared cache in both, and in /yacs/ then I hit just categories (OK as usual), sitemap (blank as usual) and test page (OK too. So it behaved the same as without the new patch. I saved the data fom the test page and the latest entries on the error log in two files and zipped them and will attach them as soon as I send this. Thank-you so much for your persistence, a friend pointed out that this situation has probably not be resolved before because upon hitting it one side or the other would give up much earlier!
Mann Zaph	le 9 juin 2007 The attachment: it will not let me attach a .rtf file... So I'm trying a word XML format... except there's no attavh option again, so another new message I'm afraid - please delete these... GnapZ - le 9 juin 2007 Zaphmann : Just a tip when you have big text files (html, xml, word, etc), please Zip or Gzip them to keep space in this server and to make faster uploads and downloads. I saw that you find "add a new file" in the article to it will be easier for you next time. I am checking your file.
Mann Zaph	le 9 juin 2007 Hello - I have new access to the error log Here I will attach it Hope this reveals everything! I have looked at the php code a bit - very impressive - much better documentation within the code than what I normally have seen - it convinces me that this is worth solving and that yacs, while ambitious, is probably the best choice. Z - AH The file attch was denied This type of file is not allowed. So... I don't like to put all this text in the message but... I'll edit and start in from a week or so ago... of course some of these errors are other sites trying to reach mine and some of yacs ones were initial setup issues. and try to reattach... but I don't see an attach in edit mode, so I'll send a new message with attachment.
Mann Zaph	le 9 juin 2007 OK - I just did a dumb experiment, but I'm trying to isolate this. If I just go to home with a normal installation (original global/php) and do nothing I have in the top left corner Menu » Home » Site Map » Categories » Users » Help These last three options work, but http://www.morethanoil.com/yacs/sections/index.php gives a blank page. So just for fun I copied another index.php from categories to replace the sections/index.php http://www.morethanoil.com/yacs/sections/index.php then gave me the categories page successfully. So - the index.php code in sections is doing something fundamentally different from the other index.phps. I am printing the code (though no expert) to see what this difference might be. Thanks for your help so far - any other experts out there to help??
Mann Zaph	le 9 juin 2007 Update - no progress. I carefully installed te new patch, leaving the original global.php in place long enough to purge cache from the control panel (and this time I purged the first 3 radials and the last), also, different browser and cleared that cache. Once I put the new patch in place only blank windows whatever I try to get to by using the back button and selecting a place, or by direct URL typing. No error messages. To get a complex post test, I switched back to the original global.php (if the test is valid after that I don't know - but it's the only way I can get it), the result is below: There are a few differences but the critical line is still the same... " $context['path_to_root']=../ " Submitted request: $_REQUEST['a']=B $_REQUEST['hello']=world $_REQUEST['fontSize']=76 $_REQUEST['PHPSESSID']=vja18ss0v247883jgbshaisoq7 Script args: $context['arguments'][0]=123 $context['arguments'][1]=456 $context['arguments'][2]=789 Cookies sent by the browser: $_COOKIE['fontSize']=76 $_COOKIE['PHPSESSID']=vja18ss0v247883jgbshaisoq7 Session data: $_SESSION['watchdog']=1181350839 $_SESSION['browser_has_flash']=1 $_SESSION['surfer_id']=1 $_SESSION['surfer_capability']=A $_SESSION['surfer_editor']=yacs $_SESSION['surfer_email_address']= $_SESSION['surfer_name']=webmaster $_SESSION['surfer_gmt_offset']=-7 $_SESSION['workstation_id']=71.56.134.105 $_SESSION['server_id']=/yacs/ $_SESSION['heartbit']=7 $_SESSION['test_hits']=2 Session variables are stored correctly if the counter increments on page reload: 3 Global YACS variables: $context['host_name']=www.morethanoil.com $context['url_to_home']=http://www.morethanoil.com $context['url_to_root']=/yacs/ $context['self_script']=/yacs/control/test.php $context['self_url']=http://www.morethanoil.com/yacs/control/test.php/123/456/789?a=B $context['path_to_root']=../ $context['charset']=utf-8 Current Working Directory: YACS version 7.4, 070501-21:24:59 GMT, www.yetanothercommunitysystem.com Server attributes: $_SERVER['CONTENT_LENGTH']=11 $_SERVER['CONTENT_TYPE']=application/x-www-form-urlencoded $_SERVER['DOCUMENT_ROOT']=/Volumes/XRAID01/Users/morethanoil/Sites $_SERVER['HTTP_ACCEPT']=text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,/;q=0.5 $_SERVER['HTTP_ACCEPT_CHARSET']=ISO-8859-1,utf-8;q=0.7,*;q=0.7 $_SERVER['HTTP_ACCEPT_ENCODING']=gzip,deflate $_SERVER['HTTP_ACCEPT_LANGUAGE']=en-us,en;q=0.5 $_SERVER['HTTP_CONNECTION']=keep-alive $_SERVER['HTTP_COOKIE']=fontSize=76; PHPSESSID=vja18ss0v247883jgbshaisoq7 $_SERVER['HTTP_HOST']=www.morethanoil.com $_SERVER['HTTP_KEEP_ALIVE']=300 $_SERVER['HTTP_REFERER']=http://www.morethanoil.com/yacs/control/test.php/123/456/789?a=B $_SERVER['HTTP_USER_AGENT']=Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3 $_SERVER['PATH']=/bin:/sbin:/usr/bin:/usr/sbin $_SERVER['REMOTE_ADDR']=71.56.134.105 $_SERVER['REMOTE_PORT']=52199 $_SERVER['SCRIPT_FILENAME']=/Volumes/XRAID01/Users/morethanoil/Sites/yacs/control/test.php $_SERVER['SCRIPT_URI']=http://www.morethanoil.com/yacs/control/test.php/123/456/789 $_SERVER['SCRIPT_URL']=/yacs/control/test.php/123/456/789 $_SERVER['SERVER_ADDR']=10.0.1.209 $_SERVER['SERVER_ADMIN']=webmaster@morethanoil.com $_SERVER['SERVER_NAME']=www.morethanoil.com $_SERVER['SERVER_PORT']=80 $_SERVER['SERVER_SIGNATURE']= Apache/1.3.33 Server at www.morethanoil.com Port 80 $_SERVER['SERVER_SOFTWARE']=Apache/1.3.33 (Darwin) PHP/5.0.4 DAV/1.0.3 mod_ssl/2.8.24 OpenSSL/0.9.7l mod_perl/1.29 $_SERVER['GATEWAY_INTERFACE']=CGI/1.1 $_SERVER['SERVER_PROTOCOL']=HTTP/1.1 $_SERVER['REQUEST_METHOD']=POST $_SERVER['QUERY_STRING']=a=B $_SERVER['REQUEST_URI']=/yacs/control/test.php/123/456/789?a=B $_SERVER['SCRIPT_NAME']=/yacs/control/test.php $_SERVER['PATH_INFO']=/123/456/789 $_SERVER['PATH_TRANSLATED']=/Volumes/XRAID01/Users/morethanoil/Sites/123/456/789 $_SERVER['PHP_SELF']=/yacs/control/test.php/123/456/789 System environment: $_ENV['TERM']=xterm-color $_ENV['SHELL']=/bin/sh $_ENV['USER']=root $_ENV['PATH']=/bin:/sbin:/usr/bin:/usr/sbin $_ENV['PWD']=/private/var/root $_ENV['HOME']=/private/var/root $_ENV['SHLVL']=2 $_ENV['_']=/usr/sbin/httpd $_ENV['CF_USER_TEXT_ENCODING']=0x0:0:0 $_ENV['NoNeSuCh']= $_ENV['MODPERL_ENV_FIXUP']= Browser GMT offset: UTC -7 hour(s) Server GMT offset: UTC -7 hour(s) (2007-Jun-09 01:00:40) Output handlers: ['0']=default output handler user/group of this script: morethanoil[337065]/wheel[0] (root) user/group of this process: www[70]/www[70]
Manu	le 8 juin 2007 Try this patch and tell me if it works or not. Caution ! This patch is done only to make a test for this topic, nothing else. Do not keep it, we will work on this way if it works. Zaphmann.zip Zaphmann - le 8 juin 2007 GnapZ: I installed the patch at my host in the shared folder. The first thing I did then was try to go to my site http://www.morethanoil.com/, and the first thing I noticed was that my favicon showed up (before it was three small square boxes, black, grey and white) - but the window is blank (empty). I remembered to give the patch file the same secuirty as the other files (very open - 757). I then tried to get to the site by prior URLs (with http://www.morethanoil.com/yak...l/configure.php or http://www.morethanoil.com/yaks/setup.php - these gave 404 errors " The requested URL /admin.php was not found on this server. Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request. " and favicon gone. So I tried directly the index.php (http://www.morethanoil.com/index.php) and just a blank window (no error message) Now, follow carefully as I did something here... I cleared my browser cache & switched back to the original shared/global.php file so I could get in with http://www.morethanoil.com/index.php. That worked (note:no favicon). I clicked on the site map just under home in the top-left to confirm I had the same situation - yes, http://www.morethanoil.com/yacs/sections/index.php gave blank window no error message. I went back to http://www.morethanoil.com/index.php. Now I switched in the new patch and tested site map (same - blank) - BACK - but also now categories is blank window - BACK - and users... and alas, the login also So I guess the patch doesn't work, but maybe the favicon and blanks logic tells you something? What next? I'm still waiting for a new reply from my host - a previous one is below - they're busy, yesterday they looked at this and your code for 30 mins and thought that the php wasn't resolving correctly the directories in all instances, but was in some, but they said your code was very sophisticated and they wouldn't want to hack it. Here's a quote: with one log error: " Zaph, looking at your error logs, the most common PHP error is that it's trying to define functions multiple times or including pages more than once. This is one of the errors I'm seeing: [timestamp] [error] PHP Fatal error: Cannot redeclare class articles in ../articles/articles.php Unfortunately, most of this code is well above and beyond my level of experience, I'd either try to re-install or see if somebody else is having a similar problem. " GnapZ - le 8 juin 2007 Zaphmann : Ok, so one thing first: when you put a patch like this one, always think to purge the Yacs cache (control panel - purge) and your browser cache. The setup page is at /control/setup.php, not /control/configure.php and not /setup.php . We allready see re-declaration errors. It was because of redundant scripts who where not in their original folders. But there is too much scripts in your case. What about FTP transfert ? On your FTP tool, can you check if you can upload in Binary transfert mode ? Is it possible to you to try a local installation (on EasyPhp, Xampp or else) ? Do you have friends who can check the same blank pages ? Nothing is logical in this story ... Zaphmann - le 8 juin 2007 GnapZ: Thanks for the tips: I cannot any local imitation as far as I know (Xampp for instance has skipped on to only intel chip macs, I am on a power pc chip). With the original global.php in place I was able to log in, I flushed my browser cache, went to http://www.morethanoil.com/yacs/control/setup.php saw that it was the database maintenance page, so I went to the control panel (http://www.morethanoil.com/yacs/control/setup.php) and using purge, I purged the cache (the first radial button) there are 6 others I did not instigate. I went back and did maintenance also and hit the button saying Run one-time scripts but it said no scripts were executed, whatever that means. Then I switched in the new global.php patch, then I tried the " Browser and server information " test page - nothing output, just blank window. In fact I can't go anywhere once the patch is activated, all blank unless I go to yacs/index,php where I get The requested URL /yacs/index.php was not found on this server & a 404, so the path isn't right with the new patch. I checked my FTP transfert I have been uploading in Binary transfert mode only. I will go to a friend's house now and se if their PC gives the same result (I think it will). Coud it be that your system won't run on this environment? It seems odd, we had a Zope and Wordpress solution working fine in the same server. Perhaps I could try to install on one of your servers?! Stuck, but there's always a reason. Thanks Zaph GnapZ - le 8 juin 2007 Zaphmann : I made another patch who changes "path_to_root" with your "$_SERVER['DOCUMENT_ROOT']" and nothing else on it (no sanity check). Try this one, clear the caches and try to get the test page (/control/test.php). I don't think it is a Mac problem because Yacs is made in PHP who is an interpreted language and runs over any browser. I think it could be a special configuration of the provider that we never see before. Who is your hosting service ? Zaphmann - le 9 juin 2007 GnapZ: Just got back from the friend's PC - same blank pages there - don't see the zip attached to your message though! Z GnapZ - le 9 juin 2007 Zaphmann : It is the same zip file on the top of this discussion, i updated it.
Mann Zaph	le 8 juin 2007 Hello there, My ISP got back to me just now, here's what they said: " RAM has nothing to do with re-declaration of classes, the server is currently set to 16M per process for PHP. " So, I don't know what they mean by 're-declaration of classes', but 16M per process for PHP was what you wnted so I guess it's not that. Hopefully the codes will reveal a script error that only appears under certain circumstances. Does the environment of their server effect the php somehow? Is yacs tested in an environment such as theirs with a Mac apache server?? I wish I had better understanding so I could help more, , let me know if there's anything else I can try - your s/w seems well worth persisting with. PS - if you need passwords I can email them to you directly perhaps? Tahnks Zaph Edited by GnapZ: Do no show any email address, the one in your profile is the only one should be used here. Modifié par GnapZ le 8 juin 2007 GnapZ - le 8 juin 2007 Zaphmann : Ok thanks for this. It is the first time we have a feed-back like this so it could be interresting to know where the problem is. If your Host service speaks about classes re-declaration, that means that they have a log about this. If you allready tell them that you do not have any message, can they send you (us) this log ? The document_root as "../" is not good too and this is not from Yacs but from vars sent by the host. Let's continue to search ...
Bernard Paques	le 8 juin 2007 Can you please check with your ISP the maximum amount of memory given to PHP in PHP.INI? I suspect there is an issue here, that would explain why some scripts work as expected, and not others.
Mann Zaph	le 8 juin 2007 " It is just a test so you can move your actual installation to a sub folder named "yacs" and change manualy the "path_to_root" paramter in parameters/control.include.php by FTP with "/yacs/". " Actually I went though the whole upload and reset permissions process and tried it with yacs in a sub folder The result is the same (for example the site map gives blank page. - it's there now http://www.morethanoil.com/ - you can try yourself. " The max execution memory of PHP (Bernard told you about this a the begining but you didn't tell us the value). Be shure to have more than 8MB (16MB minimum recommended). " I have emailed my host for this info, they didn't think it was a serious possibility when I mentioned it before, they are not at work yet today. " The result of your /control/test.php (click on the complex test button) " Here it is! ?Submitted request: $_REQUEST['a']=B $_REQUEST['hello']=world $_REQUEST['CookiesEnabled']=1 $_REQUEST['art_3']=1180655840 $_REQUEST['art_4']=1180655876 $_REQUEST['art_5']=1180936168 $_REQUEST['REMEMBER_KEY']=00000000001_xn6r9a0yj12 $_REQUEST['PHPSESSID']=7m8jivmeshpgoobm9qm6d2bre3 $_REQUEST['editor']=dhtmlext $_REQUEST['form_mode']=custom $_REQUEST['fontSize']=76 $_REQUEST['style']=Spring coming Script args: $context['arguments'][0]=123 $context['arguments'][1]=456 $context['arguments'][2]=789 Cookies sent by the browser: $_COOKIE['CookiesEnabled']=1 $_COOKIE['art_3']=1180655840 $_COOKIE['art_4']=1180655876 $_COOKIE['art_5']=1180936168 $_COOKIE['REMEMBER_KEY']=00000000001_xn6r9a0yj12 $_COOKIE['PHPSESSID']=7m8jivmeshpgoobm9qm6d2bre3 $_COOKIE['editor']=dhtmlext $_COOKIE['form_mode']=custom $_COOKIE['fontSize']=76 $_COOKIE['style']=Spring coming Session data: $_SESSION['watchdog']=1181312404 $_SESSION['surfer_id']=1 $_SESSION['surfer_capability']=A $_SESSION['surfer_editor']=yacs $_SESSION['surfer_email_address']= $_SESSION['surfer_name']=webmaster $_SESSION['surfer_gmt_offset']=0 $_SESSION['workstation_id']=71.56.134.105 $_SESSION['server_id']=/yacs/ $_SESSION['test_hits']=1 Session variables are stored correctly if the counter increments on page reload: 2 Global YACS variables: $context['host_name']=www.morethanoil.com $context['url_to_home']=http://www.morethanoil.com $context['url_to_root']=/yacs/ $context['self_script']=/yacs/control/test.php $context['self_url']=http://www.morethanoil.com/yacs/control/test.php/123/456/789?a=B $context['path_to_root']=../ $context['charset']=utf-8 Current Working Directory: YACS version 7.4, 070501-21:24:59 GMT, www.yetanothercommunitysystem.com Server attributes: $_SERVER['CONTENT_LENGTH']=11 $_SERVER['CONTENT_TYPE']=application/x-www-form-urlencoded $_SERVER['DOCUMENT_ROOT']=/Volumes/XRAID01/Users/morethanoil/Sites $_SERVER['HTTP_ACCEPT']=/ $_SERVER['HTTP_ACCEPT_ENCODING']=gzip, deflate $_SERVER['HTTP_ACCEPT_LANGUAGE']=en $_SERVER['HTTP_CONNECTION']=keep-alive $_SERVER['HTTP_COOKIE']=CookiesEnabled=1; art_3=1180655840; art_4=1180655876; art_5=1180936168; REMEMBER_KEY=00000000001_xn6r9a0yj12; PHPSESSID=7m8jivmeshpgoobm9qm6d2bre3; editor=dhtmlext; form_mode=custom; fontSize=76; style=Spring coming $_SERVER['HTTP_HOST']=www.morethanoil.com $_SERVER['HTTP_REFERER']=http://www.morethanoil.com/yacs/control/test.php $_SERVER['HTTP_USER_AGENT']=Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/418.9.1 (KHTML, like Gecko) Safari/419.3 $_SERVER['PATH']=/bin:/sbin:/usr/bin:/usr/sbin $_SERVER['REMOTE_ADDR']=71.56.134.105 $_SERVER['REMOTE_PORT']=51456 $_SERVER['SCRIPT_FILENAME']=/Volumes/XRAID01/Users/morethanoil/Sites/yacs/control/test.php $_SERVER['SCRIPT_URI']=http://www.morethanoil.com/yacs/control/test.php/123/456/789 $_SERVER['SCRIPT_URL']=/yacs/control/test.php/123/456/789 $_SERVER['SERVER_ADDR']=10.0.1.209 $_SERVER['SERVER_ADMIN']=webmaster@morethanoil.com $_SERVER['SERVER_NAME']=www.morethanoil.com $_SERVER['SERVER_PORT']=80 $_SERVER['SERVER_SIGNATURE']= Apache/1.3.33 Server at www.morethanoil.com Port 80 $_SERVER['SERVER_SOFTWARE']=Apache/1.3.33 (Darwin) PHP/5.0.4 DAV/1.0.3 mod_ssl/2.8.24 OpenSSL/0.9.7l mod_perl/1.29 $_SERVER['GATEWAY_INTERFACE']=CGI/1.1 $_SERVER['SERVER_PROTOCOL']=HTTP/1.1 $_SERVER['REQUEST_METHOD']=POST $_SERVER['QUERY_STRING']=a=B $_SERVER['REQUEST_URI']=/yacs/control/test.php/123/456/789?a=B $_SERVER['SCRIPT_NAME']=/yacs/control/test.php $_SERVER['PATH_INFO']=/123/456/789 $_SERVER['PATH_TRANSLATED']=/Volumes/XRAID01/Users/morethanoil/Sites/123/456/789 $_SERVER['PHP_SELF']=/yacs/control/test.php/123/456/789 System environment: $_ENV['TERM']=xterm-color $_ENV['SHELL']=/bin/sh $_ENV['USER']=root $_ENV['PATH']=/bin:/sbin:/usr/bin:/usr/sbin $_ENV['PWD']=/private/var/root $_ENV['HOME']=/private/var/root $_ENV['SHLVL']=2 $_ENV['_']=/usr/sbin/httpd $_ENV['CF_USER_TEXT_ENCODING']=0x0:0:0 $_ENV['NoNeSuCh']= $_ENV['MODPERL_ENV_FIXUP']= Browser GMT offset: UTC -7 hour(s) Server GMT offset: UTC -7 hour(s) (2007-Jun-08 14:20:04) Output handlers: ['0']=default output handler user/group of this script: morethanoil[337065]/wheel[0] (root) user/group of this process: www[70]/www[70] GnapZ - le 8 juin 2007 Zaphmann : Ok, there is two things: - $context['path_to_root']=../ is not good, it should be something like "/Users/morethanoil/Sites/yacs/". I will check the script for this var. - $_SERVER['HTTP_ACCEPT']=/ should have more parameters as "text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,/;q=0.5" It take a look in the scripts and tell you back.
Mann Zaph	le 8 juin 2007 Gnapz You'd asked: " "Help search engines to index more pages. (articles/view.php/123)" or "This system does not support the mapping of args in the URL. (articles/view.php?id=123)" ? " I don't recall, pretty sure it was whatever the default is... " I confirm that your path_to_root must be "/". Did you try to install yacs in a sub-driectory to check these errors ? " OK - I notice that at www.yetanothercommunitysystem.com yaks is installed in its own directory beneath the root. ie. http://www.yetanothercommunity...hp/article/2959 - I ditched the yaks level and installed all the files under yaks at my root because I wanted seo efficiency. Q1: Could this cause the problems? Q2: How does the home page come up in Yaks if the file/directory yaks is at that level?? I suppose, to test that I should try an install that way... I will. GnapZ - le 8 juin 2007 Zaphmann : I don't know if this could change something but i continue to try new ideas. It is just a test so you can move your actual installation to a sub folder named "yacs" and change manualy the "path_to_root" paramter in parameters/control.include.php by FTP with "/yacs/". To let it work by the same url, just leave a copy of /index.php at your site root. Index.php knows search in its directory and try /yacs/ too. Can you send us two important information: - The max execution memory of PHP (Bernard told you about this a the begining but you didn't tell us the value). Be shure to have more than 8MB (16MB minimum recommended). - The result of your /control/test.php (click on the complex test button) ?
Mann Zaph	le 8 juin 2007 Bad news I did a complete reinstall - alll new 7.4 download to my mac, upload to host, reset security on all files. The only hitch this time was that I used http://www.morethanoil.com/ in the path field and at the end of the rendering I got the 404 because the script had http://www.morethanoil.comhttp...orethanoil.com/ in it (ie twice). So I went back into control panel and instead of that I put in / in the path Things then proceded exactly as before. For example, in the top left under site map I get a blank page from this link: http://www.morethanoil.com/sections/index.php but the 3 links under it in that menu all work fine This is a site crippling problem but also it points to being something about a setting and/or compatibility of php. Time to think laterally & logically. GnapZ - le 8 juin 2007 Zaphmann : One idea, i just remember that i had the same issue with my subdomains using url-rewriting. On system parameters, did you select "Help search engines to index more pages. (articles/view.php/123)" or "This system does not support the mapping of args in the URL. (articles/view.php?id=123)" ? I confirm that your path_to_root must be "/". Did you try to install yacs in a sub-driectory to check these errors ?
Mann Zaph	le 8 juin 2007 Hello Yaks people, In an effort to resolve this blank page issue I have been in the control panel doing some purging and rebuild efforts, then I tried a few more areas of the site and I went to the sample editor that had been created and tried to change its password, which I did and then I got this extraodinary error: An attempt to go to a url with my url in it twice! " http://www.morethanoil.comhttp://www.morethanoil.com/users/view.php?id=2 " As I haven't gone that far yet, I am going to copy what I can of my input and then purge all fiels at my host, then upload a new copy of YACs and try again. I will report in again in a few hours with an update. Thanks Zaph.
Mann Zaph	le 7 juin 2007 Hmmm... this is a stinker I spoke at length with my host and they tried hard, they said that blank screens are typically path or php code errors. I had wondered if there was a path error (which causes similar behaviour) and they found that the site had been going to a www.stephouse.net/~morethanoil which is a subdomain off their server and was wrong. This is what was generated by me leaving the / in the Path (URL) to root directory duing install. instead they put http://www.morethanoil.com/ in the Configuration panels... System... Path (URL) to root directory and on their side they now see correct routing. Q: Is that type of setting for path what your system expects or should it be more like /Volumes/XRAID01/Users/morethanoil/Sites as other CMs's have needed? --- Now my favicon shows up! --- But the blank screens continue, for example on the home page top left, under menu, click site map: " http://www.morethanoil.com/sections/index.php " and blank screen... My configuration is: YACS 7.4, 070501-21:24:59 GMT, www.yetanothercommunitysystem.com PHP 5.0.4 MySQL 4.1.13a Apache Apache/1.3.33 (Darwin) PHP/5.0.4 DAV/1.0.3 mod_ssl/2.8.24 OpenSSL/0.9.7l mod_perl/1.29 Server time zone UTC -7 hours I love your system, please don't say I have to abandon it!!!!
Mann Zaph	le 7 juin 2007 Gnapz - thanks for continuing to try to help. The file rights are by default with this server host & my user 644, I changed some to 777 to see if it helped and no difference. " Take a look at your scripts size. I had some troubles with some FTP tools with automatic transfert mode. I all enforce to Binary mode because Ascii mode changes datas (Windows to Linux servers). " I am not to technical and don't understand this, or how to do it. I am on a Mac working via web to my host who is on latest apache, php, mysql etc. I work with them a lot they are like you guys, up to date. Java & Javascrpits are enabled in my browser (Safari) I tried Firefox and got IDENTICAL responses to clicks. " enabled Javascripts for you Yacs URL. " I don't know what this means unless you mean the browser. " Did you try different skins ? " Yes, I am in digital (one of the ones given by the system and I haven't changed anything, I switched to another skin and got IDENTICAL responses. This means it's not the skins, it's not the browsers, it's not the permissions... I think. GnapZ - le 7 juin 2007 Zaphmann : Ok i don't know what to try else. I don't remember the yacs version you use. Tell me and if you want, you can send me by mail the archive of your database and parameters. So i will try it on my host and check it.
Mann Zaph	le 7 juin 2007 Hello - thanks for the feedback, I switched on verbose. Then From my home page, When I clicked on read more " http://www.morethanoil.com/articles/view.php?id=5 " I got a blank screen. when I clicked on contents: " http://www.morethanoil.com/comments/list.php?anchor=article%3A5 " I got a blank screen. when I clicked discuss " http://www.morethanoil.com/comments/edit.php?anchor=article%3A5 " it went through to let me add a comment, which I did, and hit submit (fine) then I chose to edit it and it gave me the right entry screen, then I hit submit again and blank screen!! " http://www.morethanoil.com/articles/view.php?id=5#comments " Then I was stuck in a loop somewhat. In between all these steps I am using my browser back button. The comment is there though as I found by using the search... From the home page edit me box i continued and hit trackback " http://www.morethanoil.com/links/trackback.php?anchor=article%3A5 " which took me to the right place, back again and I hit my section " http://www.morethanoil.com/sections/view.php?id=13 " and blank screen. It's strange how some of these php calls work and others don't - I suspect permissions, I'm going t o take a closer look at that. No sign of any extra info from verbosity yet. PS: I have a friend sold on switching to YAKs, from Zope, but I want to iron this out first. Viva Zaph GnapZ - le 7 juin 2007 Zaphmann : Thats look strange ... for the file rights, we usualy use 644 but check your host privacy about rights, sometime they do not accept too low or too high rights. Take a look at your scripts size. I had some troubles with some FTP tools with automatic transfert mode. I all enforce to Binary mode because Ascii mode changes datas (Windows to Linux servers). Finaly, be shure that you enabled Javascripts for you Yacs URL. Did you try different skins ?
Mann Zaph	le 6 juin 2007 My host is really up to date with everything on their systems. But how would I find out about the memory useage? I am pretty sure it isn't a memory issue as I have pumped around some bigger php at this host recently. It seems more like a configuration issue to me, but what do I know! Any other ideas out there? Thanks Zaph GnapZ - le 7 juin 2007 Zaphmann : Did you make a derivated skin ? If yes, try with an original one. Clean Yacs cache and your browser cache then if it works that means that it is a problem in your template.php and/or skin.php If you are using an original (not derivated) skin, switch to the verbose mode in the system control panel. Go to Control Panel - System (Configuration panels) - Verbosity (System parameters): Check "Provide as much information as possible (development server)." This should show you more messages that you can feed-back here.
Bernard Paques	le 6 juin 2007 Maybe a memory issue. Have you tried to double the memory given to PHP in PHP.INI?