Closed (fixed)
Project:
Book Title Override
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
27 Apr 2015 at 20:42 UTC
Updated:
29 Jul 2015 at 13:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
osopolarComment #2
btopro commentedpinging mark to test, makes sense.
Comment #3
mmilutinovic1313 commentedDidn't break anything, but saving with an override doesn't do anything and the box becomes unchecked the next time you go into the Book via edit.
Comment #4
btopro commentedthat sure sounds like something broke...
Comment #5
btopro commentedalso what theme / jquery stuff are you using? there have been some conflicts reported there in the past unfortunately
Comment #6
mmilutinovic1313 commentedI noticed this issue in both patches - That's why I assume it is not related, but I will investigate further
Comment #7
mmilutinovic1313 commentedAfter further examination, Patch is Verified and working!
Further note: Settings for overrides will only save if the book is in an outline. I don't know if it would be possible, useful, or too confusing to have the override save if the book was not yet in an outline (just as kind of a meta property).
Comment #8
btopro commentedit can't save unless its in an outline cause it doesn't have a menu item to associate to. do a PR against the github mirror so we can get this in
Comment #9
mmilutinovic1313 commentedWhich branch for the PR to compare to? And do you want me to apply the patch before I do the PR?
Comment #10
btopro commented7.x-1.x
Comment #11
osopolarI am a bit confused about the changes in the last Release 7.x-1.1, where the file book_title_override.js was replaced by book_title_override_ops.js (with a strange namespace
Drupal.outline_designer_ops.book_title_override), but I guess this issue is obsolete now, isn't it?Comment #12
btopro commentedso book_title_override was replaced by the core form API function to show and hide based on a checkbox.
The ops file you are referencing should have always been there and is only utilized as part of the https://www.drupal.org/project/outline_designer integration
Also, yes, this thread is most likely resolved since we're using the core method of solving this now which does use behaviors
Comment #13
btopro commentedthis was fixed in 1.1 by implementing the core method of opening