Bug 4467 - messaging defaults not on add child
Summary: messaging defaults not on add child
Status: RESOLVED DUPLICATE of bug 7660
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal
Assignee: Galen Charlton
QA Contact: Bugs List
URL: cgi-bin/koha/members/memberentry.pl?o...
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-07 04:10 UTC by Nicole C. Engard
Modified: 2019-04-28 23:27 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:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Cormack 2010-05-21 01:27:32 UTC


---- Reported by nengard@gmail.com 2010-05-07 16:10:39 ----

I have set the defaults for messaging for my 'child' patron type. Messaging defaults don't show when adding child from parent "add child" button - even though messaging rules are set and work when adding child separately from parent



--- Bug imported by chris@bigballofwax.co.nz 2010-05-21 01:27 UTC  ---

This bug was previously known as _bug_ 4467 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=4467

Actual time not defined. Setting to 0.0
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Nicole C. Engard 2010-06-02 23:08:59 UTC
This is because the URL does not have a categorycode - instead it has a category type ... not sure how to fix it but hope that helps some.
Comment 2 Owen Leonard 2010-06-04 15:34:07 UTC
You can't pass a category to the add child screen because the category is unknown at that stage. The form passes the category type only, and the add child entry form automatically preselects the first available category under the 'C' category type. Theoretically, there could be any number of sub-categories to the "Child" category type.

In fact the only time when this works properly is when you begin patron creation by choosing a specific patron category. What if you start by creating a patron with one category but you change your mind and instead choose a different category from the drop-down menu on the patron entry form? You'll still have the defaults from the patron category you started with.

The only way around it would be to create some method for refreshing the messaging defaults with values based on the currently-selected patron category. I can picture some kind of AJAX-based method for this, but I don't see how you can fix this simply.
Comment 3 Nicole C. Engard 2010-06-04 15:47:12 UTC
If it was simple I would have done it :) The problem is that while you and I understand why it isn't working - those using it don't understand.  And they may assume that the defaults are selected and not see that this is not the case.  So maybe a ajax refresh - or some other note to make it clear that the messaging defaults don't work when clicking 'add child'
Comment 4 Katrin Fischer 2013-04-13 19:08:02 UTC
Maybe this could work if we changed the behaviour of the 'add child' button to make you select a child patron category when clicking it?
Comment 5 Katrin Fischer 2019-04-28 23:27:37 UTC

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