Fresh install 3.4.2 - custom fields not saving/working! WordPress

Josh Cranwell comments:

No javascript errors?

Christianto comments:

did you found error on your web browser console?
I think the link you gave to me is a server error log

I'm sure its a JavaScript since updating/adding other dom element ("custom field" fields) its an ajax function.
since the custom field "add" button moving up from its location when you click it..

could it be because the html not rendered correctly.
Can you check if the value saved to database, after you add custom field?
(although the custom field not added/appear & the "add" button move up)


============

you can try to do backup your wp-admin folder
and re-upload wp-admin folder from same version of wordpress zip to see if its not file corrupt.

Josh Cranwell comments:

I've just ran a complete fresh install, downloading 3.4.2 straight from wordpress.org and starting an absolute fresh!

See my updated question.

It appears to be ajax related, but im getting nothing in the javascript console - [[LINK href="http://i.imgur.com/TMIl2.png"]]http://i.imgur.com/TMIl2.png[[/LINK]]

It is adding it to the database - but only if I update the page. If I don't update the page, then custom field changes are lost. This is not normal behaviour as you don't have to update the page to make custom fields apply.

======

I am lost :/

Josh Cranwell comments:

Its a bug... [[LINK href="http://wordpress.org/support/topic/custom-fields-in-342"]]http://wordpress.org/support/topic/custom-fields-in-342[[/LINK]]

Christianto comments:

Thanks for let us know this, I got it too :)
the file causes this is wp-includes/js/wp-lists.js (wp-lists.dev.js - development version)

Just to let everyone know, to fix this I simply put new selector,

[id="add' + m.what + 'sub"]
you can download on https://www.dropbox.com/s/lzsnomx0574sss2/wp-lists.js

or if you use wp-lists.dev.js version by adding define('SCRIPT_DEBUG', true); on wp_config.php
on line 81
from:
if ( !e.is('[id="' + s.what + '-add-submit"]') )
return !wpList.add.call( list, e, s );
to:
if ( !e.is('[id="' + s.what + '-add-submit"],[id="add' + s.what + 'sub"]') )
return !wpList.add.call( list, e, s );

As we can see on wordpress [[LINK href="http://core.trac.wordpress.org/changeset?old_path=%2Ftags%2F3.4.1&old=21780&new_path=%2Ftags%2F3.4.2&new=21780#file14"]]code trac here[[/LINK]]

the selector is change from class to id,
so the button to add the metafield not selected since the button id attribute isn't "meta-add-submit" but "addmetasub" ( var s.what in this case "meta" ).

hope its works for you all..

Christianto comments:

[[LINK href="https://www.dropbox.com/s/lzsnomx0574sss2/wp-lists.js"]]This link to download edited wp-lists.js[[/LINK]]

Josh Cranwell comments:

How would I increase this? Can you elaborate please, my understanding of php is not great. Thanks

Dbranes comments:

if you are using php version >= 5.3.9 then this could be relevant.

You have to locate your php.ini on the webserver.

If you can run this

<?php
phpinfo();
?>

then you should be able to find the php.ini location there.

Josh Cranwell comments:

Thanks

I just showed this to my server guy as I don't have access to php.ini and up'ed to 2000 for a test.

No change :/

But i only have 45 registered custom field meta_keys? Which surely is not that much (its more than normal I know)

I worked out that over all I have 129 Posts with with a total of 2079 custom fields.

Is that abnormally high?

Thanks

Dbranes comments:

ok, it was worth the try ;-)

It's a lot but it should be ok.

Many users have experienced restriction problems (mainly with the menu builder) that have been solved by increasing this variable

see fx. this menu problem
http://wpquestions.com/question/showLoggedIn/id/4290


... there are also other php variables that could be checked ;-)

Josh Cranwell comments:

Hmmm... as you can see I've just updated my question above.

I've just ran a complete fresh install, downloading 3.4.2 straight from wordpress.org and starting an absolute fresh!

============

I've just check all my wordpress installs on the server which are in the last few months and they are all on 3.4.1 - the custom fields work absolutely fine.

However, I do have 1 other site on 3.4.2 and exactly the same problem is occuring but I didnt notice as I don't have much need for custom fields on that site.

So that does mean, I have a problem with 3.4.2 on my server - thank god I have not update others as use custom fields a lot on them.

So do you think I need to change server settings, I had a look at that thread but these lots of threads and I'm not sure what I should be looking at?

Thanks

Josh Cranwell comments:

Hmmm... as you can see I've just updated my question above.

I've just ran a complete fresh install, downloading 3.4.2 straight from wordpress.org and starting an absolute fresh!

============

I've just check all my wordpress installs on the server which are in the last few months and they are all on 3.4.1 - the custom fields work absolutely fine.

However, I do have 1 other site on 3.4.2 and exactly the same problem is occuring but I didnt notice as I don't have much need for custom fields on that site.

So that does mean, I have a problem with 3.4.2 on my server - thank god I have not update others as use custom fields a lot on them.

So do you think I need to change server settings, I had a look at that thread but these lots of threads and I'm not sure what I should be looking at?

Thanks

Josh Cranwell comments:

It's a bug... [[LINK href="http://wordpress.org/support/topic/custom-fields-in-342"]]http://wordpress.org/support/topic/custom-fields-in-342[[/LINK]]

Dbranes comments:

ok, interesting ;-)

thanks for sharing this info