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.