WordPress 2.8 settings – general save button not loading

Warning before uploading or chaning anything on any .php file! Backup your blog and database.

One of the many bugs of WordPress 2.8 has been resolved, or better say a workaround has been found. I have already written about this on the forum.

What is affected:

• New installations of localised WordPress 2.8 – Polish version is the only one tested by me
• Upgrade from 2.7.x to 2.8 of the English WordPress 2.8 version

What is the problem/bug:

• On the Upgrade of the English version, having activated the “similar posts” plugin, you see the Settings -> General screen (/wp-admin/options-general.php) without the Save Changes button and without the second half of the settings to change – see the image attached.
• On the installation from scratch of the Polish localized version, the previous problem is appearing immediately after clean installation of WordPress 2.8

The HTML on this page taken from right-click -> View Page Source:

<th scope="row">Członkostwo</th>
<td> <fieldset><legend class="screen-reader-text"><span>Członkostwo</span></legend><label for="users_can_register">
<input name="users_can_register" type="checkbox" id="users_can_register" value="1"  />
Każdy może się zarejestrować</label>
</fieldset></td>
</tr>
<tr valign="top">
<th scope="row"><label for="default_role">Domyślna rola nowych użytkowników</label></th>
<td>
<select name="default_role" id="default_role">

	<option selected='selected' value='subscriber'>Subskrybent</option>
	<option value='administrator'>Administrator</option>
	<option value='editor'>Redaktor</option>
	<option value='author'>Autor</option>
	<option value='contributor'>Współtwórca</option></select>
</td>
</tr>

<tr>
<th scope="row"><label for="timezone_string">Strefa czasowa</label></th>
<td>

<select id="timezone_string" name="timezone_string">
<br />
<b>Fatal error</b>:  Allowed memory size of 33554432 bytes exhausted (tried to allocate 7680 bytes) in <b>/home2/badjobco/public_html/mysite/wp-includes/functions.php(3233) : runtime-created function(2) : runtime-created function</b> on line <b>1</b><br />

on the php.ini I set this:

max_execution_time = 30     ; Maximum execution time of each script, in seconds
max_input_time = 60	; Maximum amount of time each script may spend parsing request data
memory_limit = 64M      ; Maximum amount of memory a script may consume (32MB)

on the wp-config.php I added this:

On the wordpress.org forum they have told me that:

Given the line number (3233) of functions.php, it appears that the fatal error is occurring with timezone_identifiers_list.

The server was running:

• Apache version 2.2.11 (Unix)
• PHP version 5.2.9
• Kernel version 2.6.28-9.16.intel.BHsmp

Thanks to ronnie the resolution was not to change the memory limit on the php.ini or in the wp-config.php.
The workaround of this was to just disable something:

Here is his post:

Hi,
I was having the same problem with the Polish version!
I don’t know how but it’s working now, I have just changed one true to false.

Go to your public html/you/wp-includes and open with your editor the file functions.php

As you can see from the error, on the line 3233 is closing the function

PHP Code:

function wp_timezone_choice($selectedzone) {
static $mo_loaded = false;


this means that something is wrong with that…

Reading the case they have opened and closed they say to use timezone_support filter

I don’t know what is that, but trying I found out that changing

function wp_timezone_supported() {
if (function_exists(‘date_default_timezone_set’)
&& function_exists(‘timezone_identifiers_list’)
&& function_exists(‘timezone_open’)
&& function_exists(‘timezone_offset_get’)
)
return apply_filters(‘timezone_support’,true);

return apply_filters(‘timezone_support’,false);
}

to

PHP Code:

function wp_timezone_supported() {
if (function_exists('date_default_timezone_set')
&& function_exists('timezone_identifiers_list')
&& function_exists('timezone_open')
&& function_exists('timezone_offset_get')
)
return apply_filters('timezone_support',[B]false[/B]);

return

apply_filters('timezone_support',false);
}


resolves it… I don’t know if temporarily or forever, but I’d suggest you to put it back to true before upgrading to the new release…
cheers

Thanks ronnie…

Do you want to read something more about WordPress vulnerabilities and how to protect? Go here…

Did you find this post useful? Please leave a comment,

Thank You & Best Regards

Do you have a blog? Let’s exchange our links!

Any question? You need our FAST help? Go to our forum and as for FREE!