• Resolved abinternet

    (@abinternet)


    I did send following query directly via your own website last week but as I’ve not yet received your response I hope you’ll forgive me for posting it here……

    I’m an administrator of the website http://www.guardian-angels.es which is running WordPress version 4.5.2 with your Participants Database plugin Version: 1.6.2.8. Up until the end of April one of our site Editors used to log in and change the automatically allocated “Private ID” which the site automatically allocates to new Single Parents who register with the site (as at http://guardian-angels.es/new/en/single-parent-registration/ ). She did this to change the Private_ID from the randomly numbered ID which is automatically created, to a meaningful ID number for each member of the site. As a result we have each previous member set with a Private ID in format GAxyx, where xyz is a 3 digit number which we add one to for each new member. So currently we have Private IDs from GA001 to GA115.

    On May 10th and May 24th two new members signed up, but when we now try to edit their Private ID numbers it does not allow us to do so, as it states that field is “Read only”. In fact I see that even at Admin level when I now try to edit the details of any member, all five of the Record Info fields at the foot of the page (“Private ID”, “Date Recorded”, “Date Updated” and “Last Accessed”) are ALL now shown as “Read only”. If I go into “Manage Database Fields” and then to the tab headed “Record Info Fields” there is no read-only checkbox available to me, so I cannot change this setting.

    Do you know what’s happened (e.g. Did you make changes affecting this in a recent update?) and is there a way I can fix this so we can again edit the Private ID field?

    Many thanks
    Gareth

    https://wordpress.org/plugins/participants-database/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author xnau webdesign

    (@xnau)

    Yes, I changed the the private_id field to be read-only, it was causing problems in some cases when it was edited. You can make it editable again by editing the “edit_participants.php” file on line 112, you’ll find:

    if (!Participants_Db::current_user_has_plugin_role('editor', 'readonly access') || $column->name === 'private_id') {

    change that to:

    if (!Participants_Db::current_user_has_plugin_role('editor', 'readonly access') ) {

    Thread Starter abinternet

    (@abinternet)

    OK, thanks.

    I did as noted above, @xnau, and when I click “apply,” the private_id changes back to its original value.

    I haven’t updated to the new version of Participants Database just released. Any idea why the change wouldn’t stick?

    Plugin Author xnau webdesign

    (@xnau)

    As of version 1.7, the correct way to do this is to use a filter:

    add_filter('pdb-private_id_is_read_only', function () { return false;});

    So there is no need to edit the plugin files, this can be placed in your theme functions file..

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘No longer able to update the Private ID field’ is closed to new replies.