-
Notifications
You must be signed in to change notification settings - Fork 11
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
HTTP error 500 when flagging content #5
Comments
This is because entities are now fully classed objects and the THis PR makes a "flagging" a real classed entity. |
@jromine are you available to review and merge this PR please? Its holding up using Flag on Forums. |
@docwilmot there should be a patches.txt file in the repo with links to any
patches that need to be applied (and their respective issues).
No patch should ever hold up using a project on a site. Here's a post on
how to do it for drupal
http://www.jenlampton.com/blog/sustainable-development-workflow-patching
…On Oct 8, 2017 2:24 PM, "docwilmot" ***@***.***> wrote:
@jromine <https://github.com/jromine> are you available to review and
merge this PR please? Its holding up using Flag on Forums.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAYSR4J5Wp5wwn26dszcj_HvFRMp8dzEks5sqT1_gaJpZM4Lw_H->
.
|
@docwilmot I don't have an active Backdrop site to test with right now. If you want to remove me as maintainer in the README that's ok with me. |
OK @jromine I'll review the patches and merge them in if you dont mind then. |
Issue #5: HTTP error 500 when flagging content
Whenever I flag a node on forum.backdropcms.org I get a HTTP 500 error:
The text was updated successfully, but these errors were encountered: