• Hello,

    The value for the post_notif_shortcode_atts_set_names option in the wp_options table is extremely large (over 40 MiB) and is causing problems with backup processes that attempt to mysqldump the websites database. (Got packet bigger than ‘max_allowed_packet’ bytes.)

    I see the value is read/updated every time the form is rendered by the function render_subscriber_form(), however shouldn’t it be overwriting the values stored and not storing a new attribute set each time?

    What is the best way to fix this issue and clean up this value?

Viewing 1 replies (of 1 total)
  • Plugin Author Devon Ostendorf

    (@devonostendorf)

    Hi 2gen,

    Sorry to hear you’re having problems with your MySQL backups, due to large table volume, as a result of data Post Notif is generating. This is the first I’ve heard of this happening, which makes me think that not many people are using the shortcode functionality. ??

    As you may have seen from my pinned post, I have been away from WordPress for a month and a half and expect to remain so until the end of the year. So I am not in a position to attempt to re-create this issue in order to debug it. If I remember correctly, the code stores a new set of attributes each time you specify a unique (system-wide) ID in your shortcode call. Which makes me think you use shortcodes a lot AND you specify a unique ID each time?

    I think one possible solution would be to determine how many unique sets of widget configuration you have/need. Then assign them unique IDs. And then go through your shortcodes and change them to use one of the new IDs. I think that would overwrite the existing entries (if any) and prevent further proliferation, as long as you continued to use a small set of IDs.

    Of course, I may be off on my memory of how that code works…

    Sorry about the inconvenience this has caused you,
    Devon

Viewing 1 replies (of 1 total)
  • The topic ‘post_notif_shortcode_atts_set_names size’ is closed to new replies.