Language specification breaks rules integration

Created on 6 January 2012, about 13 years ago
Updated 4 February 2025, 24 days ago

When a radioactivity field is initialized in a single language environment, it gets the language "und" in the database.

However, if the radioactivity field is intended to be modified with a rule, the rule assumes a language, in my case "en". This results in a duplicated row in views, but with the "und" energy value used exclusively.

To fix this, I changed a single variable in radioactivity.module in the _radioactivity_update_energy function. I changed 'language' => $language to 'language' => 'und'.

Seeing as how it's numeric, I don't see why it would need to be translatable since translated nodes have a separate set of fields.

πŸ› Bug report
Status

Closed: outdated

Version

2.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States neomenlo

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024