Closed (fixed)
Project:
Answers
Version:
7.x-4.0-rc1
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
25 Feb 2015 at 03:37 UTC
Updated:
15 Dec 2018 at 03:19 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
chipcleary commentedAh, great timing. I am just working on improved theming for answers. Just released a first version. I like the idea ... thanks! Will include this in a revision to that.
Note, I'm putting it in a submodule called "answers_theme" to not interfere with people who have already used the answers module in their sites.
Comment #3
chipcleary commentedPatch attached and committed to 7.x-4.x-dev.
Comment #4
JacksonBison commentedI'm a bit of a hack, so admittingly don't exactly know what I'm doing... I tried the patch on an existing installation of Answers, which caused all kinds of issues sitewide, but I assume that's why you said you're putting it in a theme sub-module.
Should the patch work if I delete all the answers content I have on the site? There's only test content currently...
Comment #5
chipcleary commentedHmmm ... you shouldn't have to delete any content.
A couple of questions:
Comment #6
JacksonBison commentedI tried again, applying the patch to answers.module in 7.x-4.0-rc1.
Cron run and Cache flush results in WSOD
Patch results in:
1. Some strange changes to the width of the site (sort of hard to explain, but it's sort of shrunk)
2. Existing font awesome icons either being replaced, or shifted vertically
3. Vertical shift in site content - eveything's dropped by about 3cm, leaving a blank area across the screen
4. The following error messages
Comment #7
chipcleary commentedHmmm ... not sure what is happening. Is there a way you can share what else you are doing with your site so I could try to replicate? Not sure whether you've developed a module you could share.
If not, I could focus on two ideas ... but I'm not confident in either of them:
- You are using Font Awesome Icons separately. My css defines a "FontAwesome" ... I wonder if that somehow contradicts what your code already does
- I *think* I've created all "answers-specific" css which shouldn't affect anything else on the site ... but I can check whether every css definition is prefaced by a class that is "answers-specific"
Just to check. If you disable Answers, does the error go away?
Comment #9
chipcleary commentedHere's a patch that addresses the two hypotheses I list above. I've also updated 7.x-4.x-dev with these changes, as they're good ideas in any case even if the bug lies elsewhere.
Comment #10
JacksonBison commentedIn response to #7, yes I do have FontAwesome icons already in my theme, so this would have been part of the problem. Disabling the Answers module fixed the issue. I couldn't find any other CSS that may have conflicted with what you put together (although that doesn't mean there isn't any - I just couldn't find it...)
With reference to #9, for whatever reason, I could not apply the patch (I tried on top of the other patch). That being said, the new dev release seems to work fine without effecting anything else on the site.
Comment #11
chipcleary commentedGood news
Comment #12
JacksonBison commentedJust an FYI - I'm using the Answers_Theme (sub) module with this release (7.x-4.0-rc1) rather than the dev release, and it works fine so far...
Comment #13
bluegeek9 commented