apioforum, branch thread-filtering-2apionic forumhttps://g.gh0.pw/apioforum/atom?h=thread-filtering-22022-06-10T23:21:48+00:00make radio buttons inline instead of on multiple lines2022-06-10T23:21:48+00:00ubq323ubq323@ubq323.website2022-06-10T23:21:48+00:00urn:sha1:421e5d579a005214a7ff3f3305b76e8be8037694make ui of tag filtering use radio buttons instead of links2022-06-10T23:03:48+00:00ubq323ubq323@ubq323.website2022-06-10T23:03:48+00:00urn:sha1:b2ac344c4bb4e2fed50a5e6925cdfef9c8cd041aadd tag filtering2022-05-14T02:41:01+00:00ubq323ubq323@ubq323.website2022-05-14T00:25:10+00:00urn:sha1:95744c80aae576aabd8961ecee2035b317a5849c
the only currently supported form of tag filtering is by specifying
a single tag, and then only threads with that tag will be displayed.
this meets all of the reasonable use cases i can think of right now.
add ability to sort threads by creation or modification, asc or desc2022-05-13T21:39:37+00:00ubq323ubq3232021-07-22T18:35:01+00:00urn:sha1:14f72326212adc91f27c436e201a19c431eab3e2fix permissions for view_post, and 404 instead of redirecting2022-05-13T20:46:16+00:00ubq323ubq323@ubq323.website2022-05-13T20:46:16+00:00urn:sha1:6f5741731efac510336e2b5d512b4523b9d8da13
previously it was possible to see posts you didn't have permissions
to view, by using /view_post/<id>. now, this checks permissions.
previously if a post with the given id did not exist, it would
redirect you back to /, with an error message. now, it gives
a 404 page, which is consistent with the behaviour when a thread
or forum with the given id is not found.
improve pagination navigation2022-03-02T14:59:08+00:00the lemonscitrons@mondecitronne.com2022-03-01T19:00:36+00:00urn:sha1:3644b35b92494965edb4916fdb368fd49c8d4bf2
* pages show more content
* the navigation bar is shown regardless of scroll position
* the navigation bar now lives in a box
* the navigation bar adapts to small screen sizes
I changed the padding now.
disable pulsate animation when prefers-reduced-motion enabled2022-03-01T13:02:50+00:00ubq323ubq323@ubq323.website2022-03-01T13:02:50+00:00urn:sha1:b96542d91a7fb8ce6c4275b97f72b90c5227d6f3make posts in "private" subforums not visible through search or user pages2022-02-25T19:19:58+00:00ubq323ubq323@ubq323.website2022-02-25T19:19:58+00:00urn:sha1:60244846f4318e47747fc9f6ed342a765919dc20
subforums are considered "private" if the p_view_forum permission
is denied to the 'other' role in that forum. this doesn't consider
inheritance: if a forum doesn't have an 'other' role then it is
considered "public" (!!!). since inheritance is probably going
to be removed soon anyway, and since we currently only have
one "private" subforum, i think this is acceptable.
also note that posts in "private" subforums are hidden in
user pages and in search results to everyone, even people
who do have access to the subforum in question. again, since
the permissions logic is probably going to be changed, i don't
think it's worth implementing actual permission checks here with
the current (confusing, somewhat broken) permissions system.
add repo location to readme2022-02-25T18:16:25+00:00ubq323ubq323@ubq323.website2022-02-25T17:53:13+00:00urn:sha1:44f08e3a7b01298150b149893703189e5930ad99add better error handling to webhook sending2022-02-25T18:16:25+00:00ubq323ubq323@ubq323.website2022-02-25T17:51:01+00:00urn:sha1:db885a449440a187e9dd476d07b799e5cd479cd4
this fixes the bug where you get a 500 when trying to send a webhook
about a thing with a very long title, for example