https://drupal.org/project/token_field

Maybe there is code you can use there or, even better, join forces and contrib your code to the existing module to help get a 7.x-stable. I've not browsed the code in neither of two, but looks like they're closely related.

(Also, 7.x-1.x-dev version is not available when filing issue, filed against 7.x-1.0)

Comments

maximpodorov’s picture

Issue summary: View changes
Status: Active » Closed (works as designed)

No, the goals of these modules are different. If you still think they can be united, please reopen the issue and add more details.

nithinkolekar’s picture

Status: Closed (works as designed) » Active

+1 not only https://drupal.org/project/token_field other modules like

https://www.drupal.org/project/auto_entitylabel
-only for title of node
-option to hide/show
-update value one content edit
https://www.drupal.org/project/commerce_autosku
- same as auto_entitylabel

https://www.drupal.org/project/token_alias (not tested)
- compound tokens
- supports calculations

https://drupal.org/project/token_field
- can't use token_field in another token
- unable to apply validations

https://www.drupal.org/project/computed_field
- do what ever you want, if you are a coder.

are doing same thing with little different configuration.

https://www.drupal.org/project/field_default_token
- can't use characters like hyphen,underscore in field along with token. It breaks token replacement and set value to characters only.

What Field default token can implement from these modules?
- also apply while updating node/content (when field left empty or always)
- hide/show
- allow user to enter token as value while creating/editing node(override default token)

amontero’s picture

I still +1 module merge if there is little difference.
However, this module has more users than token_field. Also, looking at the maintenance status of some of them, they are 'Minimally maintained' and even perhaps original module maintainers would happily give them for adoption (if this module's maintenance status is up to date, of course).
Perhaps the correct path would be to contact the other module maintainers and offer them merging their code here and be appointed as co-maintainers. Each module's functionality, code and issue queue's should be reviewed to decide which one to merge into which other.
Too many duplicate modules means also effort duplication and waste and, what now are several 'minimally maintained' modules could be just one better co-maintained one. All of them have pending issues, and that's not beneficial to none of them nor the community. Merging some would mean better maintenence.

nithinkolekar’s picture

+1 not only https://drupal.org/project/token_field other modules like

Err. this makes you think +1 for token field but I am too in favor of Field default token, that is why I suggested at the end what it can borrow from other modules.

paean99’s picture

Token Filter is a module that can be used in a similar manner to Field default token. See this simple tutorial to confirm it: https://www.ostraining.com/blog/drupal/tokens-in-drupal-fields/

I do not know if either of the modules can share or merge code...

nithinkolekar’s picture

@paean99 that module is for textarea only and it does't applicable for text field. This is because there is no text formats(filtered ,full html etc.) for textfield I guess..

paean99’s picture

Yes, i believe you are right, thanks for the correction.

maximpodorov’s picture

Status: Active » Closed (works as designed)