I'll start off by saying that I can't say with all certainty if this is a problem with Biblio or Token. It may seem like a very one-off problem, but this could be potentially serious so I thought I'd bring it to your attention. This is very strange, so I'm just going to explain my process to create this bug step by step:

  1. Enable Biblio, Token & Automatic Nodetitles modules.
  2. Create a content type and add fields for first and last name.
  3. Try to add tokens for my fields auto nodetitle, but realize fields are not currently supported by token.
  4. Read the enormous issue for Token module: #691078: Field tokens.
  5. Download the branch in #149 which adds support for fields.
    • Disable and uninstall token module. Remove the token directory. Add the branch token module and re-enable token.
  6. Return and set auto nodetitle to use my two fields (which now show up correctly).
  7. Create a piece of content. (It's using the correct node creation form.)
  8. I'm taken to the full node and it's content type is now biblio. The title is the token code (not the replacement values).
  9. Edit the node and it's most definitely a biblio edit form with biblio fields.

Weird, right? Disabling Biblio fixes that bug. My new piece of content is the correct content type and it uses the field token replacements correctly. But if I keep Biblio enabled and simply use drupal core tokens (date, user name - anything not added by the token branch) I don't seem to have a problem either.

I added a comment in that issue: http://drupal.org/node/691078#comment-4396820. Who's to blame? I haven't got a clue.

Comments

rjerome’s picture

Status: Active » Fixed

I tracked it down to the tokens hook in the biblio.module. A tiny, but significant error where a double equals sign (==) was a single (=) :-(

http://drupalcode.org/project/biblio.git/commit/116b085

davidneedham’s picture

Woot, thanks a lot. I can confirm it works now.

Status: Fixed » Closed (fixed)

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