You know what happens, in ATA 3.6.4, all the header is left out.

adrian - All indications are that you have the suhosin issue. looking at the generated source you sent me, everywhere a <?php include('bfa://xxxxxxx') ?> (where xxxxx= some variable) the processing is bypassed.

This leads me to believe your site must prevent the code from running, but does not give you a warning or an error, just skips over it. That or any warning messages are not going to the screen, then are going to an error log somewhere.

You need to contact your host and ask them how to whitelist something to suhosin

FYI

I had this problem and went back to 3.53 rather than try to fix. Just upgraded to Wordpress 3.1, activated 3.6.4 again and the problem is no longer. 3.6.4 is now finding the database. I use Bluehost. Yippee!

Okay juggledad, I went to open a ticket with my web hosting account. This was the response I received.

-
We apologize for any confusion earlier. Suhosin is not installed on our shared servers, no whitelisting should be needed.
-

This is Hostgator.

bushtool, thanks for your comment, I was afraid to upgrade my WordPress, because it could break ATA 3.5.3

In my case, when I upgrade WordPress, nothing changed, ATA 3.6.4 keeps the white screen.

Then I continue with my last comment on this, the header does not print.

Adrian - see the PM to you

Hello everybody,

I'm completly confused because my english isn't so perfect. I'm using Ver. 3.5.3 with WP 3.1 which works fine so far. All 3.6 versions are displaying a white screen. My hoster is using PHP 5.2.13. These are the facts so far.

I tried the suggestions with the Suhosin-issues. Every try ran in an 500 Internal Server error. I asked my hoster (Speicherzentrum.de) if Suhosin is installed and his answer is:

"das Problem liegt daran, daß das Script 256M Speicher belegen will, was ich aber nicht freigeben kann." The Problem is the script wants to use 256M of memory what I can't allow.

My conclusion: With this hoster I never will be able to use Atahualpa 3.6.x and above?

Greetings
Chris

Okay, I have to explain how I solved my problem with ATA-3.6.x, and the white screen.

I add part of an email that I send to juggledad;

Anyone reading this should note that I have no experience in this, as I mentioned above.

According to me;

suhosin causes the white screen, but not always, some of us do not have that application installed.

First, check with your web host if you have it, then use the proposal for suhosin. Otherwise, look in your php.ini because something is blocking the work of ATAHUALPA.

If you activate ATA-3.6.x and got the white screen, ask for help from your web host, they may find the problem and solving it.

Okay, I come with more information on the white screen and ATA-6.4.x

If you've read this thread, you already know some of us do not use suhosin.

I want to add more information of how I solved the white screen.

I have my website in a sub-folder. At the root of that folder I create a php.ini, I think instead of creating a php.ini in the sub-folder, you could modify your original php.ini. However, I just want to give access to ATAHUALPA.

Here the contents of php.ini

~ Note; absolute path to basedir, not the relative.

Here you do two things, one is safe_mode = On, and two, open_basedir. Remember this will only affect the folder where you allow the safe mode.

I want to add;

1. If I remove the php.ini from my sub-folder, the white screen comes back.

2. When I add the php.ini the response time of my website is accelerating. Possibly because ATAHUALPA can work without restriction.

3. safe_mode has a Warning on the php.net page
This feature has been DEPRECATED as of PHP 5.3.0. Relying on this feature is highly discouraged.

And that is why I am concerned, rather, concerned about two things.

I already using php 5.3, and is not a good idea to have to add permission to ATAHUALPA, I know you guys already know that something has to change.

So, I'm over here waiting.

I can confirm this. I am having the same problems and same errors and my host gives only 128M memory.

Is this something that should be and will be addressed in future versions of atahualpa or is it time to look for something else either host or atahualpa replacement?

3.6.4
WP 3.1
Blank screen appears only when I imported and tried to use the ata-round.txt file. Deleting and installing the theme again removed the problem. As I want to use the ata-round.txt presets I searched the forum and found the suhosin effect posts. Being not technical I am not able to locate the php.ini file on my server. Where would I find this?
Thanks
David

You may not have one in which case you can just create on on your own or download the one attached to the first post.

Hello everybody.

I've used WP+Atahualpa for some time on my private web site and always was very happy with this combination.
Updating from 3.5.x to 3.6.x I experienced the blank-page-suhosin-issue, too. I tried to fix this by adding bfa:// to
"suhosin.executor.include.whitelist" in .htaccess. But as I just learned (after contacting my
shared webhoster's support (hosteurope.de)) they are not willing to allow changes to any suhosin variable :(

For now I'm back on 3.5.3 and all looks fine. But in the medium term, I fear that this suhosin "problem" would
force me to switch over to another WP theme (at the latest when any future WP will become incompatible
with ata 3.5.3).

Is there any chance, that atahualpa >= 3.6.5 again will be able to work without a change to
"suhosin.executor.include.whitelist"?


Best regards
Frank

Some possibilities are being looked at. There are currently no time frames on this though.

Hi Larry, thanks for the information ... no time frame, but one can see a small, faint light at the end of the tunnel :)


CU
Frank

I have suhosin and using the various syntaxes on this forum did not seem to do the trick. Will uninstall this theme and wait for a more stable version.

Thanks

Just for the record, I have tried both the ini.php and .htaccess fixes on Dreamhost and had no success with 3.6.1 nor 3.6.4. I will await a true fix with bated breath.

This is something outside the control of the theme, You need to contact your host and ask them how to whitelist something in suhosin

Hi,
my hosts provider doesn't supported suhosin. I must discard ata or this will resolved in new release ?
My question (it pursued me ), why ata 364 worked fine width php 5.2 but doesn't width php 5.3 ?

what kind of problem do you have?

I opened a new thread (http://forum.bytesforall.com/showthread.php?t=13223).
The solution provided a new entry in .htaccess like : php_value suhosin.executor.include.whitelist bfa://

This line crashed my site ... suhosin is not supported by my provider hosts.

Now, I don't understand why width php 5.2 is all right instead in php 5.3 I get the warnings reported in http://forum.bytesforall.com/showthread.php?t=13223 .
Is the php version the problem ?

Lets work on it in the other thread

The method listed in the OP worked for me as well. Actually, it didn't work in the beginning. I had to add one more ingredient to the mix, ie., "suPHP_ConfigPath /path/to/php.ini" in my .htaccess file to specify where the php.ini file is since my host hadn't configured a specific path for it (or maybe configured one that i dont know about).
You might want to add it in the OP.

I tried to upgrade from 3.5.3 to 3.6.4 (under WP 3.01) last night, and suffered the same blank page issue. I have reverted to 3.5.3 while I work my way through the solutions suggested in this thread.

One question: If I find a combination of settings that fixes the suhosin issue, will I be able to see the 3.6.4 preview in the Manage Themes page before I activate 3.6.4?

Thanks...

JGB

Yes, once you have the Suhosin issue resolved, you should be able to see the preview.

Suggestion, install 3.6.4 in a separate folder called 'atahualpa364' then you can have both 353 and 364 in the theme picker and activate one or the other by picking it in the theme switcher.

I needed to edit etc/php5/apache2/php.ini
and the line: suhosin.executor.include.whitelist = bfa://

AND then restarting apache (was not mentioned here in the topic, for beginners this might not be obvious that they have to restart apache!!!!) with rcapache2 restart on opensuse.

The location of php.ini and command to restart apache is of course depending on the installed linux.

everything else would not work. So I think this patch will only work for people administering their own root server.

I was forced to upgrade to 3.6.x because 3.5.3 menubar broke down in Firefox 4, and IE 9. For all sublists with more than one item they just showed white space instead of the title. Else I would not have updated. Took me well over an hour overall with applying all the patches (damn, you should offer a 3.6.4.1 for download with all patches applied as long as 3.6.5 is not yet available - it's been several month now of bugfixes and no new version).

OK, I got help from the host server company and I had put the path incorrectly in the .htaccess file.

They changed it to

suPHP_ConfigPath /home/mypassword/public_html/nameofthefolder

and it is showing up fine.:)

Worked great for me. Only had to put the ini file in.
Thanks

Worked like a charm ( Uploaded the php.ini into the wordpress directory )

:)

Will we have to change anything when we upgrade the theme later?

Unknown as some of this appears to depend on how Suhosin is configured and the verson of PHP.

Hi everybody,

I have also problems when upgrading (from 3.4.9) to 3.6.4. I made a sub-domain to test and show you the result.

WP 3.1
Ata 3.6.4
PHP Version 5.3.2-1ubuntu4.7
This server is protected with the Suhosin Patch 0.9.9.1
http://www.acdenderland.be/phpinfo.php

This is the result: http://test.acdenderland.be/PHP%205.3.gif

Wbr
Jan

Hi everybody,

This a reply on my own message above.

Today I changed PHP version from 5.3 to 5.2. In fact, it is still 5.3 but it act as a PHP 5.2. The upgrade is working now. See http://test.acdenderland.be/php%205.2.jpg. My hosting is Priorweb.be. I can change PHP-version in the control panel.

Maybe this info was helpful.

Wbr
Jan

Thanks to extremely good notes, downloaded new version - did all the necessary bug fixes as instructed in forum, followed instructions on the php.ini and .htaccess - FTP new file 364 to host, one call to Hostgator and was online in no time at all. BTW was on version 3.2.

I have been following this thread because I also now have the blank page issue.

However please note the following:

I upgraded Atahaulpa from 3.4.x to 3.6.4 about a month ago - NO PROBLEMS.
(I was on WP 3.1)

Two days ago I upgraded WP to 3.1.1 - Now I have the blank screen problem.
(so I installed Atahaulpa 3.5.3 to get over it).

So, at least in my case - it seems to be an incompatability between Atah 3.6.4 and WP 3.1.1 - nothing to do with my web host.

Does this help the thread?

That is very curious None of my sites that are on Atahualpa 3.6.4 and WP 3.1.1 are having any problems.

Sorry, the information I gave you was slightly wrong.

3.6.4 was working fine with WP 3.0.

2 days ago I logged on to my web host and received a message to upgrade WP to 3.1 (I did this by responding to the webhost message - not within WP).

After this I logged on to the WP dashboard and realized that 3.1 had already been superseded by 3.1.1.
I upgraded again, this time automatically through WP.

I appreciate that the above actions were stupid, because I did not test my site after the first upgrade (WP 3.0 to 3.1) so I'm not sure if 3.1 or 3.1.1 has caused my blank screen problem.

Also another thought. Is it possible that if my webhost has changed something, it would only show up on later versions of WP ie 3.1 onwards?

There are many variables. Your host may have made some changes. WP 3.1 had some important security updates. Etc. At this point you can either try the Suhosin "fixes" or upload Atahualpa 3.5.3 into it's own folder and switch to that to see if that takes care of the blank page. For full documentation on that process check this thread which also applies to uploading an older version of Atahualpa. In other words don't delete or overwrite your current install of the theme.

At my hosting provider, the php.ini file is not accessible to customers such as myself. The provider added the directive

to php.ini at my request. This fixed the blank page issue.

The provider also told me that the Apache logs show this error:

and said that the error is triggered by line 235 in the file /home/myuserid/public_html/wp-content/themes/atahualpa364/css.php. That's in this section of the file (line numbers added for clarity).

He suggested that the statement should be changed to use a valid filename such as bfa-logoarea_style.

Hope this helps someone down the road.

JGB

That was my experience as well. It was only when I upgraded to WP3.1 (and now 3.1.1) that I got the blank page thing happening.
I'm back running 3.5.3 at the moment as my host has yet to be convinced why he should have to change his server settings just to accommodate my theme..!

I've spoken to my webhost. They said they disabled suhosin. I tried 3.6.4 but still the problem.

I like Atahaulpa and was really getting used to configuring it, however it seems a bit worrying that there does not appear to be a definitive fix for this problem on the horizon. I don't really want to change to another theme - because at this stage I wouldn't know which to choose.

One thing for sure. I want a theme that stays WP compatible and does not require different host configuration settings.

Two questions spring to mind.
1. What are the implications of staying with 3.5.3
2. If this was a 'premium' theme, would the situation be any different.