Fatal error on saving a post (CPT) via admin

This support ticket is created hace 6 años, 11 meses. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Hoy no hay técnicos de soporte disponibles en el foro Juego de herramientas. Siéntase libre de enviar sus tiques y les daremos trámite tan pronto como estemos disponibles en línea. Gracias por su comprensión.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	-	14:00 – 20:00	14:00 – 20:00	14:00 – 20:00	14:00 – 20:00	14:00 – 20:00
-	-	-	-	-	-	-

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

Etiquetado: Types plugin

Este tema contiene 1 respuesta, tiene 2 mensajes.

Última actualización por Beda hace 6 años, 11 meses.

Asistido por: Beda.

Autor

Mensajes

diciembre 9, 2017 at 8:53 am #597306

Valeriia

Hi,

I've been having this error for a while, just got time to look into it.

I have a post type called Word, and every time I save it via admin it causes a fatal error (plus increased load on my server as a consequence).

In the WP debug.log I see this:

PHP Fatal error: Call to a member function get_language_for_element() on null in /home/c/.../.../public_html/wp-content/plugins/types/vendor/toolset/types/embedded/includes/wpml.php on line 521.

Please advise.

Thanks.

diciembre 9, 2017 at 10:53 am #597332

Beda

I cannot see that error.
I just reported another error, that happens when you update a CPT in Toolset > Post Types > your_post_type > Edit > Edit Slug > Update.
The error there is:

( ! ) Notice: wpdb::prepare was called incorrectly. The query does not contain the correct number of placeholders (0) for the number of arguments passed (1).

So, the fatal cannot be replicated, also because if it would be a replicable BUG we should have more reports, since Fatal Errors end up in blank pages, not like the notice above, which will not break anything visually.

Can you elaborate how I can replicate this issue, or show me this on a copy of a site where (if possible) Toolset and a native WordPress Theme are used?

I enabled a private reply already.