Postponed (maintainer needs more info)
Project:
Mark-a-Spot
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
8 Dec 2015 at 11:12 UTC
Updated:
18 Feb 2016 at 04:28 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
tormiSo you log in, report an issue and it will be assigned to anonymous user?
Comment #3
nikunjkotechaYes, I checked even in default install. Also the field for email must be pre-filled for logged in users which is not the case.
Comment #4
markaspot commentedSorry, but I can not reproduce that. So you did change the selection criteria for the node_edit page to another role than "authenticated user"? I did that and registered another user. I successfully reported as user with a prefilled e-mail address, please compare screenshots attached.
Comment #5
nikunjkotechaI am talking about the popup that comes up when we click on the blue marker. Popup uses the services api "georeport/v2/requests.json" to create the request. Issue is in the popup.
Comment #6
markaspot commentedThis concerns the Mark-a-Spot Open311 Client module. Posting as anonymous user is by design. Please check the Georeport v2 specification for that.
Comment #7
nikunjkotechaIs there any possibility to include the account_id optional parameter mentioned in the wiki http://wiki.open311.org/GeoReport_v2/?
at-least for the web interface in the site, I understand it has been designed that way but it is not making sense - I am logged in to the site, I am using a feature available on the site, there is no description about hiding the identity and still it is reporting as anonymous
Comment #8
markaspot commentedI agree, adding the account_id property would definitely make sense. The report would then be impersonated to the user? We should discuss security concerns. Posting as an administrative user (or even User 1) should be prohibited.