Danbooru

Read the rules before proceeding!

Topic: Change log - 3/13

Posted under General

albert

  • Janitors can now lock and unlock forum topics
  • Forum topics can no longer be permanently deleted. Instead they are simply marked as deleted and hidden from view. They can be undeleted.
  • Pools can no longer be permanently deleted. The original active flag is now only editable by janitors and above, and this governs whether or not a pool is visible.

Updated by S1eth

  • ID: 75113
  • Permalink
  • dean exia

    albert said:
    Pools can no longer be permanently deleted. The original active flag is now only editable by janitors and above, and this governs whether or not a pool is visible.

    Much appreciated.

    EDIT: Still, there are defects in this, like what happened to inactive pools.

    Updated by dean exia

  • ID: 75114
  • Permalink
  • Log

    albert said:

    • Pools can no longer be permanently deleted. The original active flag is now only editable by janitors and above, and this governs whether or not a pool is visible.

    What? This needed to be a completely new flag, now the add to pool listing is going to need to be hundreds of pages long. There's no reason for a finished comic to have a pool that shows up in the add to pool listing.

    Apparently janitors quoting also adds an edited by note.

    edit: haha no it tracks who bumped the thread I think. This is not working even remotely correctly.

    Updated by Log

  • ID: 75115
  • Permalink
  • RaisingK

    Is that so...

    Log edit: Let's try editing someone else's post!

    Updated by RaisingK

  • ID: 75116
  • Permalink
  • m3mn4rch

    albert said:

    • Pools can no longer be permanently deleted. The original active flag is now only editable by janitors and above, and this governs whether or not a pool is visible.

    Would this update it be related to why some older images no longer think they're in a pool, even though the pool itself still shows them as being part of it?

    Edit: looks like it cuts out around page 55 of the general pool at "Strike Witches - Cold Winter 1947 (Shimada Fumikane)" (pool #3956 doesn't work) and "Strike Witches - Captains (Sample) (Kisetsu)" (pool #4572 works), though it doesn't seem to be limited to that.

    Edit edit: also interesting, (pool #1017) is above (pool #4572) on the page, but (pool #4584) on page 56 doesn't work.

    Updated by m3mn4rch

  • ID: 75117
  • Permalink
  • Wypatroszony

    RaisingK said:
    Is that so...

    That is so. The opening post displays the most recent edit/post with the username of the last user posting/editing in any message in the thread. In any other post, it's "edited" by "Anonymous" (as if no-one would have guessed by now) which also happened to be an issue (not really) in post searching much before this. Oddity taken to a brand new level.

  • ID: 75118
  • Permalink
  • Hillside Moose

    albert said:

    • Janitors can now lock and unlock forum topics
    • Forum topics can no longer be permanently deleted. Instead they are simply marked as deleted and hidden from view. They can be undeleted.

    Does this mean Janitors no longer have the ability to "delete" threads now that they can lock them? Do these thread "deletions" show up on the Mod Action page?

    Pools can no longer be permanently deleted. The original active flag is now only editable by janitors and above, and this governs whether or not a pool is visible.

    Really Albert? The active flag was used to stop finished pools from showing up on the pool listing. You just amputated what must be hundreds of pools with this update. Like Log said, it needs to be its own flag.

  • ID: 75130
  • Permalink
  • Kikimaru

    Oh dear...

    Also, what's up with the "updated by Anonymous" at the bottom of every forum post?
    Seems very superfluous.

  • ID: 75138
  • Permalink
  • Log

    It's supposed to track when someone other than the user edits a post. I'm not sure why this needs to be on every post or why it needs to be public but there you go.

  • ID: 75139
  • Permalink
  • Fred1515

    I hope these issues can be quickly resolved, these changes aren't worth the trouble otherwise. They broke more things than they fixed.

  • ID: 75143
  • Permalink
  • albert

    The bugs with the pools should be fixed now.

  • ID: 75151
  • Permalink
  • dean exia

    albert said:
    The bugs with the pools should be fixed now.

    *checking pools*
    The pools are back. Thanks.

  • ID: 75152
  • Permalink
  • jjj14

    Um, it seems that pools can now no longer be set as "public". There's no "public" checkmark, just one for "active".

  • ID: 75169
  • Permalink
  • Log

    Deleting a thread bumps it like it was edited and makes the forum appear to have unread messages despite it just being a deleted thread.

  • ID: 75260
  • Permalink
  • RaisingK

    I was able to make my latest pool public by using the Tamper Data extension to modify a pool/update request to include "pool%5Bis_public%5D=1" in the parameters.

    When I try to do this with the API and the location bar, however, it doesn't do anything.

    Entering the below into the location bar from a /pool/update/ page will let you make it public. I can't get it to do the opposite, though:

    javascript:var public = document.getElementById("pool_is_active"); if( public ) { public = public.parentNode.appendChild( document.createElement("tr") ); public.innerHTML = '<th><label for="pool_is_public">Public</label></th><td><input checked="checked" id="pool_is_public" name="pool[is_public]" type="checkbox" value="1"></td>'; }; void(0);

    On a side note, the "is_active" flag appears twice in the pool/update request, once as 0 and once as 1...

    Updated by RaisingK

  • ID: 75501
  • Permalink
  • 葉月

    And for sanity-related goodness, why was it not handled by adding history of changes, just like EVERY OTHER DELETE-RELATED FUNCTIONALITY we have around here? I fully agree with the notion that basically no data should be ever fully deletable through the web UI (ie. you have to have SQL powers to banish it for good), but christ almighty, that's not how you do it. It's not even how you have done it before.

  • ID: 75514
  • Permalink