Report site bugs here

NOT A BUG, more of a testing update:
 
Philomena is significantly improved over BooruOnRails in terms of aliasing and de-aliasing tags. Here is a write-up of a de-aliasing experiment along with some examples of use cases for this process and steps for others to follow if they need to do this.

Moderation Bug:
 
On reports, when sending a PM using the link on the report itself, the subject field is empty. Previously, it would be populated with the title of the report (ex: “Your report of image >>foo”).
 
Since I reply to most reports, this means that for every report now I need to copy both the user’s request, and then the subject of their report to populate the subject line, which adds a bit more time and clicks to closing the report. It would be handy if the subject line could please be autofilled again.

I encountered a bizarre bug. Clicking on the link inside a comment replying to a deleted one results in the full page being loaded again inside the preview. Examples inside this comment thread.

@Brokedownandmadeone  
i believe this also happens on images that have been merged, with replies attempting to link to a comment made on the old image which no longer exists

It seems stream links in the sidebar on the front page link to derpibooru.org and not the actual stream channel. Also, I’m not sure if the number next to “Live” on the navigation bar is supposed to be the number of live channels, but currently it’s not.

@wallparty  

 
i think that number counts nsfw channels as well, which are hidden by default (you can change that in the local tab of the settings page)

@Perplexiah  

 
Ah, wew, thought it was something like that but didn’t know it was an extra option in settings >_>. Thanks!

Rearranging of images in galleries seems to be somewhat broken. I saw images out of the order I put them and tried to rearrange to fix them, only to find that they can’t be moved to different pages any more, and so after hitting save they were randomly shuffled around

The DNP Request Form gives a 404 when submitted, and the request does not appear to go into the queue

I like how moderators are posting in here just like us. Who actually does the coding for the site anyway?

@O. Hancock  
Byte[], mostly.

@O. Hancock  

 
The staff features probably weren’t tested as much given only staff can use them…

@Wiimeiser  
Ahh, good point. I wasn’t, uhh, complaining or mocking anyone or anything btw. I was sincere when I said I liked how there were in here.

@Wiimeiser  
I don’t know about that side, but I hammered the user side of things as much as I could. Still am poking at things, but also looking at potential improvements to suggest once the woodchips are cleared.
 
There’s just a LOT of site to have to prod at, and stuff that I couldn’t actually poke because I just don’t have a way to (things like the DNP entry page, the streaming registration, etc).

@O. Hancock  
The code is publicly released, so there’s no point in having a “secret bug list”.
 
@Wiimeiser  
The priority was getting user features completed and tested first. There’s a lot of stuff in the staff side we can do by hand, or wait a couple weeks to get finished, so they weren’t a priority. But documenting them and keeping track of their relative pain levels is a good step now that the site is live.

@O. Hancock  
The lead developer is byte[], who wrote a majority of the code for Philomena. Meow (Luna) has also contributed a lot, particularly towards staff tools.
 
I’ve added a few things, but I’m not very knowledgable about the language yet. Then there’s also been some community contributions too as the code is open source and anyone can submit code changes.
 
@Wiimeiser  
The DNP form isn’t a staff tool. It doesn’t get too much use though (luckily), so it probably wasn’t test as much. Key features of the site are searching, tagging, commenting, etc.

>>1473399 is appearing in the Trending Images despite being several years old. Was there a merge at some point?

@Wiimeiser  
Yes, it was merged a day ago. You can see this yourself by looking under the Reporting tab on the image itself, then opening the “Updating/merging” link.

@Wiimeiser  
I accidentally screwed up the code that sets first_seen_at. It’s fixed now.

For anyone having issues with the markup, please try enabling the experimental parser in your settings (local tab). I rewrote the entire thing and it is as far as I can tell much better able to handle the corner cases than the current one.

@Derpy Whooves  
@Altopony  
Admin rename doesn’t leave old username visible on old comments. While that’s kinda the point, it really should have the option if userside renames are going to be unimplemented for a while.

@Barhandar  
Sometimes it’s useful for name changes that staff makes to not be reflected on the site. For example if someone accidentally uses their Email address as their profile name, or when someone has a need to “disappear” for personal reasons. It’s fine if that would be an option, but it’s really important that the underlying functionality of changing the name without public tracks is preserved.
 
And, once the feature re-appears on everyone’s profiles, it’s really not necessary for staff to have that option. If people can change their own names, they can change their own names. And the “Staff does it” can remain “And no one can see the bread crumbs except for staff”.

@Derpy Whooves  
Hence, “option”. I recognize there is a valid need for such changes, but it’s not applicable to this specific situation of “one of booru-on-rails options isn’t transferred to Philomena yet”.

@Barhandar  
I’d rather just see the feature re-added to the accounts settings.

Just saw that comment transfer during image merge bug has been fixed, but however, I can’t find some of my comments from the old images in the newer ones, I posted some of them before the merge when that bug still happened, but it still didn’t transferred to the new image after this fix happened.