Replacement string becomes question mark after plugin update

Viewing 1 replies (of 1 total)
  • Plugin Author Lee Willis

    (@leewillis77)

    11 years, 6 months ago

    Hi,

    As you noted the issue is that current versions of the plugin don’t create the table used to store the translations as UTF8.

    That in itself is a fairly trivial change – and I have a local version that does his. However it needs more work tifying up and testing, particularly on the upgrade process for people who are moving from a non-UTF8 table to UTF8 table before I’m happy to push this out as an update.

    Unfortunately I’m pretty busy right now, so can’t say when that’ll be.

Viewing 1 replies (of 1 total)

The topic ‘Replacement string becomes question mark after plugin update’ is closed to new replies.