Bug 17321 - Fix "Your personal details" in OPAC
Summary: Fix "Your personal details" in OPAC
Status: RESOLVED DUPLICATE of bug 17235
Alias: None
Product: Koha
Classification: Unclassified
Component: OPAC (show other bugs)
Version: 16.05
Hardware: All All
: P5 - low major (vote)
Assignee: Owen Leonard
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-20 06:52 UTC by Magnus Enger
Modified: 2017-04-20 18:45 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Magnus Enger 2016-09-20 06:52:38 UTC
Visiting <opac>/cgi-bin/koha/opac-memberentry.pl gives a 500 error:

  Global symbol "$borrower" requires explicit package name at /usr/share/koha/opac/cgi-bin/opac/opac-memberentry.pl line 190.
  Execution of /usr/share/koha/opac/cgi-bin/opac/opac-memberentry.pl aborted due to compilation errors.

This is on the latest 16.05.x packages.

The actual line is:

  %borrower = ( %$borrower, %borrower );

Looks like adding 

  my $borrower = GetMember( borrowernumber => $borrowernumber );

above line 190 fixes it. 

Can anyone confirm this?
Comment 1 Jacek Ablewicz 2016-09-20 07:23:34 UTC
Looks like a duplicate of Bug 17235 - there is a patch for this issue in Bug 16996, I think it is already pushed (or soon will be) to the 16.05.x git branch?
Comment 2 Magnus Enger 2016-09-20 07:44:43 UTC

*** This bug has been marked as a duplicate of bug 17235 ***
Comment 3 Fred 2017-04-20 17:56:59 UTC
After performing the registration from the OPAC I report error 500, I currently have version 16.11.06, in Debian 8.
Please someone can give me the solution
Comment 4 Magnus Enger 2017-04-20 18:45:34 UTC
(In reply to Fred from comment #3)
> After performing the registration from the OPAC I report error 500, I
> currently have version 16.11.06, in Debian 8.
> Please someone can give me the solution

Is it similar to bug 16996?