Remove phone property from schema.

This makes the phone property inaccessible. We don't need or use the
phone. See https://issues.roundup-tracker.org/issue2551082.

Author: rouilj

website/issues/html/user.help-search.html

@@ -45,11 +45,6 @@
   <td metal:use-macro="search_input"><input type=text></td>
 </tr>
 
-<tr tal:define="name string:phone; label string:Phone number">
-  <th metal:use-macro="th_label">Phone</th>
-  <td metal:use-macro="search_input"><input type=text></td>
-</tr>
-
 <tr tal:define="name string:roles;
                 onchange string:this.form.submit();
                 label string:Roles:"
@@ -68,7 +63,7 @@
     <input type="hidden" name="@action" value="search">
     <input type="submit" value="Search" i18n:attributes="value">
     <input type="reset">
-    <input type="hidden" value="username,realname,phone,organisation,roles" name="properties">
+    <input type="hidden" value="username,realname,organisation,roles" name="properties">
     <input type="text" name="@pagesize" id="sp-pagesize" value="25" size="2">
     <label for="sp-pagesize" i18n:translate="">Pagesize</label>
   </td>

website/issues/html/user.index.html

@@ -49,7 +49,6 @@
  <th i18n:translate="">Real name</th>
  <th i18n:translate="">Organisation</th>
  <th i18n:translate="">Email address</th>
- <th i18n:translate="">Phone number</th>
  <th tal:condition="context/is_edit_ok" i18n:translate="">Retire</th>
 </tr>
 <tal:block repeat="user batch">
@@ -61,7 +60,6 @@
  <td tal:content="python:user.realname.plain() or default">&nbsp;</td>
  <td tal:content="python:user.organisation.plain() or default">&nbsp;</td>
  <td tal:content="python:user.address.email() or default">&nbsp;</td>
- <td tal:content="python:user.phone.plain() or default">&nbsp;</td>
  <td tal:condition="context/is_edit_ok">
      <form style="padding:0" method="POST"
            tal:attributes="action string:user${user/id}">

website/issues/html/user.item.html

@@ -89,11 +89,6 @@
  </tr>
  </tal:if>
 
- <tr tal:define="name string:phone; label string:Phone; value context/phone">
-  <th metal:use-macro="th_label">Phone</th>
-  <td><input name="phone" metal:use-macro="normal_input"></td>
- </tr>
-
  <tr tal:define="name string:organisation; label string:Organisation; value context/organisation">
   <th metal:use-macro="th_label">Organisation</th>
   <td><input name="organisation" metal:use-macro="normal_input"></td>

website/issues/html/user.register.html

@@ -44,10 +44,6 @@
    <input name="roles" tal:attributes="value db/config/NEW_WEB_USER_ROLES">
   </td>
  </tr>
- <tr tal:condition="python:False">
-  <th i18n:translate="">Phone</th>
-  <td tal:content="structure context/phone/field">phone</td>
- </tr>
  <tr tal:condition="python:False">
   <th i18n:translate="">Organisation</th>
   <td tal:content="structure context/organisation/field">organisation</td>

website/issues/schema.py

@@ -80,7 +80,6 @@
              password=Password(),
              address=String(),
              realname=String(),
-             phone=String(),
              organisation=String(),
              alternate_addresses=String(),
              queries=Multilink('query'),
@@ -261,7 +260,7 @@ def may_edit_file(db, userid, itemid):
 
 # Allow Users and Developers to view most user properties.
 p =  db.security.addPermission(name='View', klass='user',
-   properties=('id', 'username', 'address', 'realname', 'phone',
+   properties=('id', 'username', 'address', 'realname',
          'organisation', 'alternate_addresses', 'timezone'))
 db.security.addPermissionToRole('User', p)
 db.security.addPermissionToRole('Developer', p)
@@ -289,7 +288,7 @@ def own_record(db, userid, itemid):
     description="User is allowed to edit their own user details",
     properties=('username', 'password',
                 'address', 'realname',
-                'phone', 'organisation',
+                'organisation',
                 'alternate_addresses',
                 'queries',
                 'timezone')) # Note: 'roles' excluded - users should not be able to edit their own roles.