I am testing a new site in the directory /newSite, so it's not in the root. In the install.txt, it mentions that I need to change something on line 35 of editor_plugin.js, and to see the documentation on lines 31-35. I don't see any documentation though, so what do I need to change?

Also, the current development version linked to on the main module page doesn't have the plugin/script/theme files, but I found them in the CVS.

Comments

tronathan’s picture

tronathan commented
Assigned: Unassigned » tronathan
Status: Active » Needs work

1) The wysiwyg module/api recommends putting the tinymce editor (And all other editors) in the /sites/all/libraries folder. I havent tried installing a text editor at /sites//libraries. The documentation still needs updating - leaving the issue open.

2) A new release 6.x-1.2 has been made that contains the missing files:

http://drupal.org/project/tinymce_node_picker 6.x-1.2
http://drupal.org/node/580956 (release)

It still contains the documentation error you cited above.

sharmoni’s picture

sharmoni commented

Solved(?):

Change the line in editor_plugin.js that reads:

      file : '/tinymce_linkpicker',

to:

      file : '/[your-site-folder]/tinymce_linkpicker',

At least this worked for me.

compuguru’s picture

compuguru commented

Hmm, it seems to be ignoring the setting. I tried file : '/newSite/tinymce_linkpicker', and file : 'newSite/tinymce_linkpicker', in a few different browsers, but it keeps opening .com/tinymce_linkpicker?5 Any ideas?

sharmoni’s picture

sharmoni commented

Off the top of my head, my root directory may be different than yours. I'm being hosted rather than running my own server, so I don't know the complete tree.

From what I could make out of the editor_plugin.js code, it's building the tinymce_linkpicker when called by tinymce and then telling the script (which opens when the button is pressed in the tinymce editor) that it will be found at the root. So editing that line was what worked for me. My guess is that the function creates the plugin at the root of the drupal folder, but isn't able to know when that isn't the site root. What happens if you give it the full http: address instead of starting with the site folder?

I'd try it out myself, but right now I'm dealing with the problem of none of the placed links pointing to my aliased pages.

peter törnstrand’s picture

peter törnstrand commented
Component: Code » Documentation

This is now fixed in HEAD. Also fixed in dev snapshot.

peter törnstrand’s picture

peter törnstrand commented
Component: Documentation » Code
Assigned: tronathan » peter törnstrand
Category: support » bug
Status: Needs work » Fixed

Component: Documentation » Code
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.