Fatal error when saving changes to style

[Frank Woolf]

I can create a new child style of an existing style but then when I go to "Edit all style options I just get an error message even if I made no changes at all.

When I save I get:

Warning: implode() [function.implode]: Bad arguments. in /admincp/css.php on line 103
Then a box titled "Rebuild Style Information" and in the box, the following message: Updating Style Information for '' and child styles...
...
Fatal error: Invalid styleid specified in /includes/adminfunctions_template.php on line 327

Can anyone please advise what to do.

[Marco van Herwaarden]

To troubleshoot this, please remove any hacks and disable your plugins, then see if you still have this problem.
Note: To temporarily disable the plugin system, edit config.php and add this line right under <?php

define('DISABLE_HOOKS', true);

If so, reupload all the original vB non-image files (except install.php). Make sure you upload these in ASCII format and overwrite the ones on the server.

[3towers]

We got the exact same error in two different forums. The first one we updated recently to vb3.6.5 from 3.5.4 and the second one is a fresh install.
We installed directly from the tarball on our server.

[Steve Machol]

Strange. I don't see any way to get that error with a fresh install and no modifications. Are you sure about this?

[3towers]

The only thing we installed so far was the vbshout shoutbox and a new style. No hacks to vb core files. The error occurs with disabled plugin system too.

[Steve Machol]

That's not that same as a 'fresh' install.

Add-ons make changes to the database and templates, and also install files in the includes/xml directory that can still execute even when plugins are disabled.

[3towers]

That's right indeed! The style options were not so important to me to uninstall the plugins again. But I will try to uninstall it later just to make clear if its a vb or a mod problem!

EDIT:

Just uninstalled all plugins/products, removed all non vb XMLs, disabled the plugin system - error still there!

[Marco van Herwaarden]

Do you have mod_security or Suhosin/Hardened PHP installed on your server?

[3towers]

Ahh... indeed! We are running PHP-5.2.1 with Suhosin patch and extension. Any incompatible options in there I should disable?

EDIT:
That it was! I changed request.max_vars and post.max_vars to a higher value. That did the trick. Thank you for the tip!

[Frank Woolf]

Can somebody please help me understand the last two posts? Maybe tell me exactly what I should ask the hosting company to do.


I just tried on my development site. I even deleted all the existing styles except legacy. Then I created a new child style, checked it and got the same error. What I found is that when a child style is saved it loses about 20% of the data in the CSS part of the style.

[Marco van Herwaarden]

The following suhosin settings can cause problems if set or if set too low:

suhosin.cookie.encrypt Off
suhosin.request.max_vars
suhosin.post.max_vars

[Frank Woolf]

Thanks.

Can you say what is too low? I know my hosting company will make the minimum change that may not solve the problem so if possible I need to be specific on what to tell them.

[3towers]

The default value is 200 and I have set it to 500.

[Steve Machol]

This is generally what I recommend for those settings:

php_value suhosin.request.max_vars 2048
php_value suhosin.post.max_vars 2048

[jw00dy]

Thanks, this was very helpful!