This topic is locked.
LOL, another bug: see link above.
Use "<<" and ">>" around link. Or add a space after the link.fireattack said:
LOL, another bug: see link above.
I think enter/newline should play the same role as space.van said:
Use "<<" and ">>" around link. Or add a space after the link.
That one is known bug which also happens in danbooru :Dfireattack said:
LOL, another bug: see link above.
Seems like Japanese Characters aren't working for the tag subscription name. They show up as a line of 2 underscores.
Should work again now.aoie_emesai said:
Seems like Japanese Characters aren't working for the tag subscription name. They show up as a line of 2 underscores.
It's not a "new" problem. Sometimes the dupe detector was shown as "down", and I thought it just down temporarily.
Today I found it's just always down for some images, like post #213764: https://yande.re/post/similar/213764?services=local Find similar works, though.
Today I found it's just always down for some images, like post #213764: https://yande.re/post/similar/213764?services=local Find similar works, though.
Apparently it'll always show "down" status when using local or yande.re service. I'll see how to fix this sometime later this week.fireattack said:
It's not a "new" problem. Sometimes the dupe detector was shown as "down", and I thought it just down temporarily.
Today I found it's just always down for some images, like post #213764: https://yande.re/post/similar/213764?services=local Find similar works, though.
Nope. Most of posts can use "find dupe" and it works well.edogawaconan said:
Apparently it'll always show "down" status when using local or yande.re service. I'll see how to fix this sometime later this week.
examples which really have dupes:
https://yande.re/post/similar/213760?services=local lolspace
https://yande.re/post/similar/213731?services=local lolspace
Others which can't find dupe won't show (down) either:
https://yande.re/post/similar/213739?services=local lolspace
https://yande.re/post/similar/213738?services=local lolspace
So as I said, the (down) problem happens only on SOME iamges. I often use this feature to parent posts so I'm sure about it.
Just noticed I can't even type two urls in diff lines.edogawaconan said:
That one is known bug which also happens in danbooru :D
And danboru doesn't have this bug, i just tested:
http://danbooru.donmai.us/forum/show/77035
Weird, testing using their parser in wiki/add preview feature ( http://danbooru.donmai.us/wiki/add ) also showed this problem.fireattack said:
Just noticed I can't even type two urls in diff lines.
And danboru doesn't have this bug, i just tested:
http://danbooru.donmai.us/forum/show/77035
The parser is in process of being fixed (or rewritten) anyway.
Would be nice if you have more example of posts which have similar problem.So as I said, the (down) problem happens only on SOME iamges. I often use this feature to parent posts so I'm sure about it.
I will try..edogawaconan said:
Weird, testing using their parser in wiki/add preview feature ( http://danbooru.donmai.us/wiki/add ) also showed this problem.
The parser is in process of being fixed (or rewritten) anyway.
Would be nice if you have more example of posts which have similar problem.
https://yande.re/post/similar/213792?services=local lolspace
Multiple links per line one after another is causing all of them to not work properly. since it connects to an invalid url. Such as fireattack's multilinks from forum #14502. I had to add a separate them for the links to work.
Before when you click "View larger version", the larger image showes from up to down (or from blur to clear, if it's a progressive JPEG) in Firefox. But in Chrome, it wouldn't show anything until the full image was loaded. I didn't have chance to test other browsers.
From about several days ago, maybe due to some code update of my Firefox (13b) or site, Firefox works exactly like Chrome, which is very undesirable for me. Is it possible to restore it back by modify Post.highres();? Of course if you can make Chrome works like Firefox too it would be the best.
Tried with fx12 too, same problem.
--
updated: after some tests, i still can't let it work like before anymore..
From about several days ago, maybe due to some code update of my Firefox (13b) or site, Firefox works exactly like Chrome, which is very undesirable for me. Is it possible to restore it back by modify Post.highres();? Of course if you can make Chrome works like Firefox too it would be the best.
Tried with fx12 too, same problem.
--
updated: after some tests, i still can't let it work like before anymore..
And I should mention danbooru doesn't have this problem in Firefox.
for example, open http://danbooru.donmai.us/post/show/1164790 with firefox, then left click on "4999x3403 (1.8 MB)".
for example, open http://danbooru.donmai.us/post/show/1164790 with firefox, then left click on "4999x3403 (1.8 MB)".
All right, apparently this bug is quite weird ಠ_ಠFrom about several days ago, maybe due to some code update of my Firefox (13b) or site, Firefox works exactly like Chrome, which is very undesirable for me. Is it possible to restore it back by modify Post.highres();? Of course if you can make Chrome works like Firefox too it would be the best.
The problem starts when I replacing about:blank instances in javascript with /image/blank.gif.
As it turns out, the "about:blank" in chrome and firefox behaves differently: firefox tries to load http://yande.re/post/show/123/about:blank while chrome tries to load "about:blank" (the blank page) - that explains why it behaved differently between firefox and chrome.
Now after I replaced it with /images/blank.gif, both behaves exactly same - the unwanted one. small image ==> blank ==(wait_until_complete) ==> full.
Even if I change the url to something nonexistent, behavior in chrome stays same (small image ==> error/blank ==(wait_until_complete) ==> full) while it reverted to correct one in firefox.
tl;dr:
bug turned into feature, fixed bug: loss of feature (ノಠ_ಠ)ノ彡 ┻━┻
I'll see if there's actual solution for this.
I think it should be fixed now. Force reload the site to see the update.I'll see if there's actual solution for this.
yeah works fine now. thanks for fixing.
I don't know whether it's a bug or not, but it seems that i can't download from pool anymore. Every time i tried to download, the download always stopped at 3 MB. Looks like another people is having the same problem, since i saw their post complaining about unable to complete download. I tried to download some illustration from the pool, but always failed at 3 mb. I tried more than 10 times, still no luck. Hope you can fixed this. If there's someone who manage to solve this problem, or doesn't have problem like this at all, could you tell me how you do that? What browser did you use? Thanks.
Yes, I'm also having this problem :( Or at least few weeks ago when I was trying to download something.rro said:
I don't know whether it's a bug or not, but it seems that i can't download from pool anymore. Every time i tried to download, the download always stopped at 3 MB.
My wild guess says it has something to do with cloudflare not supporting large file download quite well.
On the following page: https://yande.re/post/index?tags=moonstone
"The following tags are ambiguous: ["moonstone"] " points to a malformed url:
https://yande.re/post/\"/wiki/show?title=moonstone\"
"The following tags are ambiguous: ["moonstone"] " points to a malformed url:
https://yande.re/post/\"/wiki/show?title=moonstone\"
Fixed. Thanks!Cyberbeing said:
On the following page: https://yande.re/post/index?tags=moonstone
"The following tags are ambiguous: ["moonstone"] " points to a malformed url:
https://yande.re/post/\"/wiki/show?title=moonstone\"
https://yande.re/history?search=tag%3A10625 lol space
leads to error
leads to error
Should be all right now (962a2aca030e)
"» History for tag: moonstone" points to the wrong page?fireattack said:
https://yande.re/history?search=tag%3A10625
https://yande.re/tag/show/10625
All right, should be fixed now. The previously used parser engine broke on slightly weird xml files.fireattack said:
It's not a "new" problem. Sometimes the dupe detector was shown as "down", and I thought it just down temporarily.
Today I found it's just always down for some images, like post #213764: https://yande.re/post/similar/213764?services=local Find similar works, though.
Is me the only one think the new style of quote is worse than before? Also curious why bother to change it?
Because with previous style the links are unreadable. I'm testing one of the solution. Inputs and suggestions are welcome.fireattack said:
Is me the only one think the new style of quote is worse than before? Also curious why bother to change it?
Looks great to me.edogawaconan said:
Because with previous style the links are unreadable. I'm testing one of the solution. Inputs and suggestions are welcome.
fireattack
https://yande.re/post/index?tags=akko
Maybe you meant: dakko_shite_gyu!, gakkou_no_kaidan, hakkoo, hyakko, rakko, orshiritsu_sakuranbo_shougakkou
between or and shiritsu_sakuranbo_shougakkou