Enabling token_insert prevents certain nodes from being saved, i.e. webform.

Can you be more specific? Do you get an error message of some sort? What steps should I take to reproduce?

I added a textfield to a content type and everything worked just as expected...

I have a similar issue where when token_insert was enabled, previously saved webforms would not save.
Neither would new webforms. If you went to node/add/webform, and clicked save, you wouldn't even get the "title is required" error, just get bounced back to the webform.

We're in the process of trying to replicate on a clean install with only modules required for token_insert and webform installed.

Database is PostGres, although that's probably not the issue.

Modules list:
Advanced Forum (advanced_forum) 7.x-2.0-rc1 7.x-2.0 Update available
Drupal 7.12 7.12 Up to date
node_clone 7.x-1.0-beta1 7.x-1.0-beta1 Up to date
Context (context) 7.x-3.0-beta2 7.x-3.0-beta2 Up to date
Chaos tools (ctools) 7.x-1.0 7.x-1.0 Up to date
Date (date) 7.x-2.1 7.x-2.2 Update available
Devel (devel) 7.x-1.2 7.x-1.2 Up to date
Diff (diff) 7.x-2.0 7.x-2.0 Up to date
DraggableViews (draggableviews) 7.x-1.x-dev 7.x-1.x-dev Up to date
Email (email) 7.x-1.0 7.x-1.0 Up to date
Entity API (entity) 7.x-1.0-rc1 7.x-1.0-rc1 Up to date
Features (features) 7.x-1.0-beta6 7.x-1.0-rc1 Update available
Feeds (feeds) 7.x-2.0-alpha4 7.x-2.0-alpha4 Up to date
Fivestar (fivestar) 7.x-2.0-alpha1 7.x-2.0-alpha2 Update available
GMap (gmap) 7.x-1.x-dev 7.x-1.x-dev Up to date
Google Visualization Style (gvs) 7.x-1.0-rc2 7.x-1.0-rc2 Up to date
Job Scheduler (job_scheduler) 7.x-2.0-alpha2+3-dev 7.x-2.0-alpha2 Up to date
Link (link) 7.x-1.0 7.x-1.0 Up to date
Location (location) 7.x-3.x-dev 7.x-3.x-dev Up to date
Login one time (login_one_time) 7.x-2.4 7.x-2.6 Update available
Node export (node_export) 7.x-3.0-rc1+2-dev 7.x-3.0-rc1 Update available
References (references) 7.x-2.0 7.x-2.0 Up to date
Pathauto (pathauto) 7.x-1.0 7.x-1.0 Up to date
Rules (rules) 7.x-2.0 7.x-2.1 Update available
Testing (simpletest) 7.x-2.0 7.x-2.0 Up to date
Token (token) 7.x-1.0-rc1 7.x-1.0-rc1 Up to date
Universally Unique ID (uuid) 7.x-1.0-alpha3 7.x-1.0-alpha3 Up to date
Views (views) 7.x-3.2 7.x-3.3 Update available
Views Bulk Operations (views_bulk_operations) 7.x-3.0-rc1 7.x-3.0-rc1 Up to date
Voting API (votingapi) 7.x-2.4 7.x-2.6 Update available
Webform (webform) 7.x-3.17 7.x-3.17 Up to date
webform-fivestar 7.x-1.x-dev 7.x-1.x-dev Up to date

drush pml --type=module --status=enabled --pipe --no-core

Gives me this result:

devel
token
token_filter
token_insert_text
token_insert
webform

These are the non-core modules I have enabled on my site. I can add text fields to a webform, enable token_insert for both the body and the new textfield, add a webform without a title and get the error message and add a webform with title and save the new webform.

Are you sure it's token_insert's fault?

Hi,

I'm also unable to save content.

I'm able to input my title and text (including the token), but when I click save, I'm returned to the same input form with all my entry cleared, and the node has not be saved.

Nothing showing up in my error log.

Hope this helps.

can someone who has this error start testing with only these modules enabled:

devel
token
token_filter
token_insert_text
token_insert
webform

And then gradually start enabling modules until the error occurs?
As I said in #5, I don't get the error with these modules enabled, so maybe it's because of a clash with an other module...

Tested with:

Pressflow Drupal 7.12 profile "Minimal"
field_ui 7.12
token 7.x-1.0
token_filter 7.x-1.1
token_insert 7.x-2.0
token_insert_text 7.x-2.0
token_insert_ui 7.x-2.0

Created content type "Story"

Edited the field "Body" and enabled "Token Insert".

Inserted "[node:author]" via the Insert Token groups select list and the insert button.

It worked.

Enabled modules progressively back to what I had earlier, now it works. Same codebase, multisite install, MAMP.

Can not reproduce on fresh install.

I noticed that Insert Token from the in page element stops working when I added wysiwyg token insert. The wysiwyg works.

I noticed that Insert Token from the in page element stops working when I added wysiwyg token insert. The wysiwyg works.

Yes, when wysiwyg is enabled you should use the wysiwyg plugin, not the form below that element.
In the latest dev version that form is hidden when the wysiwyg editor is active

As per

Tested with:

Pressflow Drupal 7.12 profile "Minimal"
field_ui 7.12
token 7.x-1.0
token_filter 7.x-1.1
token_insert 7.x-2.0
token_insert_text 7.x-2.0
token_insert_ui 7.x-2.0

Created content type "Story"

Edited the field "Body" and enabled "Token Insert".

Inserted "[node:author]" via the Insert Token groups select list and the insert button.

It worked.

Enabled modules progressively back to what I had earlier, now it works. Same codebase, multisite install, MAMP.

Can not reproduce on fresh install.

I'm going to close this, because I don't think this is a Token Insert issue. It might be because of some kind of clash with an other module. But as long as we don't know which module that is, we can't reproduce this and thus we can't fix this...

I am having this same problem, with a custom content type, where the inserted token is a field collection on the node edit form added with a token node:field- etc

It was working a couple of weeks ago great. I can restore the old db and it works too. but it's kind of complex to back migrate content types, views panels created since then

I have a hunch it's related to two things:
1. I disabled the Filtered Text format and ended up re-enabling it in the db since I was getting missing format messages in dblog
2. I tried the metatag and metatags_quick modules - metatag just isn't working yet for D7, and metatags_quick seems to have some non-standard install and uninstall code. I also manually removed leftover rows from metatag modules in the system table AFTER I uninstalled them during the debug process.

I was hoping to "fix" the current project but looks like I will have to roll back, since this is a critical feature.

I should note that global tokens are replaced with token_filter and I have installed and uninstalled various versions of token_filter too.

I found the problems in some custom code:

path_is_admin() (in PHP code)
Drupal.behaviors (in JS code)

using either of these break the token replacement :)

regarding OP

having token_insert_text enabled keeps the node from being saved;

I disabled it because I am using token_insert_wysiwyg anyway, fixed the problem

I'm glad to say this should finally be fixed in latest dev.

See #1764610: Token insert is preventing comments from being saved.

If I could kiss you I would, thank you as this fixed a problem that I've spent the last 2 hours on.