if you are getting blank page with Atahualpa 3.6.x (Suhosin issue)
If you are unable to activate or even preview 3.6.x give these a try and let us know if one of the following work.
First add the following to your .htaccess file HTML Code:
php_value suhosin.executor.include.whitelist bfa:// HTML Code:
suhosin.executor.include.whitelist bfa:// see also: http://forum.bytesforall.com/showthread.php?t=12673 You may also have to add a path to your php.ini file as mentioned in this post. |
Oops... did not work for me. I did an auto update of the theme and it said all was OK, but it is not. Blue gray blank screen.
I have the site running in a sub folder and put the unzipped file php.ini you provided in both the /public_html and the /rto folder but still seeing only a blank page. I have a backup but a bit cumbersome to pull it down and redo. Any other suggestions are very welcome. :) Site is RAINTREE I deactivated plugins but still the same. Thanks in advance. Kmack |
It does appear to work for some and not others. An alternative to recovering a backup is just to upload 3.5.3 into a separate folder via FTP. You would then have an atahualpa and an atahualp353 folder. Since you did an automatic upgrade you will have to add your header and logo images if you had any in the atahualpa/images folder.
We generally recommend a manual backup so you can switch back to a previous version if something doesn't go quite right. |
Wow! Thanks for the very fast reply. I'll see if I can undo it by using my backup that is saved in the cloud. Appreciate your help.
kmack |
It does not work here - so I loaded an ini to every folder in my system. Not working.
Hans Quote:
|
Where do one find the 3.5.3 ?
|
Look in the 'New Versions & Updates' forum and you will find a link
|
Quote:
yep, same with me, don't work, only white blank screen, i put it in my WP root, still same. after that put in public_html and same result |
I'm sorry on my bvision.nl site the 3.5.3 still works, but i tried everything to get the 3.6.1. working, WP super cache off, implemeted the ini file, but no atahualpa working...
|
I try add php.ini but donnīt work
|
I am sorry, but to be brutally frank, the instruction given in this thread is 100% bogus because a php.ini file can be located anywhere depending on the host's configuration and the original poster had no clue about this.
|
If you will notice I said give this a try and let us know if it works. These instructions worked for me on one site that was having problems. I put the php.ini file in and the problems went away. I took it out and the problems came back. I put it back in and the problems went away again. This issue APPEARS to be an environmental issue and this was just one idea to try. So this may be bogus for some but I know it worked for at least one person.
|
Quote:
The above php.ini directive, and the file made for download, has a wrong syntax. I have confirmed that it will not work with this syntax. The correct syntax for an ini directive is: parameter.name = value Thus, try this line in your php.ini file: Code:
suhosin.executor.include.whitelist = bfa:// Code:
suPHP_ConfigPath /home/<your-user-dir>/ By doing both the above changes we fixed the white page problem. But trying the line "php_value suhosin.executor.include.whitelist bfa://" in .htaccess did just crash the sites, and we immediately removed the line. php.ini should be located in the very root (/) of your account (above www), while the .htaccess file usually is located in the www or public_html folder. |
Kurt - thank you for the detailed explanation!
|
Thanks Kurt. It will be good to test that syntax. Where did you find that syntax? I had a specific instance of it definitely working although I did not try the syntax with the = in it but I suppose it could have been a fluke. That's why I wanted people to test it.
I have edited the original post with the alternative syntax so that both are there until we get a difinitive. |
Quote:
At Suhosin web site you can find the name of the parameter, exactly as you used it. I still doesn't understand fully why this ini setting seems to completely disable the suhosin module. But fact is that it disappears from phpinfo(). At last I have a tip, as an alternative to making av file conaining <?php phpinfo(); ?>. This is to install the weodprees plugin "WP Serverinfo". It will give you all information on both PHP and MySQL on your server. One of the web hosts I have investigated is ProISP. But on both web hosts the suhosin module disapperas completely. If this is to some security thing, I think that it was a bit too easy to just disable it. I would have expected that it just displayed a whitelist of "schemes". I would be quite interetes in wich line in the Atahualpa code thet triggers the suhosin module to kill the whole process so abruptly. The whole thing really needs investigation. |
Quote:
Where can the 3.5.3 version of the theme be found? I tried to find it through wordpress but only option is 3.6.1. it seems that this is the only way to fix the problem. Have tried the delete button mentioned by JD and what you mentioned, neither worked. |
You can get any previous versions at wordpress.bytesforall.com.
|
Tried it out without success. Got a blank page with 3.6.1 and 3.6.4.
Greets Chris |
In an effort to reproduce this problem I set up an Ubuntu Server 10.10 VM with lubuntu9.3 (LAMP), no small task for this non-*nix guy. This also includes PHP 5.3.3 with Suhosin patch 0.9.9.1. I installed WP 3.0.4 and added Atahualpa 3.6.1 with no problems.
Looking back at my production server (which I have no control over other than the web server content), it is running PHP 5.2.13 with Suhosin 0.9.7. Does anyone else have any version information they can share that might help us figure out where the root cause of the problem might be? |
I went a step further and set up a fresh WP 3.0.4 in a sub-directory on the production server that is giving me trouble. Lo and behold, Atahualpa activated with no problems. This leads me to believe that Suhosin (at least version 0.9.7) may not be the problem after all.
I have already tried installing all the Plug-ins on my local VM that I am using in production but none of them appear to have broken anything. I am going to try some more experiments later, maybe tomorrow, to try and pin-point the problem. I'll keep you posted. Feel free to PM me if you have suggestions on specific things I might want to check. |
I added plug-ins to the test site one-by-one until The Events Calendar blew up the admin pages. It looks like something in this plug-in doesn't play well with Atahualpa. I may look at other plug-ins but the was the top rated calendar app and seemed to be the best featured.
What can I do to help figure what's wrong with the plug-in? Update: Events Manager Extended and My Calendar also have problems. |
The Event Calendar plugin is NOT compatible with WordPress 3.0 and above. It must not be used as is!
If you desperately need a version of Event Calendar that works with WP 3.0+ I have a modified version running quite well. |
Do you think that this problem with suhosin will be corrected with future versions? Is this a problem with this particular theme or with Wordpress in general? I'm confused because I was reading on another thread about "Wordpress requirements." My host (dreamhost) gave me a choice if I wanted to switch to the new version of php (5.3) and when I tried it, my site would not work. I switched back to 5.2 and all is fine, but I'm just worried that at some point in the future I won't have a choice and will have to use the version with suhosin in it. I don't want to have to move hosts or change themes if I don't have to, but I want to prepare myself if this is going to be a huge problem. Thanks for any insight you could give me.
|
Quote:
Quote:
Quote:
Quote:
|
Thank you for clarifying things for me. I will check on the dreamhost forums how to edit these suhosin options.
|
Quote:
|
Oh if only there was a way to have the hundreds of plugin and theme developers use the same naming conventions and standards...I mean, the big software companies all agree on the same standards...oh wait, that's right, they don't....sigh :(:(
|
Thank you very much for the solution suggested below of adding the following line to my php.ini file: suhosin.executor.include.whitelist bfa:// which resolved the problem on HostPapa with WP 3.0.5 and Atapualpa 3.6.4.:)
Quote:
|
This is incredibly frustrating. I'm transferring a site using 3.6.1 from one server to another, and lo and behold I get all of these errors.
I don't even have Suhosin installed on my server, which mean now I've got to try and determine why exactly it's not working. Will investigate and get back to you all. |
This helped me
PHP Code:
|
I understand that there is a Suhosin issue (which, I have no idea what that means) and that is why I have a white screen. I had installed this theme on another account, and liked it so much thought I'd install it onto my own. Never had any problems on the other account. My current one is an add onto my current website (a sub directory). I don't know what Suhosin means, and I see I'd have to go into files and start changing things, and not have any assurance there will be success. Sorry guys, but with zillions of themes to choose from that do work, this is just too much effort!
|
Quote:
|
Hello.
1. I have no experience in PHP, CSS or whatever to build a website. In web hosting, just to set up Wordpress. 2. According to me. The problem is not suhosin, my shared hosting does not have suhosin installed. 3. The problem is not a plugin, I've tried a fresh installation and no plugin. 4. I've also tried installing version 3.6.4 in a different folder. With or without 3.5.3. 5. In all cases there is a white screen, but I should explain the side bars can be seen, left or right. I have several menu and look on the screen without problem. But the center column does not appear. As I have no knowledge of these things, very likely I'll say something stupid. In version 3.6.4 should be a code that tries to do things with suhosin, but at the same time, hinder the operation when suhosin is not present. That's because those who do have suhosin installed, solve the problem with the solution presented here. But those like me, and some have said here, do not solve the problem with the solution for suhosin. Thank. |
How did you determine that your shared hosting does not have Suhosin installed.
|
Beside that, you can ask the web hosting. I've searched my info.php.
I use three resources without having to ask the web hosting. 1. In my web hosting forum, a clear answer, we do not use, and we do not plan to use Suhosin. 2. I look at the support page of my web hosting, there is no word on Suhosin. 3. My info.php, when I add the recommendation made here, and then refresh my info.php. My php.ini, do not add the code because Suhosin not installed. I think what happens is that some web hosting want to give customers more freedom, although they have more work. Other web hosting, solve problems easily, limiting the customer with Suhosin. lmilesw. Thanks for your quick response. |
adrian - what is your url?
|
If I have done this well, the URL of my Spanish website is in contact information.
juggledad. Thanks for your quick response. |
It looks like you switched back to 3.5.3 so I can't see anything about the 3.6.4 issue.
|
1 Attachment(s)
Not sure if this can help. I'm adding a screenshot, in addition I am sending a message to your account with a file from the source page.
Thanks for coming to this. |
All times are GMT -6. The time now is 10:06 PM. |
Powered by vBulletin® Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.