Posted under General
This topic has been locked.
evazion said:
Site update (2017.01.05 - 2017.01.11)
Changes
- Previous usernames are now visible to Members and up (forum #125541, topic #13516).
A small question on how this works, but when I click on previous usernames I see this 'Delete' button at the bottom... what's that for? Deleting the listed 'previous' name request, or something else?
That's an admin-only option. It's safe to click, it will give you an access denied error unless you're an admin. This page was designed for unapproved requests, so some of it doesn't make sense for approved requests. This could use some work.
As for what it does: yes, it totally deletes the request. I'm not sure why even an admin would want to do that though, it doesn't seem necessary.
Parent-child relation doesn't seem to show in Tag History.
Was updating pool #9176 with the lap_dance tag and noticed the first 3 were incorrectly using parent-child relation.
Kikimaru said:
Parent-child relation doesn't seem to show in Tag History.
Was updating pool #9176 with the lap_dance tag and noticed the first 3 were incorrectly using parent-child relation.
It was recorded in the tag history as shown below, however it wouldn't show up in the first (post #1820650) since parent posts never have a metatag as part of their tag string (unless they are a child to another post).
http://danbooru.donmai.us/post_versions?search%5Bpost_id%5D=1820653
http://danbooru.donmai.us/post_versions?search%5Bpost_id%5D=1820655
Is DanbooruBot a new feature of this site? It needs a little fix. It keeps telling me that I'm underusing the 2017, new year, yorha no. 2 type b tags. Really?
Sacriven said:
Is DanbooruBot a new feature of this site? It needs a little fix. It keeps telling me that I'm underusing the 2017, new year, yorha no. 2 type b tags. Really?
That means each of those tags was added by other users to at least 5 of your uploads from the last week, IIRC, so it's technically undertagging. It's seems to still be in alpha phase though, so to speak - ideas on how to improve are welcome.
Type-kun said:
That means each of those tags was added by other users to at least 5 of your uploads from the last week, IIRC, so it's technically undertagging. It's seems to still be in alpha phase though, so to speak - ideas on how to improve are welcome.
Hmm, maybe extend the "undertagging week" into 2 weeks? Also, increase the post limit, for 5 is too few IMO. I don't want this bot flooding my inbox just because I forgot to tag several "less known" tags.
Am trying to delete a user record I left, but keep seeing the following:
NoMethodError exception raised
undefined method `updater_id' for #<UserFeedback:0x007f0a7c45d980> Did you mean? update updated_at
app/models/user_feedback.rb:16:in `block in <class:UserFeedback>'
app/controllers/user_feedbacks_controller.rb:46:in `destroy'
Today's update removed the legacy API without warning. The legacy API was still in use by iqdb.org since it is compatible with all other boorus I index.
I know it's been deprecated for years but my understanding was that it would be kept available anyway. Since the new API has a completely different XML structure and practically all attribute names are different, it basically means iqdb would need a separate new parser just for danbooru.
Would it be possible to get the old API reactivated?
[edit] (by the way, it was commit 4b1cbb2 that broke it)
Updated
Created issue #2846 for Vote Up/Down bug.
piespy said:
Today's update removed the legacy API without warning. The legacy API was still in use by iqdb.org since it is compatible with all other boorus I index.
...
Would it be possible to get the old API reactivated?
Probably need to ping @albert so he knows. But how about preprocessing the new format into the old format? Something like this gets you halfway there, modulo the different attribute names:
$ curl http://danbooru.donmai.us/posts.xml | xsltproc elems-to-attrs.xsl - > posts.xml
$ cat elems-to-attrs.xsl
<!-- https://stackoverflow.com/questions/655411/converting-xml-elements-to-xml-attributes-using-xslt -->
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="posts">
<posts>
<xsl:apply-templates/>
</posts>
</xsl:template>
<xsl:template match="post">
<post>
<xsl:for-each select="*">
<xsl:attribute name="{name()}">
<xsl:value-of select="text()"/>
</xsl:attribute>
</xsl:for-each>
</post>
</xsl:template>
</xsl:stylesheet>