Storing Large Keys in mbfs_keys

Support MB Frontend Submission Storing Large Keys in mbfs_keys

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #47784
    Craig McKeeCraig McKee
    Participant

    Is there an alternative method to store this data efficiently, such as breaking it into smaller chunks or using a different storage approach? CAn I remove the mbfs_keys key and replacing it with a new key or will it impact any existing functionality of the plugin.

    #47785
    Craig McKeeCraig McKee
    Participant

    Essentially we are encountering a WordPress database error: "Got a packet bigger than 'max_allowed_packet'" due to large data stored in the wp_options table under the meta key "mbfs_keys". So, can we safely rename or create a new key for mbfs_keys without affecting the functionality of the Meta Box plugin? If not, is there an alternative way to handle large data storage efficiently?

    #47794
    PeterPeter
    Moderator

    Hello Craig,

    As replied in the ticket system. You can safely delete the key if it has too many characters to be saved in the database.

    We store keys of frontend form configs into database to be able to retrieve its settings later.
    This key can be safely deleted regularly as it's used for temporary only.
Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.