Closed (fixed)
Project:
Linkit
Version:
7.x-3.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
15 Apr 2015 at 10:41 UTC
Updated:
19 Nov 2015 at 22:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
mizage@gmail.com commentedI can confirm this issue. Using the following:
Firefox or Chrome
Drupal 7.36
Linkit 3.3
IMCE 1.9
Wysiwyg 2.2 configured with TinyMCE 3.5.11
See screen shots.
Comment #2
tylergbass commentedHello,
I can also confirm that this is an issue with Linkit 7.x-3.3.
Comment #3
joverstreet001 commentedHas there been any fix to this issue? Customer is experiencing the same behavior.
Thanks!
Comment #4
tylergbass commentedWorked with @cmanalansan to create this patch.
Comment #5
mizage@gmail.com commentedThanks @tylergbass and @cmanalansan! The patched worked for me.
Comment #6
jaydarnellI can also confirm that patch #4 works for version 7.x-3.4
Comment #7
granticusiv commentedI can also confirm patch #4 work width 7.x-3.4
Comment #8
anonWhats the reason for this?
linkit_profile_load_by_formatreutrns the first profile that has a given text format.To just move the tests
isset($profile->data['imce']) && $profile->data['imce'] == 1may fix the problem, but not the root problem.Also, I can't see that ckeditor has to do with this, please explain.
Comment #9
leonblueeyes commentedThanks tylergbass and cmanalansan! The patch #4 worked for me.
Comment #10
danbarron commentedI am having the same problem even when CKEditor is present, and the problem seems to be in the same bit of code.
I can fix it by selecting all text formats to use the LinkIt profile, but this is clearly an accidental work around that will break if we change our set up.
I'm not 100% sure what this code is meant to be doing, but it does seem that something is amiss in the logic. The $profile variable is used to determine whether or not to add the button, but that variable will be FALSE if the last text format checked in the foreach is not using the profile.
Comment #11
anonI can confirm this issue now. I will have a look at it. First look at the provided patch seems to solves this.
Comment #12
zipymonkey commentedPath #4 works for me as well.
Comment #14
anonThanks for the patch.