-
Notifications
You must be signed in to change notification settings - Fork 45
Conversation
*/ | ||
public function moveTopicToForum(Topic $topic, Forum $forum) | ||
{ | ||
return $this->decoratedRepository->moveTopicToForum($topic, $forum); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This needs to update the cache (simply call forget
for now), otherwise the other functions will return invalid data.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok cool, thanks.
Some other things I've noticed:
That's what I found while playing with the code a bit. Sorry if you're already aware of some of them ;) |
@JN-Jones Thanks man! I'm not really worrying about the front-end tbh, it's not my area of expertise so I'm kinda making it work and not look horrendous on the basis that we will create separate issues to improve the front-end. What do you think?
Yup, I've thought about this but I don't think that blocks this PR, as above I think creating a new issue to improve the front-end is the best course of action once this is merged.
Sure, don't think that is an issue for this PR though.
Yup, will add to #45 for future PRs.
Thanks, will fix that.
Happy to this in this PR. Can the permissions system do this right now? Or will it have to wait?
What are the steps to reproduce?
Actually I think we can be smarter and provide an autocomplete type-ahead feature for this. For now though I'd like to merge as is and tackle this in a separate issue / PR if that's ok?
I'll have a look at the clear selection link in this PR, thanks.
Agreed, would also like to tackle this in a separate PR. The aim is to provide basic working inline moderation that we can iterate on with future PRs and issues. Keen to avoid a long-running branch that falls foul of conflicts over time. @JN-Jones let me know what your thoughts are on what I've said, then I can put together a list of things to address in this PR and what we're happy to leave for future PRs. I will happily create the issues for future work so we do not forget the good ideas in this PR. |
I'm fine with seperate issues/PRs, did the same already with my PRs. About styles: Feel free to add them on trello: https://trello.com/b/NFeiW7em/mybb-2-0-styles
Yes. The permissions system has three types of permissions: yes/no where yes overrides no and never which is never overwritten. Simply add a new permission related to forums, 0 as default value and then add the admin role with value 1.
I've selected one post, selected the second, clicked on the link and nothing happened. |
Thanks buddy, I'll add a to-do list to the PR tonight and work through it this week. |
About the merge link:
(Un)approving any post will also change the status of the topic. |
@@ -209,6 +210,10 @@ public function reply($slug, $id, Request $request, $postId = null) | |||
throw new TopicNotFoundException; | |||
} | |||
|
|||
if ($topic->closed) { | |||
throw new \Exception("This topic has been closed"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be translatable and a real exception class instead of throwing a basic exception
The file headers need to be updated now ;) |
Closing for refurbishment. |
This PR contains the WIP of inline moderation for posts and topics. See the issue here #45 for the tools that it has implemented.
Would like some QA and feedback whilst I tidy things up, then I'm going to open a PR with a view to being merged. Once this work is merged I will crack on with the rest of the items in the above issue.