An oddity. When I update the context module from 7.x-3.0-alpha3 to 7.x-3.0-beta1 it breaks the directory structure. I thought it was related to a core bug (#986616) but it works via the update manager.

Before the update the module lives in sites/all/modules/contrib/context. After the update (drush upc -y context) I end up with:

$ svn status
?       sites/all/modules/contrib/context/context
!       sites/all/modules/contrib/context/context_ui/tests
!       sites/all/modules/contrib/context/context_ui/theme
!       sites/all/modules/contrib/context/context_ui/context_ui.module
!       sites/all/modules/contrib/context/context_ui/context_ui.install
!       sites/all/modules/contrib/context/context_ui/json2.js
!       sites/all/modules/contrib/context/context_ui/context_ui.css
!       sites/all/modules/contrib/context/context_ui/README.txt
!       sites/all/modules/contrib/context/context_ui/context_ui.info
!       sites/all/modules/contrib/context/context_ui/context_ui.js
!       sites/all/modules/contrib/context/context_ui/jquery.pageEditor.js
!       sites/all/modules/contrib/context/context_ui/export_ui

It has removed the original files from within the sites/all/modules/contrib/context/context_ui directory and downloaded a new copy of the module as a subdirectory, sites/all/modules/contrib/context/context.

Comments

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna commented

Just to keyword drop to make searching easier, this bug is related to "pm-updatecode" aka "upc".

moshe weitzman’s picture

moshe weitzman CreditAttribution: moshe weitzman commented
Assigned: Unassigned » jonhattan

There is a movement around to standardize do that the "main" module in a project is located at top level and additional ones are in subdir. This movement has an issue but I cant find it. Is mentioned at #925246: Move devel module down a level in filesystem.

We should still fix if this is a real bug.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna commented

I'm aware of that movement, bug #986616 kinda started it and I was one of the ones chasing around with a bullwhip ;-) This is something different, though, as Context doesn't live within a subdirectory of itself like e.g. the Omega theme does.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna commented

@moshe: the Context module has a valid directory structure, but something weird is happening. I haven't seen this happening to any other project, just Context.

jonhattan’s picture

jonhattan
Primary language Spanish
Location Plasencia
CreditAttribution: jonhattan commented

I was unable to reproduce it. Will test on a svn setup.

greg.1.anderson’s picture

greg.1.anderson CreditAttribution: greg.1.anderson commented
Version: All-versions-4.x-dev » 8.x-6.x-dev
Status: Active » Closed (won't fix)
Issue tags: +Needs migration

This issue was marked closed (won't fix) because Drush has moved to Github.

If desired, you may copy this bug to our Github project and then post a link here to the new issue. Please also change the status of this issue to closed (duplicate).

Please ask support questions on Drupal Answers.