• I’m not the most internet savvy, so I apologize in advance.

    I can draw a diagram with the native shapes and the plugin saves everything just fine. But what I want to do is draw arrows and callouts on top of an image. The image I’m using is 397 KB.

    The image inserts just fine and I can make the drawing but when I click save, the “saving…” pop-up just spins it’s wheel. Opening Chrome’s Developer Tools shows the following error: “Failed to load resource: the server responded with a status of 413 (Request Entity Too Large)”

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter snowgalvin

    (@snowgalvin)

    /wp-admin/admin-ajax.php:1 Failed to load resource: the server responded with a status of 413 (Request Entity Too Large)

    Thought I’d add that admin-ajax part, if it helped you to understand what’s happening.

    Thanks!

    Thread Starter snowgalvin

    (@snowgalvin)

    I contacted DreamHost with the same question and here’s the response:
    Has the plugin’s author come back to you? It looks like that’s related to the PHP memory which can be increased, but we will need to know exactly what limit needs to be increased

    You can check the current values here https://colorado-pinball.com/phpinfo.php

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    It’s not actually PHP memory, it’s the LimitRequestBody Directive. What it implies is that this plugin is transmitting all the data from your drawn shape to WordPress via the body of the post.

    And yes, this could happen if a traditional image upload is too big.

    It looks like you’re on a shared host, so it’s VERY possible the issue is that the plugin is sending ‘too much data’ for shared to process safely. I work for DreamHost, and we do limit how big that body can be, for sanity. All hosts do.

    Question for the developer: What are your server requirements for this?

    Plugin Author assortedchips

    (@assortedchips)

    @ipstenu thanks for chiming in. There are no server requirements, per se, since I don’t feel it is the plugin’s place to mandate a maximum drawn file size. It sounds like if a user has a particular use case in mind which includes embedding very large images, then that is the server requirement for that particular scenario. The image 397 KB size that @snowgalvin called out does not seem unreasonably large.

    I can add something to FAQ about this, and can also explore changing how the drawn image gets uploaded back to the server, but ultimately this does seem like a server setting limitation like you pointed out.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    It’s not about the file size as much as he amount of data your plugin is passing back to generate the image. You’ll need way more than 300k to draw that image after all.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Request Entity Too Large’ is closed to new replies.