Bug 13505 - No advanced constraints for subfields $t
Summary: No advanced constraints for subfields $t
Status: CLOSED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: System Administration (show other bugs)
Version: 3.18
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-01 18:20 UTC by Pablo AB
Modified: 2017-06-14 22:11 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
Example of bug for subfield 505$t on serials framework (18.94 KB, image/jpeg)
2015-01-01 18:20 UTC, Pablo AB
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pablo AB 2015-01-01 18:20:49 UTC
Created attachment 34854 [details]
Example of bug for subfield 505$t on serials framework

On Home › Administration › MARC frameworks › AnyFramework, on any field, for subfield $t we can't open/expand Advanced constraints:
http://myKoha/cgi-bin/koha/admin/marc_subfields_structure.pl?op=add_form&tagfield=710&frameworkcode=SER#advt
I suspected a Javascript issue, but Firefox (v34.0) console only throw «Empty string passed to getElementById()». Chromium (v39.0.2171.65 Ubuntu 14.10) with same issue. 
Koha 3.18.2.
Comment 1 Katrin Fischer 2015-01-01 18:33:13 UTC
Hi Pablo,
I have seen this recently - For me it starts working when I deactivate Adblock Plus. Hope this doesn't sound too weird :)
Comment 2 Pablo AB 2015-02-20 17:12:55 UTC
Thanks Katrin!

I confirm disabling Adblock solves the problem. Is a false positive from ABP, a filter rule filtering "###advt", as commented on closed (equivalent?) bug #11898, where  Fridolin SOMERS consider this is an ABP issue, but the URL where he report it now gives 404 (domain a 403). Maybe following this instructions[0] and crossing fingers solve the problems.

[0] https://adblockplus.org/en/getting_started#false-positives
Comment 3 Owen Leonard 2016-06-21 13:34:03 UTC
Since this bug is caused by a browser addon rather than Koha itself I think this can be considered resolved.