Filename replacement incompatible with serialized data

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

  • FYI – their current unreleased version (in GitHub?) has this fix in it. We’ve tried it and it did the job right. We aren’t moving forward until they publish the version, though, because we don’t know what else is incomplete at this time.

    Plugin Support Gerard Blanco

    (@sixaxis)

    Hi @clemorphy,

    What @chetcromer says is correct. We are soon going to release a fix for that. Stay tuned to your updates ??

    Cheers!

    Thread Starter clemorphy

    (@clemorphy)

    Thanx for your quick answer.

    I don’t know when the fix will be published, but in the meantime, people still use the current version and might face this really annoying problem. That’s why I suggested to add a warning or disable the rename option until it’s fixed.

    Plugin Support Gerard Blanco

    (@sixaxis)

    Good morning @clemorphy,

    Adding such warning or disabling the renaming option would also require an update ?? Like I said, we will release it (with the actual fix) soon, but unfortunately I can’t tell you when exactly though.

    Cheers!

    Thread Starter clemorphy

    (@clemorphy)

    Hi @sixaxis

    If I’m right, this has been fixed in v 3.3.8 ?

    Plugin Support Gerard Blanco

    (@sixaxis)

    Hi @clemorphy!

    That’s right, it’s been already fixed ??

    Cheers!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Filename replacement incompatible with serialized data’ is closed to new replies.