Closed (duplicate)
Project:
Drupal core
Version:
7.0
Component:
update.module
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Jan 2011 at 09:12 UTC
Updated:
13 Jan 2011 at 16:08 UTC
Jump to comment: Most recent file
Comments
Comment #1
Gluhm commentedForgot screenshot.
Comment #2
nerilka commentedI have the same problem. Each time I update omega, a folder omega is created inside the folder omega, etc...
Comment #3
himerus commentedI've not seen this.... but ALSO, not used the "automated" update via the administrative interface.
I use drush to update locally and on my server, and all works fine.
I'm willing to bet (but I'll have to investigate) that this is a core issue with that, and the way that in the root Omega folder (I'm not the only one to do it this way) there are no .info files, and only subfolders essentially with the themes in there. (that was done for a reason)
I'll investigate and see what I can find...
Comment #4
himerus commentedWould it be possible for you to perform a test for me? I don't have any of my sites setup to use FTP access, and can't test the update feature locally.
I think it may be because of the way Omega organizing the directory, and I'd like you to test another theme that uses a similar method. Fusion & Genesis don't have anything other than dev releases, so can't test those, but I think testing Adaptive theme the same way will help me understand.
http://drupal.org/node/942982
Download the beta-1 version, then you should be asked to update to beta2.
Please let me know if the problem happens there as well... If so, then this is a core issue with that update functionality.
Comment #5
Gluhm commentedI tested the update-process and can confirm that the AT-Theme also duplicates folders using the core build in update procedure. It seems to be a Drupal 7 problem and not related to the Omega theme.
Sorry for for the inconvenience.
Comment #6
himerus commentedSo, the issue seems to be that core when pushing those updates via the interface is not respecting themes (modules too??) that don't actually have a template.php or .info file in the root of the directory. I have not tested (or have an environment to test) the FTP updates via the browser.
Many popular themes structure their file systems this way to allow for starterkit, base, admin, etc. themes all in the same package.
Moving this issue to Drupal Core > update.module.
Comment #7
bfroehle commentedMarking as a duplicate of #986616: Update Manager fails when the primary module/theme for a project lives in a subdirectory.