Beak
Forum Replies Created
-
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
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, 3 months ago by 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
Thanks for your response, Ojoma.
Installing via FTP still triggered the error. No change.
Do you have any other possible solutions?
Thanks.
My first impression is that adding both lines of code to the wp-config.php solved it. Thanks!
@photocrati – I installed the recent NG update, but no luck.
Do you agree to what the mailpoet guy said that the problem is caused by “NextGEN Gallery is forcing wp_head() and wp_footer() to be loaded on every single page, including MailPoet pages.” ?
And if you do, can and will this be fixed in your next update?
Thanks!
@photocrati – Thanks. I will wait for the next official NG update and see what happens.
Today I noticed that there are several side effects (error messages and changes in mailpoet display in the dashboard) of adding the code to the wp-config.php file.
So, after all this is not a solution.
Fundamentally imo the NextGEN code should just be active on NextGEN content and leave anything else untouched.
Is it possible in a future update of NextGEN Gallery, to stop forcing wp_head() and wp_footer() to be loaded on every single page?
Looking forward to hearing from you!
Thanks Benjamin – that worked! If I update to a new WP version or theme, will I have to do this again? Can I put this in my child theme file? Any info is appreciated!
Thanks for your quick reply. I will contact Mailpoet.