We recently discovered that LinkIt wasn't working for our primary page content type on a site I'm working on. I tracked the cause to Viewfield. When I removed the field LinkIt began to work. I further narrowed the cause to the token browser. If I comment out the // Provide token help. section of the viewfield.module the token browser doesn't display and LinkIt works.

I realize that this likely means that there is a bug in token rather than viewfield, but I'm posting here in case someone else runs into this and also as a feature request to include an option in the viewfield configuration to prevent the token browser from displaying. Even without the LinkIt conflict, on a large site, the long list of tokens makes the edit page very sluggish.

Comments

Jonah Fenn’s picture

Jonah Fenn commented

We're encountering this issue as well. An option to use/not use the token list would be great.

jerdavis’s picture

jerdavis
Location Minneapolis, MN
commented
Version: 7.x-2.0 » 7.x-3.x-dev
Category: Bug report » Feature request

Adding as a feature request. This option would not be included in 7.x-2.x in order to minimize risks to existing, stable D7 sites.

jerdavis’s picture

jerdavis
Location Minneapolis, MN
commented
Status: Active » Closed (duplicate)

Actually, I'm going to reference this to #2073555: Node/add/page with viewfield loaded very slow ... and address it there as that's a more generic request (not specific to a conflict with linkit)