Closed (won't fix)
Project:
Fusion
Version:
7.x-2.0-alpha1
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
26 Oct 2011 at 11:04 UTC
Updated:
15 Apr 2014 at 16:35 UTC
Jump to comment: Most recent

Comments
Comment #1
esmerel commentedWhat did you use to update/upgrade (manually, drush, etc)?
What does the .info file for your subtheme say for fusion[api] ?
You may need to re-extract fusion core if it's not there; doublecheck your installation and make sure it's copied to the correct place?
Comment #2
mshepherd commentedesmerel - Thank you for your reply.
I documented the process I used at http://drupal.org/node/1313268#comment-5140226
The version of fusion I'm using is definitely 2.
My info file:
I didn't touch the text at the end as it's labelled as being added by the packaging script.
Comment #3
sheena_d commentedLooks like we forgot to remove the old version information before we rolled the 2.x release of Fusion. You can safely edit that line in the .info file for the time being, to read:
and we will make a new release with the correct version information in the .info file.
Comment #4
mshepherd commentedIf I can safely edit that's good, I think your code is fine.
I made my subtheme with fusion 1.x - just didn't know I had to change that line. I'll do so right now and report back.
Many thanks
Comment #5
mshepherd commentedI changed my subtheme's info file as per your suggestion above - and then cleared all caches. Now, Fusion is correctly listed as up to date, but I still get that undefined index error.
Comment #6
mshepherd commentedJust to follow up on this, I've just done a fresh Drupal install (7.9) and installed Fusion Core (2) and the Fusion Accelerator module. I still get the undefined index error above. I've changed the title of this post as it looks like my other problem (now solved - thanks) was a red herring.
Many thanks for your help
Comment #7
aquariumtap commentedHi @mshepherd, thanks for your help with testing!
Fusion Core is no longer listed on the themes page. It's now hidden, since it should never be used as the default/active theme.
It looks like the info file you posted is for your Illuminate sub-theme, is that right? In that case, it shouldn't have these lines at all:
Those lines apply only to Fusion core, but @sheena_d and I figured out it's being added into our starter kits as well. I'll need to rename those starter kit info files from fusion_starter.info to fusion_starter.info.txt to get around the problem.
Could you delete those .info lines entirely, clear cache and let me know if you still get the undefined index error?
Comment #8
mshepherd commentedHi @aquariumtap
I've removed those lines from the bottom of my subtheme's .info file, cleared cache and the Undefined index error is now gone. Like magic!
However, I've noticed that there's now no indication that Drupal checks for Fusion Core updates when it checks for available updates. It's not listed anymore on the Available Updates page? Seems odd to me.
Thanks for your support,
Matthew
Comment #9
mshepherd commentedHi Again,
I think this relates to #986888: Undefined index warning in "Available Updates List" with hidden=TRUE base themes
At least that may account for the error.
I'm not sure why Fusion Core doesn't get listed on the Available Updates page.
Matthew
Comment #10
drupert55 commentedFYI - Error message still exists in 7.x-2.x-dev (October 18).
Comment #11
mshepherd commented@aquariumtap,
Renaming starter pack info files to *info.txt may have a few negative effects:
I'd vote for removing
hidden = TRUEfrom fusion_core.info until #986888: Undefined index warning in "Available Updates List" with hidden=TRUE base themes is resolved.Comment #12
sheena_d commentedI think @mshepherd makes a good point. i vote for removing hidden=TRUE for Fusion Core until #986888 is fixed.
Comment #13
sheena_d commentedhidden = TRUE is removed in the current dev version (http://drupal.org/commitlog/commit/11150/512b5e5a343661feb0704745dde717e...)
However, if I enable Fusion core as the default theme, I get the undefined index error:
Of course, the only reason I would have Fusion core set as the default is for testing Fusion Core itself, but I want to bring this up so we can make sure that this error persisting is not somehow evidence that we have not addressed the actual problem.
Comment #14
aquariumtap commentedFusion core now is set to hidden = FALSE, to avoid issue #986888: Undefined index warning in "Available Updates List" with hidden=TRUE base themes in core.