Bug 25100 - Add ability to add custom text to top of the Self registration Form
Summary: Add ability to add custom text to top of the Self registration Form
Status: RESOLVED DUPLICATE of bug 19838
Alias: None
Product: Koha
Classification: Unclassified
Component: OPAC (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Lucas Gass
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-09 15:46 UTC by Lisette Scheer
Modified: 2022-01-27 21:48 UTC (History)
6 users (show)

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


Attachments
Bug 25100: Add sys pref OPACSelfRegistrationHeader (5.57 KB, patch)
2020-05-19 22:34 UTC, Lucas Gass
Details | Diff | Splinter Review
Bug 25100: Add SelfRegistrationHEad content area to news (3.09 KB, patch)
2020-05-21 23:03 UTC, Lucas Gass
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Lisette Scheer 2020-04-09 15:46:29 UTC
It would be great if we could have a custom HTML setting for information at the top of the self registration field to make it easy for staff to add/edit information about how to follow up with their new card. 
We currently use jquery to add it, but it would be nice if it was a separate setting.
Comment 1 Lucas Gass 2020-05-19 22:34:18 UTC Comment hidden (obsolete)
Comment 2 Katrin Fischer 2020-05-20 06:20:41 UTC
Hi Lucas, I was wondering if this should go directly into the news editor so we don't have to move it later. Totally agree with the idea of a new customizable spot.
Comment 3 Lucas Gass 2020-05-21 23:03:19 UTC
Created attachment 105234 [details] [review]
Bug 25100: Add SelfRegistrationHEad content area to news

This patch adds a new news feature which allows librarians to add content above the self registration form
1. Apply patch
2. Make sure self registration is turned on.
3. Go to the Tools > News and create a New entry.
4. You should see a new location on of SelfRegistrationHead, select that option and create a new news item with some content.
5. Go to the self registration page and confirm you can see your content.
6. This should not effect the OPAC patron modification page, go there and make sure this is the case.
7. Test by only displaying this for certain branches and make sure it only shows up on those branches.
Comment 4 Lisette Scheer 2020-06-11 15:38:24 UTC
(In reply to Lucas Gass from comment #3)
> 7. Test by only displaying this for certain branches and make sure it only
> shows up on those branches.

I can't get it to show up only for certain branches on branch selection. 

Otherwise it works great. 
Lisette
Comment 5 Barbara Johnson 2020-07-17 17:18:47 UTC
I got the same results as Lisette.  Everything works great but when set to only display for certain branches the content did not show up.
Comment 6 Lucas Gass 2020-08-02 17:08:06 UTC
Hi Lisette and Barbara,

Thanks for testing. I think we should ignore step 7 "Test by only displaying this for certain branches and make sure it only shows up on those branches."

By nature the user registering is not logged on, therefore can't yet belong to any specific branch.
Comment 7 Barbara Johnson 2020-08-04 16:00:17 UTC
Lucas - I'm getting an error page when i go to Tools > News.  

https://snipboard.io/SvQroR.jpg
Comment 8 Owen Leonard 2020-08-13 16:03:30 UTC
I think the error may have been because of a conflict with the patch in the sandbox. I had to tweak it to get it to apply on master in my test system.

The branch selection question is an interesting one. Seems like you'd have to require that the news item always be defined as applying to "all libraries," but I don't know how you'd enforce it efficiently.

The other option is to output versions of the text from ALL libraries and switch visibility based on the library the user selects. The KohaNews plugin wasn't designed to provide this ability.
Comment 9 Caroline Cyr La Rose 2022-01-27 21:43:18 UTC
Is this a duplicate of bug 19838? I'm asking because both have been worked on recently, but the options looks really similar.
Comment 10 Lucas Gass 2022-01-27 21:48:29 UTC
(In reply to Caroline Cyr La Rose from comment #9)
> Is this a duplicate of bug 19838? I'm asking because both have been worked
> on recently, but the options looks really similar.

Indeed, it is.

*** This bug has been marked as a duplicate of bug 19838 ***