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.
Created attachment 105126 [details] [review] Bug 25100: Add sys pref OPACSelfRegistrationHeader This patch adds a system prefernce called OPACSelfRegistrationHeader which allows librarians to add HTML above the self registration form TO TEST: 1. Apply patch and updatedatabase 2. Make sure self registration is turned on. 3. Search for the new system preference 'OPACSelfRegistrationHeader'. 4. Add some HTML to the field like <h1>TEST</h1> 5. Go to the self registration page and confirm you can see your HTML. 6. This HTML should not effect the OPAC patron modification page, go there and make sure this is the case.
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.
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.
(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
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.
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.
Lucas - I'm getting an error page when i go to Tools > News. https://snipboard.io/SvQroR.jpg
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.
Is this a duplicate of bug 19838? I'm asking because both have been worked on recently, but the options looks really similar.
(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 ***