Hi
I am using this module together with I18n 7.x 1.5 and I replace the taxonomy's name field, in order ot be able to translate it.

All the names appear blank in views and whenever I edit them they appear blank in the taxonomy terms list. They only appear correcltly in the taxonomy term edit form.

I am getting this error in my log:

Warning: htmlspecialchars() expects parameter 1 to be string, array given in check_plain()

Any ideas?

Comments

elyobo’s picture

Same thing happening for me. Tried upgrading to the dev release, but the same process occurs.

elyobo’s picture

I've had time to look at this a little more and I've noticed that the problem only occurs when the replacement title field is translatable using entity translation; marking the field as not translatable, or disabling the entity translation module entirely makes the problem go away.

Module versions -

  • entity_translation - 7.x-1.x-dev
  • entity - 7.x-1.0-rc2
  • title - 7.x-1.0-alpha2+5-dev

This is the state of the database after a faulty insert; I have two languages, Thai and English, with the default being English. No name gets stored in taxonomy_term_data or under the "und" langauge, but it does get stored in the "en" language. Things seem to work correctly for the description, although that has also been replaced.

mysql> select * from taxonomy_term_data where tid = 13601;
+-------+-----+------+-------------+---------------+--------+----------+-----------+
| tid | vid | name | description | format | weight | language | i18n_tsid |
+-------+-----+------+-------------+---------------+--------+----------+-----------+
| 13601 | 8 | | w00t | filtered_html | 0 | und | 0 |
+-------+-----+------+-------------+---------------+--------+----------+-----------+
1 row in set (0.00 sec)

mysql> select * from field_data_name_field where entity_id = 13601;
+---------------+---------+---------+-----------+-------------+----------+-------+------------------+-------------------+
| entity_type | bundle | deleted | entity_id | revision_id | language | delta | name_field_value | name_field_format |
+---------------+---------+---------+-----------+-------------+----------+-------+------------------+-------------------+
| taxonomy_term | testing | 0 | 13601 | 13601 | en | 0 | w00t | NULL |
| taxonomy_term | testing | 0 | 13601 | 13601 | und | 0 | | NULL |
+---------------+---------+---------+-----------+-------------+----------+-------+------------------+-------------------+
2 rows in set (0.00 sec)

mysql> select * from field_data_description_field where entity_id = 13601;
+---------------+---------+---------+-----------+-------------+----------+-------+-------------------------+---------------------------+--------------------------+
| entity_type | bundle | deleted | entity_id | revision_id | language | delta | description_field_value | description_field_summary | description_field_format |
+---------------+---------+---------+-----------+-------------+----------+-------+-------------------------+---------------------------+--------------------------+
| taxonomy_term | testing | 0 | 13601 | 13601 | en | 0 | w00t | | filtered_html |
| taxonomy_term | testing | 0 | 13601 | 13601 | und | 0 | w00t | NULL | filtered_html |
+---------------+---------+---------+-----------+-------------+----------+-------+-------------------------+---------------------------+--------------------------+
2 rows in set (0.01 sec)

Please let me know if there is any further information I can give to assist in debugging this.

elyobo’s picture

Status: Active » Closed (duplicate)
elyobo’s picture

axe312’s picture

i had the same issue.

in my case, the error happened because the entity translation for taxonomy terms was -not- enabled! so make sure it is enabled!

SandraVdv’s picture

Issue summary: View changes

So what can we do about it? I still have this issue with latest dev release of title and ET 7.x-1.0-beta3... When I replace the name fields, they remain empty if I go to the edit page of a taxonomy term...
Maybe a solution can be described here?

philosurfer’s picture

If you stumble across this issue, Comment #5 is reported as working from a client.