Database error since 4.1.3.1 update/introduction of notifications page

  • Resolved Mitchell Gilbertson

    (@mgilbertson)


    3 years, 3 months ago

    I’ve been getting these warnings ever since the most recent update that added the notifications page.

    WordPress database error: [Unknown column ‘new’ in ‘where clause’]
    SELECT * FROM wp_aioseo_notifications WHERE 1 = 1 AND dismissed = 0 AND new = 1 AND (start <= ‘2021-08-12 21:09:48’ OR start IS NULL) AND (end >= ‘2021-08-12 21:09:48’ OR end IS NULL) ORDER BY start DESC, created DESC /* 1 = 1 */

    WordPress database error: [Unknown column ‘new’ in ‘where clause’]
    UPDATE wp_aioseo_notifications SET new = 0 WHERE 1 = 1 AND new = 1 /* 1 = 1 */

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author arnaudbroes

    (@arnaudbroes)

    Hey @mgilbertson,

    Thank you for reporting this.

    That is strange. The Notifications page has been there for a while, but we did make some changes and added a new column to the database table we use in the latest update.

    Can you check the aioseo_notifications table in your database to see if it has the new column? If not, I would recommend downgrading to the previous version (4.1.2) and then updating again to 4.1.3 to see if the column is now added correctly. If not, something might be going wrong on your website when the migration that adds the column is supposed to run.

    Thread Starter Mitchell Gilbertson

    (@mgilbertson)

    Hi @arnaudbroes,

    Thanks for your reply. The

    new

    column was in fact missing from my database on the site I tested this on my localhost. Downgrading from the current version to 4.1.2.1 and then updating to 4.1.3.3 did add the

    new

    column to the database as you predicted.

    However, when I tried this same thing on the staging URL for this site, the

    new

    column was not added, and the database errors appeared again after updating back to 4.1.3.3. So for whatever reason, the column is being added to the table when upgrading to 4.1.3.3 on my local environment, but not on my live environment. Definitely a strange issue, and I have no idea what would be causing this. This does seem to be a consistent issue across every site that I’ve worked on since this update(20+ sites, at least). These sites are hosted through WPEngine, if that information helps at all.

    Any ideas why this might be?

    Plugin Author arnaudbroes

    (@arnaudbroes)

    Hey @mgilbertson,

    Thank you for getting back to me.

    That’s strange. So far, we’ve only had one other report about this besides yours. Obviously it’s a pretty obscure issue because otherwise we would have gotten a lot more reports by now.

    Anyway, would you mind reaching out to us via our basic question form here so that we follow up with you more quickly and figure out why this is happening on your websites – https://aioseo.com/contact/

    A migration should have ran after you updated the plugin to add the new column to the table, but for some reason it either didn’t run at all or simply failed to add the column on your websites.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Database error since 4.1.3.1 update/introduction of notifications page’ is closed to new replies.