An error has happened while performing a request, the server has responded with

  • I am unable to see my list of subscribers or forms. When I attempt to view them, I get the error message:

    An error has happened while performing a request, the server has responded with response code 200

    And my users get an error message when signing up for my newsletter on my site. (However, I noticed that in spite of the error message, they are being added to the database.)

    I’m not sure this is related, but today I modified the database and set the Engine=innodb on all tables. I’m wondering if I should set them all back to MyISAM.

    I’m not seeing any errors in the logs.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Lynn J.a11n

    (@lynnjat7)

    Hi there @nocloset,

    This error is a little confusing, as “response code 200” is the typical response code for a successful request, and yet an error has happened.

    We usually only see this unusual situation when there is a code conflict on the site. For MailPoet in particular, out email designer can make MailPoet screens sensitive to other plugins that alter the dashboard.

    We would recommend running a conflict test on the site. Here’s how to do that:
    https://kb.mailpoet.com/article/204-how-to-test-for-plugins-conflict

    If you are still able to cause the error while in conflict test mode (i.e. running a basic theme, and no plugins other than MailPoet are active), please let us know and include your System Info with your reply (available under MailPoet > Help on the “System Info” tab).

    Thread Starter nocloset

    (@nocloset)

    I ended up restoring backups of my database and files to before I changed from MyISAM to InnoDB and before I installed MP 5.1. I’m now running MP 5.0.2 again, and things seem to be working.

    I’m not comfortable installing MP 5.1 until I’m confident that this whole issue has been resolved.

    Plugin Support Thu P. a11n

    (@thup90)

    Hi there,

    We are not able to replicate this issue from our end. It seems this error might be related to your site only. Without being able to replicate, we won’t be able to fix it.

    I’d recommend creating a staging site and perform a conflict test as suggested earlier to find out what is causing the error. If your host doesn’t offer that option, I’d recommend WP Staging for quickly copying your site to a staging environment.

    Feel free to get back to us in case you have any additional questions!

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.