Closed (works as designed)
Project:
@font-your-face
Version:
7.x-2.6
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Dec 2012 at 16:12 UTC
Updated:
7 Jan 2013 at 18:22 UTC
Steps to reproduce:
Probably not a huge issue but was kind of like a "huh?" moment for me today as I was testing out different fonts.
Comments
Comment #1
Drave Robber commentedI could not reproduce this following these steps. 'Details' and 'Preview' are just collapsible fieldsets of a sort standard to Drupal, and fontyourface_ui.module does not do anything that could turn them not collapsible (or, in this case, not expandable).
Are you using the default admin theme, Seven?
Are you using overlay? (If yes, does the problem show up if overlay is disabled?)
Comment #2
Courtney.B commentedI am using the default admin theme. I am not using the overlay.
Tonight, I'll set up a clean environment and run the steps I listed above to see if I get the problem there. It could just be some sort of issue with one of the modules I've installed on in the development environment. I will report back my findings on the clean environment test.
Thanks for the prompt response! I will investigate further and let you know what I find.
Comment #3
Courtney.B commentedThis message is more for my sake, for when I check back with this issue when I'm ready to run tests on a clean environment.
I need to test Font Your Face first without the jQuery Update and again after I've updated everything to match the version I'm running in my development environment. This is jQuery 1.7.1 on both back/front end with jquery update version 7.x-2.3-alpha1+0-dev.
I have a hunch that this might be the cause of my AJAX-related issues with this module. I'm not 100% certain though because I don't know what sort of role AJAX and jQuery have with each other. It's the best guess I've got so far so that is where I will start my testing.
If you have any other suggestions or do not think this is a good starting point, please let me know. I'm changing the status "postponed (maintainer needs more info)" as the maintainer needs more information from me before assisting with some sort of solution.
Comment #4
Drave Robber commentedSuspiciously similar forum topic: One particular fieldset won't render clickable anymore
There might be something global to this, after all.
Comment #5
Courtney.B commentedChanging to closed (works as designed) because my issue stemmed from using jQuery update. Unfortunately, I do not have time to troubleshoot the issue. I had to revert back to the version Drupal ships with and doing so fixed my above issue.
Thanks Drave for being so responsive!