In the page project of CKEditor Link, reference is made to the 2nd part of this module, that is noted as "An optional (but recommended) server-side input format filter that converts the links added through the plugin into aliased and language prefixed URLs."

Why is this option recommended ? Will be a problem if this option is not checked ?

For my side, I would like to have data under node/x format in the database : I think that, in the case of copy of the database to a test site not in root (i.e. with an url like http://mysite.fr/test/), internal like will be always good, while if the links are under alias url (/alias-of-the-node format) in the database, it will lead to error page (page doesn't exist error) in the test site.

Comments

jasondecamp’s picture

jasondecamp commented

I'm with lucuhb on this one. My main problem with CKEditor Link in the past has been when migrating content from the development site (not located at site root) to the live site (root path). Suddenly all of the links need to be re-entered. I was not even aware that there was an option. Can we get some more information about why it is recommended? Otherwise, I'm going to be disabling that feature pretty universally.

anrikun’s picture

anrikun commented

Your problem is not related to CKEditor Link. This would happen even if you didn't use it.
For instance, think about image paths:
If you insert an image located at /my-dev-path/sites/default/files/images/my-image.jpg on your dev site
then move your dev site to root (/), image path will get broken too, won't it?

A solution to this problem is to use the Pathologic module: http://drupal.org/project/pathologic

Another thing you mustn't forget is to clear *all* your Drupal cache when moving from dev to production.
This way, cached paths will be updated.

About the Filter: CKEditor Link Filter is just here to convert your /node/xxx paths into their aliases when content is sent to end-users.

anrikun’s picture

anrikun commented
Status: Active » Closed (works as designed)