Seems like today's update broke uploading through the bookmarklet from pixiv, somehow. I keep getting a "NameError exception raised uninitialized constant UploadsController::HTML" page whenever I try.
Posted under General
This topic has been locked.
API is using new wrapper objects now, too... (issue #2506)
Searching for gofu -monochrome returns the error: "canceling statement due to statement timeout." Searching for -monochrome by itself or with another artist doesn't cause the error. Searching for gofu and, for example, -smile doesn't cause the error either.
Also, 2k-tan and me-tan return the same error.
demosquid said:
Searching for gofu -monochrome returns the error: "canceling statement due to statement timeout." Searching for -monochrome by itself or with another artist doesn't cause the error. Searching for gofu and, for example, -smile doesn't cause the error either.
Also, 2k-tan and me-tan return the same error.
These are 6-second searches, and regular members time out after 3 seconds.
For some reason gofu -monochrome is slower at 20-posts per page than higher limits. You could try gofu -monochrome limit:50 and it should be faster.
Toks said:
For some reason gofu -monochrome is slower at 20-posts per page than higher limits. You could try gofu -monochrome limit:50 and it should be faster.
But isn't that an impossible search for normal members as it'd be three tags or is 'limit:50' something not counting as a tag?
fossilnix said:
I'm using Firefox 40.0.3, and about a month ago the bookmarklet stopped doing anything if I clicked it on a Twitter status. Now I have to directly view the image to upload it, but when I do that, there's no option to include the commentary.
Same here. It seems that it affects only to Twitter uploads, because Pixiv uploads still works fine.
fossilnix said:
I'm using Firefox 40.0.3, and about a month ago the bookmarklet stopped doing anything if I clicked it on a Twitter status. Now I have to directly view the image to upload it, but when I do that, there's no option to include the commentary.
Twitter seems to be using Content Security Policy to prevent security issues... but because of a Firefox bug, it also affects bookmarklets.