Posts

Paradigm, as in from OOP (with some procedural and functional sprinkled in) to a fully functional language.

Not sure what you mean when it comes to Ecto and being tied down by schema. Not quite sure how it works with Django, but most modern ORMs let you design the schema code-first and use migrations

@Angius
Who says Phoenix isn’t in the same paradigm as Rails?

@Stellar Dust

Not sure if it’s supposed to work like that in the beta but the search posts page from the forums doesn’t show you the search options

They’re folded into the search query. Scroll down for more documentation on how that works.

@Stellar Dust

You can’t see the Historical Statistics in the stats section

I’m not sure if I will implement this.

 

This image is blocked by your current filter - click here to display it anyway

your current filter.

 
I like that statistics thingy. I don’t want to see it go away :-(

You can’t see the Historical Statistics in the stats section

Not sure if it’s supposed to work like that in the beta but the search posts page from the forums doesn’t show you the search options

@Yoshimon1

• The placeholder “Search” text of the search bar suddenly is a dark gray instead of the usual light blue-white-ish.
• Every single element on the entire site has an added line-height: 1.15 rule inherited from…
• “Watched by x users” is missing under artist links on profile pages.

A minor nitpick: if an image has no faves, on the Rails’ side the “List favoriters” tab says “Favorited by 0 users”, but on the Philomena side the same message is “Favorited by”, ie. the text just cuts off. And when there are faves, on Philomena side you get a list of favers normally, but there’s still no faves count.

The “Next” and “Last” links in the “Watched Images” section of the site’s main page don’t take you to your “watched” list.

Changing the source of an image with the same source adds a change to the source history
If you search a tag that it’s hidden or has 0 images it says “Showing results 1 - 0 of 0 total” instead of “No Images Found”

So what is your estimate on when you think you’d be releasing the source to the current state of the booru?

@byte[]

I’d like to know what the breakages are. To my knowledge the CSS is a straight copy from booru-on-rails, so this means I likely bungled the markup structure.

Oh, alright then. In that case, here’s what I noticed (Default theme):

• The placeholder “Search” text of the search bar suddenly is a dark gray instead of the usual light blue-white-ish.
• Every single element on the entire site has an added line-height: 1.15 rule inherited from…

@/**! normalize-scss | MIT/GPLv2 License | bit.ly/normalize-scss **/
html {
line-height: 1.15;
-ms-text-size-adjust: 100%;
-webkit-text-size-adjust: 100%
}@

…here in the default.css that makes everything look a bit squished together compared to before.

• media-boxes on profile pages (Recent artwork/uploads/favourites) are bigger (232x254 for me instead of the old 150x172) and there’s now 6 instead of 5, which may have been an intended change, but now makes everything very big and displayed in two lines. (Or is that a setting somewhere?)

Also:

• “Watched by x users” is missing under artist links on profile pages.
• “Posts: x” is missing under avatars in forum posts.