I have a subtheme based on fusion 6.x-1.12. I just updated the core fusion theme to 6.x-1.13, I removed the old fusion_core folder and copied the new one.
But the status report still asking me to update to 6.x-1.13 for security reasons.
What Should I do ? I run cron , clear cache but still have the same message error, should I also override my subtheme files?

Comments

esmerel’s picture

Status: Active » Fixed

Did you update just fusion_core? You also need to remove the other files (including the other two subthemes) and update; that should take care of it.

kalilo’s picture

Thank you, I have just two folders in the server:
fusion_starter and fusion_core, I have never uploaded fusion_starter_lite.
So, if I understand, I should override also all my fusion_starter files. and what will happend to The css files in my subtheme?

sheena_d’s picture

If you created a Fusion sub-theme, you should have duplicated the fusion Starter folder outside of the Fusion directory and renamed the folder and included files to match the name of your new theme, so completely deleting the entire Fusion directory should have no effect on your sub theme. See our documentation for more details: http://fusiondrupalthemes.com/support/theme-developers/subtheming-quicks...

If you edited Fusion Starter in place, then you will need to remove the auto-generated packing script from the .info file. It looks something like this:

; Information added by drupal.org packaging script on 2012-03-28
version = "6.x-1.13"
core = "6.x"
project = "fusion"
datestamp = "1332949846"
kalilo’s picture

I have renamed the folder fusion_starter, and place it beside the fusion_core folder, I didn’t uploaded the entire fusion folder, but only those two subfolders: fusion_starter and fusion_core .
Now I just override my subtheme.info file with the new one. Rename my css file. And all is fine.
I don’t know if this was the correct way to create a subtheme. I hope it is.
Thank you a lot , You support here or in TopNotchThemes is always the best.

chien_fu’s picture

I just updated the whole 'fusion' theme folder including core, starter and starter_lite. The subtheme I'm using is acquia_prosper and it is all up to date so I didn't do anything with that. Yet the fusion theme still says it is out of date in the available updates page.

sheena_d’s picture

@chien_fu: have you cleared the site's cache?

chien_fu’s picture

I have flushed all the caches, yes. Still says needs updating..

esmerel’s picture

Are you sure you don't have another copy of fusion somewhere? Like in the core themes directory? This is the most common cause of 'failure to update' errors. Doublecheck your install, all of it (tedious!) for another copy of fusion, just in case.

chien_fu’s picture

Actually... despite what I now know to be best practice, I've installed all modules and themes in the core directories as opposed to sites/all/...
So there is only one install of it.
That said, the site in question is a development site and is a complete mirror of my live site.. nothing is shared, it's a completely different database and drupal install, but it is running on the same server... Not sure if that would have anything to do with it, but my live site also has the fusion theme and has not been updated. The reason for having the dev site, obviously, is to make sure all upgrades and fixes actually work before performing them on the live site.

I don't know what other information I can offer, please let me know if there's anything you need to know to better understand what's going on.

THANKS!

crutch’s picture

Priority: Normal » Minor
Status: Fixed » Needs review

subscribe, same issue, still shows not secure, template.php is in original location only, file structure is accurate a separated from custom theme.

However, when looking at my custom theme.info file this tells drupal that it is still old. I copied lines 65-69 from the new fusion_starter.info file and pasted in custom theme.info and this forced the update status as updated.

crutch’s picture

Status: Needs review » Fixed

solution @ #3

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.