Error en WordPress 3.1 RC1

[fliberty]

Quería reportar, que utilizando WP 3.1 RC1, al momento de insertar un campo personalizado, carga la página y sale en la parte superior "campo personalizado actualizado", pero con los campos en blanco como si se fuera a crear nueva entrada y tengo que volver a edición de entradas y abrir el borrador guardado para poder continuar con la edíción de la misma y poder publicar correctamente; y si no hay un borrador actualizado tengo que volver a editar las partes que no se guardaron.

[nacin]

Google Translate:

Wanted to report that using WP 3.1 RC1, when inserting a custom field, loading the page and comes out on top "date custom field", but with blank fields as if they were to create new post and I have to go back to edit entries and open the saved draft to continue with editing and to publish it properly, and if there is an updated draft I have to re-edit the parts that were not saved.

---

Not sure what the bug is here. Translate didn't help too much.

fliberty: Any plugins? Can you provide an English explanation?

[solarissmoke]

Don't know if it helps much, but the correct translation of "campo personalizado actualizado" (taken from the .PO file) is "custom field updated".

I can't find a way to even get that message to display (custom field is updated using ajax)!

[ocean90]

Replying to solarissmoke:

I can't find a way to even get that message to display (custom field is updated using ajax)!

Custom field updated. will be shown if you add a custom field without Javascript.

Custom field deleted. will be shown if you delete a custom field without Javascript.

Post updated. will be shown if you update a custom field without Javascript.

[edwardw]

Please re-open this bug with detailed information if this is still present with latest trunk.