2.1.0 issues

  • Resolved Bas Buis

    (@basbuis)


    2 weeks, 6 days ago

    Since the update to 2.1.0 my client could not use their connection to the website anymore. I rolled back to 2.0.1.

    Info: Cursor pro was used and it worked perfectly before the update.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Buddy

    (@friendswp)

    2 weeks, 6 days ago

    hi, can you share a bit more details about the errors that he got? Have you tested with v2.1.1 and is still not working?

    We can look into this right away.

    Thread Starter Bas Buis

    (@basbuis)

    2 weeks, 6 days ago

    My client makes posts for his website with Cursor and Easy MCP AI.

    I updated your plugin at 15.45 Spanish time. Sometime later the client called that nothing worked anymore; he just waits and waits.

    Everything on the site looked good, so I decided to roll back the version. 5 minutes later the client sends an email that everything works again.

    He works from a Cursor Project, not the standard chat. Maybe that makes a difference in the latest version of your plugin.

    Errors like this:

    https://mega.nz/file/fkJTgQrY#_jCICTS22EsQ2V-LM1t05oWIcopaflz-syfZxh04wpw

    Plugin Support malexandric

    (@malexandric)

    2 weeks, 5 days ago

    Hi @basbuis,

    Thanks for the screenshot!

    The log shows Cursor connected and working (for example, the media delete went through). What fails is every call to upload an image (wp_upload_media). Cursor’s agent then keeps retrying with different made up arguments, like file paths on the Mac or a temp file, which the site can’t read. That retry loop is the “waiting” your client saw.

    This upload tool works the same way in 2.0.1 and 2.1.x. It expects the image itself as base64 text inside the request, and AI agents in Cursor usually can’t write out that much text for a normal sized image.

    Since the site is on 2.0.1 now, could you ask your client to try one quick test? In the same Cursor Project, ask the agent to upload the same image it was trying to upload before. Then let us know if it worked. If it failed, please click the red “Error” row in the Easy MCP AI log and send us the message shown there.

    If it fails on 2.0.1 too, the cause is the image upload limit and not the update. These two ways work reliably:

    1. If the image is already online, ask the agent to use wp_upload_media_from_url with that public link.
    2. Or upload the image in Media Library yourself, then ask the agent to use it by its media ID (as a featured image or in the post).

    If it works on 2.0.1, then 2.1.0 changed something for you and we’ll look into it right away.

    Let us know what you find.

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

You must be logged in to reply to this topic.