Bug 33175 - When reporting a problem while not logged in, the problematic page is set to opac-reportproblem.pl
Summary: When reporting a problem while not logged in, the problematic page is set to ...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: OPAC (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Owen Leonard
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-08 19:53 UTC by Caroline Cyr La Rose
Modified: 2023-04-12 18:43 UTC (History)
1 user (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 Caroline Cyr La Rose 2023-03-08 19:53:20 UTC
To reproduce:

1. Turn on OPACReportProblem
2. Go to the OPAC - DO NOT log in at this point, log out if you are
3. Click "Report a problem" at the bottom of the page (opac-main.pl)
4. It will ask you to log in, log in
   --> Problem found on page is /cgi-bin/koha/opac-reportproblem.pl
5. Click the Koha logo to go back to the main page
6. Click "Report a problem" again
   --> Problem found on page is /cgi-bin/koha/opac-main.pl

It should probably remember which page the patron was on when they clicked the link to report a problem?
Comment 1 David Nind 2023-04-12 18:43:50 UTC
For me, Koha is recording the OPAC home page (/) as the problematic page, irrespective of:
- whether I'm logged in or not
- irrespective of the page I'm on

For example:
1. Log out of the OPAC
2. Go to a detail page for a record (for example http://127.0.0.1:8080/cgi-bin/koha/opac-detail.pl?biblionumber=262) or any other page (except the OPAC home page)
3. Click on report a problem in the footer
4. Prompted to log in
5. Log in
6. For the form, / is shown for "Problem found on page"
7. Enter some details and submit
8. In the staff interface, the problem page is reported as the OPAC home page

Maybe this feature requires some other bugs to be applied, or that aren't in master yet?

Or maybe I'm misunderstanding and getting confused with bug 31028 ...