Moderator
t-p
(@t-p)
What theme are you using?
Tara, Thank you for your reply. Do note it’s a fresh installation. But for the record, I was using 2015, but also tried 2013. No changes.
Moderator
t-p
(@t-p)
try MANUAL re-uploading all files and folders. Download a fresh copy of the WordPress .zip file to your computer, unzip it, and use that to copy up all files and folders EXCEPT the wp-config.php file. You may need to delete the old copies of files & folder on your server before uploading the new ones. Read the Manual Update directions first.
Tara,
With all humble respect, I think you twice did not read what I wrote, but again, I did a whole new installation on a new domain, thus a new root folder, with a new database, with a freshly downloaded WordPress. Thus no plugins, themes, any files or changes to the default wordpress. And I manually did that all by myself. Folder permissions are alright.
But still not working.
Apparently this is probably server related, as I have multiple WordPress installations on that VPS, capable of handling them, and all of them perform this issue.
Each of those installation has it’s own .htaccess file, and there is non in the root (/public_html/) overruling, so I’m pretty sure it’s server related..
But what could cause it?
Hey do you run suhosin? I just had this issue as well after 4.1.1 upgrades
if yes which version?
phpinfo() would let you know if you don’t off hand. and if yes, check out this thread i just closed:
https://wordpress.org/support/topic/wp-411-suhosin-adding-menu-items-fails?replies=3
Hi!
I do run Suhosin, but not on purpose. It came with my Ubuntu/Admin panel installation, I guess. Anyway, I run the same version as you do: Suhosin Extension 0.9.37-dev.
I checked the post you linked and honestly.. I don’t understand what you write in the second post, thus first reply on yourself. The third one is clear enough.
I’ve played with Suhosin values in my .htaccess and php.ini (as recommended in a few threads), but that didn’t seemed to change anything. If I’m using the correct syntaxes atleast..
Hey
basically the second post is just saying that if you’re on 0.9.37, there is no way to fix it
so the options i would explore are:
A. get host to upgrade suhosin
or
B. disable suhosin with a php/htaccess override for long enough to edit your menu
–> you should be able to switch suhosin to simulation mode via htaccess as long as the host doesn’t prevent overrides on this. here’s the value for htaccess:
php_flag suhosin.simulation On
i grabbed that info from here
I’m running a VPS, which means I’m the one running the show on the server. – If that is what you mean with ‘host’.
However, Sentora (‘successor’ of zPanel), my admin panel (Not cPanel/DirectAdmin) uses the suhosin version written above. It will be upgraded to a newer version with a new release, but I don’t expect that within a few weeks, honestly..
I wrote the simulation line to my htaccess, even rebooted the server, but still not able to add menu items.
Update: After refreshing phpinfo, it seems suhosin is still on. I’m trying something else atm. brb. 🙂
well the good news is, compiling it by hand is easy
yes that is what i meant by host
SSH access?
if yes, ssh in and:
# cd /usr/local/src
# wget https://download.suhosin.org/suhosin-0.9.37.1.tar.gz
# tar zxvf suhosin-0.9.37.1.tar.gz
# cd suhosin-0.9.37.1
# phpize
# ./configure
# make
# make install
# apachectl restart {or whatever your syntax is for restarting apache}
# php -v
–> you should see the suhosin version as upgraded now
if this is a non option or makes you nervous, you can disable suhosin in your default php.ini (grep it for suhosin, you should find an extension line). if suhosin is not loaded via the php.ini, it’s likely got a file in php.d’s directory which you could move to any other folder, restart apache and it should be ok
thoughts?
I’m gonna take a snapshot of the current setup and then run your code. Such thing does makes me nervous, but a snapshot should be a correct safe point 🙂
I tried the second thing you suggested, extensible written here: http://geeksterminal.com/how-to-disable-suhosin-for-particualr-domain/626/
But that didn’t work out..
YES! That did it mate!
It feels there are no side effects, but perhaps you can tell me if there are any side effects of having this update, which have to be known?
At this point: Thanks incredible!
Btw: is there any explanation why suhosin was messing up the menu items? And.. The menu items only, in fact. Everything else worked. Seems so unlogical.
Honestly I dont know what/if for side affects there will be yet, but it is just a bugfix release so the impact should be small
The changelog just says “relaxed array index blacklist” so i don’t really know why it only affected the menu item array
2014-12-12 – 0.9.37.1
– Changed version string to 0.9.37.1 (without -dev)
– Relaxed array index blacklist (removed ‘-‘) due to wordpress incompatibility
full changelog
I’m stoked you’re back in business tho! I was fighting this one too today and damn it was frustrating.
It feels good when you win though, right?
Everything seems to be still working after a night of sleep, so guess nothing to worry. But.. with a minor patch as this, a bug fix as you say, no hassle at all, gladly.
Winning after such battle, stressing over 2 days of trying everything does indeed feels great. Thanks mate! 🙂
bernebe01, I have lurked the WP forums for 5+ years… not once did I register to reply to any helpful thread but had to for this. Your solution on updating suhosin fixed all the issues I was having with WP on 3 of the servers I help manage. I was literally banging my head on the wall for days until I found this thread. Just wanted to say thanks – much appreciated 😀
