Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support Ojoma a11n

    (@geraltrivia)

    Hello there @beak,

    We are sorry to hear you’re experiencing this.

    As a first step, could you please try to re-install MailPoet plugin via FTP and see if that works without triggering the error? 

    Looking forward to hearing back from you.

    Thread Starter Beak

    (@beak)

    Thanks for your response, Ojoma.

    Installing via FTP still triggered the error. No change.

    Do you have any other possible solutions?

    Thanks.

    Plugin Support Ojoma a11n

    (@geraltrivia)

    Hello there @beak,

    Thank you for your update regarding the FTP installation error. I regret to hear you’re still experiencing difficulties.

    While we haven’t encountered this specific issue before, it may be related to the version of the MailPoet plugin you are using. To address this possibility, I suggest rolling back to a previous version of the plugin by following one of these methods:

    1. Use the WP Rollback plugin: https://ww.wp.xz.cn/plugins/wp-rollback/. This plugin makes it simple to revert to a former version of MailPoet.
    2. Download a previous version of MailPoet from this page: https://ww.wp.xz.cn/plugins/mailpoet/advanced/ (scroll down to the ADVANCED OPTIONS section). Then, install it via FTP, following the instructions in our guide here: https://kb.mailpoet.com/article/258-re-installing-updating-the-plugin-via-ftp.

    Please contact us via https://www.mailpoet.com/support/sales-pre-sales-questions/ and include a link to this thread so we can investigate your issue more thoroughly.

    Thread Starter Beak

    (@beak)

    Hi Ojoma,

    I am currently using MailPoet 4.7.1. and this version is working fine. The problem arises when I try to instal a higher version.

    Staying with this version is fine for now, but not a real solution. There are others who have reported similar problems around the ‘Column not found’ error on this forum, but I’ve not seen a way to fix it yet…

    The clue might be in looking at what was changed in the transition from version 4.7.1 to version 4.8.0. – where the error appears first?

    Thanks,

    Beak

    • This reply was modified 2 years, 4 months ago by Beak.
    • This reply was modified 2 years, 4 months ago by Beak.
    Plugin Support Ojoma a11n

    (@geraltrivia)

    Hello @beak,

    Thank you for reaching out and detailing the issue you are experiencing.

    Interestingly, the version you’re referring to, MailPoet 4.7.1, was indeed released on February 27, 2023. The latest version, however, is 4.41.3. I believe there might be a misunderstanding with the version numbers as they don’t necessarily follow a linear increment – thus, 4.41.3 is actually a newer version than 4.7.1.

    Often, the “Column not found” error occurs when using outdated versions of the software, and it’s likely the issues you’re experiencing are due to the older version you’re currently using. We strongly recommend updating to the latest version, 4.41.3, to benefit from the latest features, improvements, and bug fixes. It should most likely correct the error you’re facing during the transition to a newer version.

    You can download the most recent version directly from the WordPress Plugin Repository or from our website.

    After updating the plugin, if the issue persists, please provide us with additional details so we can assist you further.

    Thread Starter Beak

    (@beak)

    Hi Ojoma,

    Again: MailPoet 4.7.1 works fine. Updating to a higher version CAUSES the problem. And yes of course, 4.41.3 is a newer version than 4.7.1.

    Your advise is too general and doesn’t address the issue.

    Can you please pass this ticket to a colleague with more knowledge/experience regarding this topic?

    Thanks,

    Beak

    • This reply was modified 2 years, 4 months ago by Beak.
    Plugin Support Kel C. a11n

    (@kellymetal)

    Hi there @beak,

    That Uncaught PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column ‘t0.wp_post_id’ in ‘field list’ error can occur if there was an issue with a migration that did not complete successfully, resulting in the missing column.

    It looks like that specific wp_post_id column is added in this Migration_20230716_130221_Db migration:
    https://github.com/mailpoet/mailpoet/blob/5cd7dad6268f0735082ee856b368dfe5e4afe615/mailpoet/lib/Migrations/Db/Migration_20230716_130221_Db.php#L11

    You could try forcing it to rerun that migration by going into the *_mailpoet_migrations table, and deleting the line for that migration. Then deactivate and reactivate the plugin, and it should try to rerun the migration.

    I would definitely recommend making sure you have a complete backup of the site/database first before doing this, just in case!

    Thread Starter Beak

    (@beak)

    Hi Kellymetal,

    Thanks for your reply. Sounds like a good solution. However, I already reinstalled the plugin. I lost some data, but could keep most through exporting and importing.

    Others may find this post and use your solution!

    Thanks again,

    Beak

    Plugin Support Kel C. a11n

    (@kellymetal)

    Hi there @beak,

    Thanks for the update, and glad to hear you were able to resolve the issue through a reinstall of the plugin (though it’s unfortunate you lost some data).

    I’m going to mark this as resolved, but if you have any other questions, please feel free to open a new thread! Take care, and have a wonderful day.

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

The topic ‘Column not found – ERROR 1054’ is closed to new replies.