Closed (fixed)
Project:
Bootstrap
Version:
8.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
26 Aug 2015 at 21:49 UTC
Updated:
10 Oct 2015 at 17:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
rodrigoaguileraI worked around calling the the old preprocess function from the new one.
Comment #3
markhalliwellPretty sure this is a duplicate of this related issue.
Comment #4
rodrigoaguileraI still don't see any text inside the button element with the latest commit.
I tested on my site and a quick https://simplytest.me/ instance.
Comment #5
markhalliwellHm. Ok. It still sounds like it's related to this D8 issue though.
I'll have to step through the registry/theme invocation in more detail. It may be an issue with the registry alter (not picking up the file for preprocess suggestions?).
The ultimate reason I closed this is because the patch in #2 should not be necessary. Preprocess functions are accumulative (meaning the base preprocess should always run first) and this patch would essentially "double" preprocess a button.
Comment #6
markhalliwellEssentially, the majority of _bootstrap_process_theme_registry_suggestions() needs to come out... or at the very least severely refactored so just adds in the discovered base theme hook files.
edit: also, please keep in mind that the code in registry.inc is still heavily based on 7.x.
Comment #8
neardark commentedI was seeing this also, so I've merged this which does fix the issue. Guess that preprocess wasn't being fired in the past...
Comment #10
neardark commentedReverting this commit until the issue that caused button labels can be addressed.
Comment #11
markhalliwellI will try and cleanup the registry.inc file this weekend.
Comment #12
marcingy commentedI have traced the issue and have suggesting working once again there maybe some clean up we could do the issue was introduced by #939462: Specific preprocess functions for theme hook suggestions are not invoked because of changes to how the registry is build. The fix just updates the bootstrap module but I was able to also fix it by changing
Too
This off course means that we lose the ability fully alter the registry and brings into question do we need an alter.
Comment #13
slashrsm commentedSolution looks OK and it seems to fix the issue. When reviewing this I thought how much nicer would this be if we'd extent core's registry service and add bootstrap's stuff there. This will give us access to protected functions like
postProcessExtension()etc.I am aware this is module material, but so complex registry alter probably belongs there anyway.
Comment #14
marcingy commentedFixes a notice at install time
Comment #16
neardark commentedMerged.