I'm getting an error on Drupal's available updates page:
Notice: Undefined index: fusion_core in theme_update_report() (line 200 of ...drupal-7.8/modules/update/update.report.inc).

I think this in since I updated to Fusion 2.x

This seems to verify this:
version mixup

I know that the version of fusion core I have installed is 2.x.

On my themes admin page, it lists fusion_starter, fusion_starter_lite (both at version 2.x) and my subtheme listed at version 1.0 alpha2. Fusion core is not listed.

CommentFileSizeAuthor
fusion_version_mixup.png8.52 KBmshepherd

Comments

esmerel’s picture

What 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?

mshepherd’s picture

esmerel - 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:

name = Illuminate
description = A template theme by Illuminate ICT, based on fusion_core.
base theme = fusion_core
core = 7.x
engine = phptemplate

stylesheets[all][] = main.css

fusion[api] = 2
fusion[directory] = skins

...

; Information added by drupal.org packaging script on 2011-08-03
version = "7.x-1.0-alpha2"
core = "7.x"
project = "fusion"
datestamp = "1312385816"

I didn't touch the text at the end as it's labelled as being added by the packaging script.

sheena_d’s picture

Looks 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:

version = "7.x-2.0-alpha1"

and we will make a new release with the correct version information in the .info file.

mshepherd’s picture

If 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

mshepherd’s picture

I 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.

mshepherd’s picture

Title: Version mixup after upgrade to fusion 2 » Undefined index error on available updates page with fusion 2

Just 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

aquariumtap’s picture

Hi @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:

; Information added by drupal.org packaging script on 2011-08-03
version = "7.x-1.0-alpha2"
core = "7.x"
project = "fusion"
datestamp = "1312385816"

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?

mshepherd’s picture

Hi @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

mshepherd’s picture

Hi 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

drupert55’s picture

FYI - Error message still exists in 7.x-2.x-dev (October 18).

mshepherd’s picture

@aquariumtap,

Renaming starter pack info files to *info.txt may have a few negative effects:

  • it will add another thing for the themer to do before their subtheme is active
  • starter pack subthemes will be unusable before a user changes the name of the info file [using a starter pack subtheme in place may not be the documented route, but some may use them that way]
  • future fusion_core updates may compromise the theme if someone has used a starter pack subtheme in place [although obviously this would happen anyway]

I'd vote for removing hidden = TRUE from fusion_core.info until #986888: Undefined index warning in "Available Updates List" with hidden=TRUE base themes is resolved.

sheena_d’s picture

I think @mshepherd makes a good point. i vote for removing hidden=TRUE for Fusion Core until #986888 is fixed.

sheena_d’s picture

hidden = 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:

Notice: Undefined index: base theme in system_find_base_themes() (line 2645 of /Users/sheena/Sites/drupal_commerce/modules/system/system.module).

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.

aquariumtap’s picture

Status: Active » Closed (won't fix)

Fusion 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.

  • Commit 512b5e5 on master, 7.x-2.x by aquariumtap:
    Issue #1322092: Undefined index warning in "Available Updates List" with...