Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix for GetUnread to include unread discussions without comments #1881

Closed
wants to merge 1 commit into from
Closed

Fix for GetUnread to include unread discussions without comments #1881

wants to merge 1 commit into from

Conversation

R-J
Copy link
Contributor

@R-J R-J commented Apr 28, 2014

GetUnread didn't show unread discussions without comments. First fix didn't respect permissions - thanks @peregrine-web for raising that issue

This fix includes unread discussions without comments and adds a permission check to the function

GetUnread didn't show unread discussions without comments. First fix (1ab2895) didn't respect permissions - thanks @peregrine for raising that issue (#1871)   
   
This fix includes unread discussions without comments and adds a permission check to the function
R-J referenced this pull request Apr 28, 2014
GetUnread was not showing new discussions without any comment. Fixed that.
@linc
Copy link
Contributor

linc commented Apr 28, 2014

Thanks! I am actually going to hold this for the first 2.1 patch because I need to test this and we're way past beta.

@R-J R-J changed the title Update DiscussionModels function GetUnread Fix for GetUnread to include unread discussions without comments Sep 21, 2014
@linc
Copy link
Contributor

linc commented Dec 27, 2014

To get this in, I'd need two things: the merge conflicts resolved (by merging 2.1 back into this PR) and to make sure the equivalent fix is in master so we don't have a regression for 2.3.

@linc linc added the Revisit label Dec 27, 2014
@R-J
Copy link
Contributor Author

R-J commented Dec 28, 2014

Sorry, I'm a git noob and I do not know how to merge something back into a PR. The code change is very small, shall I "simply" create a new PR against the current branch?

@linc
Copy link
Contributor

linc commented Jan 21, 2015

Oh, you just push the changes to the same branch. A pull request is not specific commits, it is branch-to-branch, so changes to the branch are auto-added.

@linc linc closed this Jan 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants