I love linkit. However, had not had the chance to use it much, but when I used it on Chrome, it crashed the browser the first time I did. I'll try to do more later. Thanks again. This is a great addition to the workflow.
Sure, I'll make sure there is only one README and that all info from the other README's get there. It'll be an awesome new stable release coming up soon with lots of improvements.
Should be the examt same as using WYSIWYG and TinyMCE.
-- INSTALLATION & CONFIGURATION --
1. Install and enable Linkit's dependencies (see below). Make sure
Path Filter is enabled on the input formats you intend to use with linkit
2. Install and enable linkit (required) and at least one of linkit_node,
linkit_views and linkit_taxonomy
3. Enable the Linkit button in your WYSIWYG editor's settings
Thank you anon, got everything working, except now I believe HTMLPurrifier is stripping the generated links out. Can you take a look at my post on that issue que and let me know what you think. http://drupal.org/node/838496
I don't have Theme developer enabled and I'm trying to use Linkit on a CKEditor only installation.
I'm pretty shure (not absolute) I've done everything mentioned in the readme files.
The only problem I encountered was the second point in the extra readme file for Linkit without wysiwyg where one had to add the button in the toolbar in the ckeditor.config.js file. In my config file there was no toolbar specification as everything is configured in the CKEditor settings in the configuration page of the module. I added 'Linkit' there and when I go to my edit-page I see the linkit icon but nothing happens when clicking it.
After a while I thought it could have something to do with the directory where I installed Linkit as I put all the contributed modules in a directory "contrib" within my "modules" directory. (sites/all/modules/contrib/linkit)
But when I uninstalled the module, move it to the root of the modules directory and enabled it again nothing had changed. So, I'm not shure it has something to do with it.
Anyone ideas what else I could try, or is it a bug?
The Linkit popup is triggerd by the editors own functions, so I cant see why this should be a Linkit problem.
Are you running firefox for chrome browser? If you are, do you have time to see if you can get some extra info from the JS-console?
When you push the Linkit button, there should be some JS errores.
Comments
Comment #1
anonAdded a README.txt file into CVS.
Its just a very basic start.
Comment #2
anonsee #744916: Links don't work
Comment #3
betamos commentedREADME file needs information about how to configure the module.
Some kind of community documentation would also be handy. I'll do it as soon as I get my CVS account.
Comment #4
anonYou dont need a CVS account to patch =)
Comment #5
anonComment #6
CinemaSaville commentedHow do I use this with CKEditor?
Comment #7
betamos commentedThere is a README.txt in linkit/editors/ckeditor
We will be improving the documentation soon, but if you have any questions just ask.
EDIT: The README I referred to is only if you use CKEditor without WYSIWYG.
Comment #8
CinemaSaville commentedAh OK. You hid it in there. You may want to put that in the main Readme.txt Thanks again for doing this. I'll let you know how it goes.
Comment #9
betamos commentedYep, sorry about that. We will be working with major improvements on the documentation overall in the next weeks.
If you want to help us, tell us what you think about Linkit. We need all feedback we can get right now, since the project is pretty new :)
Comment #10
CinemaSaville commentedI love linkit. However, had not had the chance to use it much, but when I used it on Chrome, it crashed the browser the first time I did. I'll try to do more later. Thanks again. This is a great addition to the workflow.
Comment #11
betamos commentedCommited a better README for 6.x branch now. We'll look out for that Chrome bug, btw. Thanks!
Comment #12
jgdemat commentedIt would be useful to also include the linkit/ckeditor/README.txt into the help.
Comment #13
betamos commentedSure, I'll make sure there is only one README and that all info from the other README's get there. It'll be an awesome new stable release coming up soon with lots of improvements.
Comment #14
Daythorn commentedIs there any instructions for how to install Linkit on CKEditor with WYSIWYG?
I am a beginner and don't really understand how to make this work.
And is Linkit working with HTML Purifier too?
Comment #15
anon@daythorn
Should be the examt same as using WYSIWYG and TinyMCE.
-- INSTALLATION & CONFIGURATION --
1. Install and enable Linkit's dependencies (see below). Make sure
Path Filter is enabled on the input formats you intend to use with linkit
2. Install and enable linkit (required) and at least one of linkit_node,
linkit_views and linkit_taxonomy
3. Enable the Linkit button in your WYSIWYG editor's settings
Comment #16
bryancasler commentedHow do I enable it with just CKeditor installed, not WYSIWYG?
Comment #17
anon@animelion:
FROM linkit/editors/ckeditor/REAMME.txt
##############################################
## ONLY if you use ckeditor WITHOUT wysiwyg ##
##############################################
Installation:
Do the following steps to add Linkit button to the CKEditor toolbar:
1. Open /drupal/modules/ckeditor/ckeditor.config.js
2. Add button to the toolbar. The button name is: Linkit
For example if you have a toolbar with an array of buttons defined as follows:
['Link','Unlink','Anchor']
simply add the button somewhere in the array:
['Linkit','Link','Unlink','Anchor']
(remember about single quotes).
3. Scroll down to the end of the file, right before "};" insert:
// Linkit plugin.
config.extraPlugins += (config.extraPlugins ? ',Linkit' : 'Linkit' );
CKEDITOR.plugins.addExternal('Linkit', Drupal.settings.basePath + 'sites/all/modules/linkit/editors/ckeditor/');
Comment #18
bryancasler commentedThank you anon, got everything working, except now I believe HTMLPurrifier is stripping the generated links out. Can you take a look at my post on that issue que and let me know what you think. http://drupal.org/node/838496
Comment #19
anonAdded a comment on http://drupal.org/node/838496#comment-3138040 about HTML Purifier
Comment #20
bryancasler commentedThanks anon, that took care of it.
Comment #21
bclinton commentedI had an issue where I could see the Linkit button in ckeditor, but it would not open as if it was disabled. Firebug showed an error:
To resolve this I needed to set some settings in Drupal Site Configuration -> LinkIt
Comment #22
anon@bclinton: Good point, I will look at this.
Comment #23
anon@bclinton:
I unistalled Linkit, and installed it again, but I cant re-create that error msg. Its works perfect for me.
Comment #24
cverond commentedI had the same Drupal.settings.linkit problem. It was the Theme Developer module that made Drupal.settings disappear.
Comment #25
anonComment #26
aimevpI'm having the same problem with the D7 version.
I don't have Theme developer enabled and I'm trying to use Linkit on a CKEditor only installation.
I'm pretty shure (not absolute) I've done everything mentioned in the readme files.
The only problem I encountered was the second point in the extra readme file for Linkit without wysiwyg where one had to add the button in the toolbar in the ckeditor.config.js file. In my config file there was no toolbar specification as everything is configured in the CKEditor settings in the configuration page of the module. I added 'Linkit' there and when I go to my edit-page I see the linkit icon but nothing happens when clicking it.
After a while I thought it could have something to do with the directory where I installed Linkit as I put all the contributed modules in a directory "contrib" within my "modules" directory. (sites/all/modules/contrib/linkit)
But when I uninstalled the module, move it to the root of the modules directory and enabled it again nothing had changed. So, I'm not shure it has something to do with it.
Anyone ideas what else I could try, or is it a bug?
Comment #27
anonHi hatznie, sounds like you have some JS errors.
The Linkit popup is triggerd by the editors own functions, so I cant see why this should be a Linkit problem.
Are you running firefox for chrome browser? If you are, do you have time to see if you can get some extra info from the JS-console?
When you push the Linkit button, there should be some JS errores.
Comment #28
anonAlso, Please create a new issue for this.
This issue isnt about that, its about documentation.
Thanks.