hey

i'm getting lots of errors whenever i use tokens.

    * warning: Illegal offset type in isset or empty in /locale/locale.module on line 372.
    * warning: mysqli_real_escape_string() expects parameter 2 to be string, array given in /drupal-6.19/includes/database.mysqli.inc on line 323.
    * warning: Illegal offset type in /locale/locale.module on line 379.
    * warning: Illegal offset type in /locale/locale.module on line 398.
    * warning: Illegal offset type in /locale/locale.module on line 398.

seems related to translation/multilingual modules.

CommentFileSizeAuthor
#11 errors.jpg100.13 KBenomertens

Comments

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

What internationalization/translation modules do you have enabled? What version of Drupal?

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Title: token errors » token errors when using internationalization
lpalgarvio’s picture

lpalgarvio commented

listing the enabled i18n, URL, meta tags and related modules

Drupal 6.19
Internationalization 6.x-1.7
Internationalization Views 6.x-2.0
Language assignment 6.x-1.2
Language icons 6.x-2.0
Language Switcher Dropdown 6.x-1.2
Lightbox2 6.x-1.11
Localization client 6.x-1.8
Localization update 6.x-1.0-alpha2
Nodewords 6.x-1.12-beta9
Page Title 6.x-2.x-dev (2010-Ago-26)
Pathologic 6.x-3.2
Token 6.x-1.15
Translation helpers 6.x-1.0
Translation Management 6.x-1.5
Translation Overview 6.x-2.4
Translation table 6.x-1.2
Transliteration 6.x-3.0

i haven't successfully yet isolated the problem, but after disabling a bunch of nodewords modules, i'm not getting the issue anymore.
at the moment i have these enabled:
Nodewords, Administration interface for Nodewords, User interface for Nodewords, Basic metatags.
Pagetitle is enabled
Tokens is enabled, but not connected into Nodewords (disabled in the configuration)

will try enabling module-by-module later, till i find the exact culprits.

lpalgarvio’s picture

lpalgarvio commented

note, i've had issues before with Translation Management 6.x-1.5

i had to change the function call in a file to stop the site from crashing. issue submitted bellow.
http://drupal.org/node/946880

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Status: Active » Postponed (maintainer needs more info)

@LPCA looking at #946880: Nodewords it seems this may have been an issue with Translation Management after all. Please confirm the issue no longer exists. Thank you.

lpalgarvio’s picture

lpalgarvio commented
Version: 6.x-1.12-beta9 » 6.x-1.x-dev

i've done extensive testing with nodewords, nodewords contrib modules and locale/i18n contrib modules

turns out Nodewords 1.12-beta9 is behaving fine, it's causing no issues.
the tokens integrations is also fine.
and the tokens submodule is again fine.
when using page_title (Page Title) and nodewords_pagetitle (Nodewords Page Title (Views, Panels, Non-nodes)) submodule, yet again, fine.

the problem arrises when you enable nodewords_nodetype v1.x-dev / 1.7 (Nodewords - node type meta tags / Meta tags Node Type) against Nodewords 1.12-beta9 / 1.x-dev, which then causes the mentioned problems with locale/translation_management
it works fine with Nodewords 1.11.

also, there is currently an incompatibility with nodewords_bypath v1.x-dev / 1.0 (Meta Tags by Path) against Nodewords 1.12-beta9 / 1.x-dev, which causes critical PHP errors on the config page of nodewords_bypath.
it also works fine with Nodewords 1.11.

so the conclusion is that Nodewords runs fine with locale modules as of 1.12-beta9.
will test 1.x-dev soon.

lpalgarvio’s picture

lpalgarvio commented

as a side note, from what i understand,:
- the Tokens submodule (Tokens for meta tags) adds new metatags, starting with "metatags_", which perform specific functionalities
- the Token integration, located as "Enable the integration with token.module (The integration with token.module allows to use tokens in meta tags content.)", under "Third party modules integration", adds the Patterns info in Nodewords edit forms BUT does NOT add the Token integration itself

Token integration itself is always turned on if Token module is present.
i tested the token [node_path] in Canonical URL, with and without it checked, and it always worked.

i think that documentation should be changed to reflect this and if the Token checkbox is meant to turn on integration with Token, then it should ;)

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

@LPCA: thanks for doing all the research, it's appreciated.

I'll add a separate issue for the Token confusion.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

FYI the other issue I opened for the Token bug / clarification: #948094: Token integration ignores checkbox?

enomertens’s picture

enomertens commented

Hi all,

I'm having same kind of errors, first i had it on one website and it showed up on another website we're developing after adding:

Translation helpers 6.x-1.0
Translation Management 6.x-1.5
Translation Overview 6.x-2.4
Translation table 6.x-1.2
Transliteration 6.x-3.0

(updated all mods to current releases) - after installing the modules the same errors showing up on this website, ... so or another module is messing up one of those modules. Or we have an issue with one of the translation management modules.

I'm going to dissable them one by one to point a finger to the right module(s) and will let you know or our conclusion is the same about the nodewords.

On both sites we're using nodewords, metatags, etc. (regular modules)

Kind regards,

Eno Mertens

enomertens’s picture

enomertens commented
StatusFileSize
new errors.jpg100.13 KB

FIXED after disabeling translation management module, it gives for e.g. the erros you see in the attachement ;)

Kind regards

Eno

lpalgarvio’s picture

lpalgarvio commented
Status: Postponed (maintainer needs more info) » Closed (fixed)