On MySQL 8 on DIgitalOcean

  • Resolved timwendisch

    (@timwendisch)


    4 years, 7 months ago

    If I use your plugin on my “old DB” (MySQL 5) I see in the session overview the correct writings of session content… When I look into the blob in the DB I see content like

    72f48c031d81fd8dabbafa029e57743c|a:3:{s:23:"Login_Server_Session_id";s:32:"d93748b1bd322c325275a158b038b1d9";s:9:"loginDone";b:1;s:11:"credentials";a:2:{s:8:"username";s:35:"[email protected]";}}
    This is Correct!

    After our switch to MySQL 8 on Digital Ocean I see a lot of unicode specialchars
    This is not!

    • This topic was modified 4 years, 7 months ago by timwendisch.
    • This topic was modified 4 years, 7 months ago by timwendisch.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Daniel Bachhuber

    (@danielbachhuber)

    Hey @timwendisch,

    Can you share an example of the session data you see on Digital Ocean?

    Also, is your session-related functionality still working on Digital Ocean?

    WP Native PHP Sessions calls maybe_serialize() prior to inserting the data in the database. All MySQL knows about is the end result of serialization, a plain text string, so I’m not sure why the behavior would change between MySQL 5 and MySQL 8.

    My hunch would be there’s something else that’s different about your Digital Ocean PHP configuration that is causing the discrepancy. We only offer limited support for non-Pantheon sites, though.

    Thread Starter timwendisch

    (@timwendisch)

    It seams that these chars are unicode… I made an image , cause I cannot “copy” them

    I send you a picture to your github-Email

    • This reply was modified 4 years, 7 months ago by timwendisch.
    • This reply was modified 4 years, 7 months ago by timwendisch.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘On MySQL 8 on DIgitalOcean’ is closed to new replies.