Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Please use Prefix mode instead of Postfix. Postfix mode is known to be creating problems from time to time.

    I’m afraid it’s not anything related to xLanguage. xLanguage line 224 is a SetCookie call, but because the error (and more importantly error message) is thrown earlier, any HTTP Header related function would then be fatal because it’s too late.

    The particular line 53 in wp-project is about unserialize an get_option call, but AFAIK get_option already does unsearialize, unless you are doing searialization in the wp-project itself, or else it should be a bug.

    I noticed that the code of this exact line is different from the v1.2.3 (current marked stable version) and the trunk version, I bet it has been fixed in the un-released trunk version?

    And that indeeded is a bug which I didn’t notice.

    It’s now fixed and should unblock the deployment problem.

    Thank you for reporting the bug.

    It’s rather abnormal to have $options[‘language’] undefined, and no, 0 language should cause an empty array, not undefined one.

    It should be initialized to an empty array when the plugin is activated once, and the code all over the places assume that it’s defined, not just view/admin/*. I would suggest you to reset the configuration (in the options tab) if the problem persist.

    Once again, thanks.

Viewing 4 replies - 1 through 4 (of 4 total)