/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!
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 http://colorado-pinball.com/phpinfo.php
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?
@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.
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.
