Hi all,
I'm just wondering why entity has this deep nesting of catalogs.
On my my setup (uniform server, win xp) it looks something like this: /sites/all/modules/entity/entity/entity/entity/
It seems like the media module expects on catalog less ( looking for: /sites/all/modules/entity/entity/entity/entity.db.inc.
Can anyone explain how I could fix this?

Thanks for a great module.

Jørgen

Comments

fago’s picture

ouch, "/sites/all/modules/entity/entity/entity/entity/" is wrong. There is another, second "entity" folder for the CRUD API module below the usual "entity" directory, but not more. How did you update the module previously?

rakke’s picture

Hi fago,
I've updated my module by using the drupal update (core). But it seems like something broke the structure of entity. I'm on a fresh install now, and so far this looks ok. Main entity content in sites/all/modules/entity/entity. This structure I can understand, just had problems understanding the 4 level deep nesting.

I'm not sure what more information I can give to help. I still have the old install, so I'll try finding all info you need.

Jørgen

fago’s picture

Title: Why all the subfolders? » Updating with the Update-manager fails
Category: support » bug
Priority: Minor » Major
DamienMcKenna’s picture

The core issue is that drupal_get_path() expects your module's primary module to be in the module's main directory and doesn't work when it's in a subdirectory. The simple fix is to move the module's primary module to the main directory. Doing so now would be a good idea, before the final Drupal 7.0 release.

fago’s picture

I don't think drupal_get_path() does assume that, anyway please keep the discussion centralized at #986616: Update Manager fails when the primary module/theme for a project lives in a subdirectory. I leave this issue open though, such that is visible for others in the entity API queue.

DamienMcKenna’s picture

When I said "doesn't work when it's in a subdirectory", what I meant was that it returns the path to the directory that the example.info file resides in, not some random parent directory that contains all of its related submodules. Rather than building lots of work-arounds to deal with really odd scenarios and ending up chasing our tails when a new fringe use case is identified, the simplest solution is to fix the modules.

Scott J’s picture

Does anyone know where this /sites/all/modules/entity/entity/entity/entity/ path is being saved? I was just making some progress with D7, so I would like to manually delete it from my database rather than do another fresh install.

fago’s picture

Check the system table.

fago’s picture

Status: Active » Fixed

fixed with #988780: Merge both modules into one - thus placing the next dev snapshot at "sites/all/modules/entity" + running update.php should fix your installation.

Status: Fixed » Closed (fixed)

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