Project:Conference Organizing Distribution (Drush make files and install profile)
Version:5.x-1.x-dev
Component:Code
Category:bug report
Priority:normal
Assigned:zacker
Status:closed (won't fix)

Issue Summary

The token module is not listed in the readme.txt, causing trouble for the users until they discover the documentation is incomplete. Also, the modules are listed with their file name, not with the Drupal module name, which is sometimes not the same and hence it could be made easier to newbies.

Comments

#1

thanks temmeron. I will create a second issue for the readme instructions.

#2

(and make i a dependency for the install profile)

#3

i tried adding token to the install profile and got pathauto and link errors. so i removed pathauto for now. token is not currently required AFAICT.

#4

Title:token module needs to be mentioned in the readme.txt» pathauto/token module problems and mentions
Component:Documentation» Code
Priority:minor» normal

Now that it's been removed, I'd like to get back to a place where we can talk about how to cause this bug to happen and how to fix it.

I created a codefake.profile as a simplified test case that looks like this:

function codfake_profile_modules() {
  return array('block', 'color', 'comment', 'filter', 'help', 'menu', 'node', 'system', 'taxonomy', 'user', 'watchdog', 'pathauto', 'token', 'path');
}

And it installed fine with Pathauto5.x-2.0 and Token5.x-1.9. No errors that I could see at install.

So, who has a simplified repeatable test case for reproducing this?

#5

when installing from an install profile, I've been getting this error:

Call to undefined function token_get_values()

commenting out pathauto from the module list array and enabling it after install is a workaround.

DT

#6

@davidwhthomas - did you try adding token to the list of modules to be installed if it wasn't already there?

Also, which line was that error on?

#7

Status:active» closed (won't fix)

The 5.x version of this module is basically no longer supported. I'm clearing out the queue for 6.x.

I was also never able to repeat the bug the times I did investigate it in 2008, so I think it was a temporary problem that we got around.