DB error: access_token too long/invalid

  • metricmedia

    (@metricmedia)


    3 weeks, 4 days ago

    I’m seeing this error when accessing the Settings page: WordPress database error: Processing the value for the following field failed: access_token. The supplied value may be too long or contains invalid data.

    I have version 6.11.3 of the plugin. MySQL 5.7, WordPress 6.9.4.

    The access_token column in wp_sbi_sources is varchar(1000). The current stored value is 457 characters.

    Does Instagram Feed 6.11.3 still expect wp_sbi_sources.access_token to be VARCHAR(1000), or should newer encrypted access tokens use a TEXT column?

    Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Smash Balloon Louis

    (@smashballoonlouis)

    3 weeks, 3 days ago

    Hi @metricmedia,

    Thank you for contacting us, and for the detailed report! I’ll be happy to help with this.

    To answer your question first: the column type hasn’t changed since 6.11.3. Rather than this being a problem with the size of the column, this error is most likely caused by an issue that occurred during the encryption of the token that’s stored there.

    The best way to clear that up is to remove and reconnect your source, which stores a fresh token:

    1. Go to WordPress Dashboard > Instagram Feed > Settings.
    2. Locate your connected source and click the trash/delete icon to remove it.
    3. Click Save Changes.
    4. Click Add Source and reconnect your Instagram account.

    Once reconnected, please check whether the error still appears when accessing the Settings page.

    If those steps don’t resolve the issue, could you please submit a ticket on our web site https://smashballoon.com/support/ so that we can investigate this further with you?

    I hope this helps!

    Thanks!
    Louis

    Thread Starter metricmedia

    (@metricmedia)

    3 weeks, 3 days ago

    The error does still appear in admin. After deleting the source and saving, the error continued to appear, as it did after re-adding and saving. I am seeing current posts on our public site, but the last post was made 6 days ago. No error message when viewing on the public site.

    Should I just delete the entry in the db and try again?

    Plugin Support Smash Balloon Louis

    (@smashballoonlouis)

    3 weeks, 3 days ago

    Hi @metricmedia,

    Thank you for the update and sorry to hear those steps did not resolve the issue.

    Deleting the entry in the database likely wouldn’t cause a problem, but this is essentially what the plugin is doing when you remove the source from within the plugin UI. A safer and more complete option would be to full deactivate and delete the plugin, and then do a fresh install. This will drop and then recreate all the data for the plugin. You would need to reconnect your account and recreate any feeds after this.

    If this does not resolve the issue, if you could please submit a ticket through our web site https://smashballoon.com/support/, we can investigate this more closely to find a solution.

    Thanks!
    Louis

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

You must be logged in to reply to this topic.