www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (INFRA-9250) Self serve does not allow empty attributes to be populated
Date Thu, 19 Nov 2015 00:31:11 GMT

     [ https://issues.apache.org/jira/browse/INFRA-9250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Chris Lambertus resolved INFRA-9250.
    Resolution: Won't Fix

If an attribute is not editable on id.apache.org by the customer, it is either not meant to
be edited by the customer or is not currently used. This isn't something we have the bandwidth
to address, and should probably part of a larger discussion on account management. I'm closing
this ticket because it does not affect functionality; it is a cosmetic issue only. 

> Self serve does not allow empty attributes to be populated
> ----------------------------------------------------------
>                 Key: INFRA-9250
>                 URL: https://issues.apache.org/jira/browse/INFRA-9250
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>            Reporter: Sebb
>            Assignee: Tony Stevenson
> The self-serve app does not allow empty attributes to be populated.
> This is because of lines 258/259 in [1], where the field is set to disabled if the attribute
is not present in the values for the current record.
> A simple fix is to remove the lines.
> However, this then causes a problem, because empty fields are pre-populated with the
value "<not present>", which will get written to the attribute if the user does not
clear the fields first. This would be tedious and error-prone.
> Dropping the "<not present>" value does not work either, because the field is currently
only rendered if there is a value for it.
> The changedetails.html template needs to show at least one field for every supported
attribute whether it has an actual value or not.  
> For writable fields, one could use a field placeholder attribute [2] to show the "<not
present>" text. This would also be suitable for read-only fields.
> Whatever approach is taken, there needs to be a way to test the changes.
> Is there a test installation of the SelfServe app that can be used to check that the
page renders OK?
> [1] https://svn.apache.org/repos/infra/infrastructure/selfserve/trunk/lib/selfserve/__init__.py
> [2] http://www.w3schools.com/tags/att_input_placeholder.asp

This message was sent by Atlassian JIRA

View raw message