it seems like post changes history are not reflecting properly. i'm missing a few posts that i know i modified.
Posted under General
This topic has been locked.
ghostrigger said:
it seems like post changes history are not reflecting properly. i'm missing a few posts that i know i modified.
I opened issue #3378 because I found the same problem.
fossilnix said:
Is anyone else unable to upload from Twitter? I get "Couldn't get status ID from URL" errors. I'm using Firefox 57, though, so it might be a browser problem and not a site problem
Are you using the batch bookmarklet? It's currently broken for twitter, while the normal one works fine. I've already opened issue #3377 about it.
nonamethanks said:
Are you using the batch bookmarklet? It's currently broken for twitter, while the normal one works fine. I've already opened issue #3377 about it.
I'm using the normal one.
nonamethanks said:
It works fine for me. I'm on a previous version of Firefox (56). Does the source field get filled with the direct image url rather than the twitter post, like in the screencap in the github issue I posted?
If I use the bookmarklet while viewing the image directly, then the direct image link is in the source field and the tweet URL is in the referrer field, but it doesn't load the source data and doesn't show a preview image.
If I use the bookmarklet on the tweet (because Firefox 57 allows that, when 56 didn't) then the tweet URL is in the source field, and the info is loaded, but it still doesn't show a preview image.
Actually, I hadn't tried filling out the tags and clicking "upload" anyway, because I didn't want to risk it; Turns out it will upload, it's just annoying not having the artist autofill and the thumbnail in the same window for tagging
MyrMindservant said:
On a slightly related note, can someone remind me CSS to remove the huge "Favorite" button under posts?
It’s in the Custom CSS thread: forum #135438
Odd behavior
Searched "northern_ocean_hime seaport_hime" get no page mobility and I know it's got a LOT of art. So I kludge together a view page 10 of search results and it resolves to showing page 10 of results with the ability to go back to page 9 then back to page 8 all the way back to the front but not able to go forwards
It seems to be on all two tag searches now.
Worked out fine yesterday so not sure what broke today
Edit: Screenshot
Edit: Searching for "northern_ocean_hime" or any single tag gives proper behavior
Updated
jigo_kudani said:
Im getting no ability to swich pages with the search "-impossible_clothes -cleavage -panties -swimsuit -male_focus -comic"
changing the page number in the url works but its not the best solution
Firstly, please surround searches with double curly brackets {{tag1 tag2}} to make them clickable: -impossible_clothes -cleavage -panties -swimsuit -male_focus -comic
Do you get no paginator (the thing with page numbers and arrows) at all or just no page numbers but still the arrows?
The problem with your query is that there’s no inclusive tag, only exclusive tags. For a search like original -impossible_clothes, the database can quickly take all original posts and then remove all posts with impossible_clothes from them. Your search has no starting point, so the database has to go through all posts and remove what you don’t want, which is very slow. This is less of a problem when picking only 40 posts to show you, but it’s a big problem for the paginator because the site needs to know how many matching posts there are to display the correct page number range. If the database runs into a timeout, no paginator will be shown.
You can get around that problem by specifying a post ID range and hopping from one range to the next, like so: id:2500001..3000000 -impossible_clothes -cleavage -panties -swimsuit -male_focus -comic and then 2000001..2500000, etc. The database will have a starting point and will return results much quicker. As a Gold user, you will have to sacrifice one of your six tags in the search for it, though. If you’re into user scripts, the Danbooru 2 Tweaks script in topic #56209 has an option to display a second paginator for post ID ranges if you use them.
Greasemonkey (now Ver. 4) and Firefox (now Ver. 57) have both undergone major overhauls from their respective preceding versions, and one or both appear to have rendered Danbooru Miscellaneous Tweaks incompatible. I tried disabling Greasemonkey and installing Tampermonkey, but that didn't seem to bring the tweaks back up. I may have overlooked something, though.
The search field shows on top of the popped-out tag box (Screenshot)
Moonspeaker said:
Greasemonkey (now Ver. 4) and Firefox (now Ver. 57) have both undergone major overhauls from their respective preceding versions, and one or both appear to have rendered Danbooru Miscellaneous Tweaks incompatible. I tried disabling Greasemonkey and installing Tampermonkey, but that didn't seem to bring the tweaks back up. I may have overlooked something, though.
@Moonspeaker, if you switched to Tampermonkey, your settings aren't going to get carried over, and all tweaks are disabled by default. They work for me.
What a mess. Figured out how to modify scripts to work with Greasemonkey 4, realized that not all scripts had carried over, realized there's no way to manually install local scripts yet, gave up and switched to Tampermonkey.
kittey said:
Firstly, please surround searches with double curly brackets {{tag1 tag2}} to make them clickable: -impossible_clothes -cleavage -panties -swimsuit -male_focus -comic
Do you get no paginator (the thing with page numbers and arrows) at all or just no page numbers but still the arrows?
The problem with your query is that there’s no inclusive tag, only exclusive tags. For a search like original -impossible_clothes, the database can quickly take all original posts and then remove all posts with impossible_clothes from them. Your search has no starting point, so the database has to go through all posts and remove what you don’t want, which is very slow. This is less of a problem when picking only 40 posts to show you, but it’s a big problem for the paginator because the site needs to know how many matching posts there are to display the correct page number range. If the database runs into a timeout, no paginator will be shown.
You can get around that problem by specifying a post ID range and hopping from one range to the next, like so: id:2500001..3000000 -impossible_clothes -cleavage -panties -swimsuit -male_focus -comic and then 2000001..2500000, etc. The database will have a starting point and will return results much quicker. As a Gold user, you will have to sacrifice one of your six tags in the search for it, though. If you’re into user scripts, the Danbooru 2 Tweaks script in topic #56209 has an option to display a second paginator for post ID ranges if you use them.
Still doesn't explain my problem though as mine is similar but is inclusive tags (two character tags) but still gives the problem shown in my screenshot.
I just get the arrows but nothing else. Unless the search time is so incredibly limited now for non-pay users that two tags is impossible to search for. (Which is a rather bullshit IMO as it's stripping basic functionality from the site and paywalling it)
I've cut down to a smaller search tani_takeshi hakurei_reimu which is a 2.5k primary tag which produces about 12.5 pages of results with default settings
I only get the arrows and never the page numbers.
Updated
Zelinkokitsune said:
Still doesn't explain my problem though as mine is similar but is inclusive tags (two character tags) but still gives the problem shown in my screenshot.
I just get the arrows but nothing else. Unless the search time is so incredibly limited now for non-pay users that two tags is impossible to search for. (Which is a rather bullshit IMO as it's stripping basic functionality from the site and paywalling it)
I've cut down to a smaller search tani_takeshi hakurei_reimu which is a 2.5k primary tag which produces about 12.5 pages of results with default settings
I only get the arrows and never the page numbers.
I’m pretty sure that your paginators not showing page numbers is due to the timeouts I explained. Basic users always had a lower timeout than Gold users and it didn’t get reduced. During the past few days, the database has been under a lot of stress from the recent update(s), so it’s been slower for everyone, but basic users run into timeouts more easily, even with inclusive searches. It’ll hopefully be back to normal soon.
Zelinkokitsune said:
...
To add onto what kittey said, I can't replicate any of your issues with an anonymous login on Internet Explorer. I tried every search you mentioned that had an issue, and all of them work just fine. Just for reference, Anonymous has the same timeout and tag restrictions as Member-level users (Help:Users).
Therefore, I'm guessing that there's something else going on.
Have you tried those searches on a different browser...? Additionally, you could try resetting the cache and cookies for this site, or resetting the browser itself.
fossilnix said:
The search field shows on top of the popped-out tag box (Screenshot)
Created issue #3383.
