Hi,

I'm relatively new to drupal, have setup my site in the past 4 months and have upgraded to 4.6.1 successfully yesterday. Quite an exercise but with appropriate testing and preparation I did it in 15 minutes. Most of the time's I've been able to quickly find solutions to problems on this site but now I'm stuck.

I'm using htmlarea and freelinking, both new to me in my 4.6 site. The xinha extension within htmlarea uses CamelCase directorynames for their plugin's, consequently url's created e.g. for smiley's contain these CamelCase directory names. Freelinking acts on these and breaks the url's. Freelinking inserts its own url substituting the CamelCase part. I can imagine (but have not tested) that this goes for any url containing CamelCase.

I would expect the Freelinking module to not do any work within a url, even within any html tag, therefore I report the bug against freelinking, correct me if I'm wrong.

Thanks for your support
Johan

Comments

jvlagsma’s picture

jvlagsma commented

Freelinking version is $Id: freelinking.module,v 1.2.2.4 2005/06/01 22:51:18 eafarris Exp $

eafarris’s picture

eafarris commented
Assigned: Unassigned » eafarris

You should configure your input formats so that freelinking takes place after htmlarea. This can be done in administer->input formats.

You are correct that freelinking should not touch the inside of a URL. I'll look in to that.

Also, the CVS version of freelinking.module has a setting to turn off CamelCase links. It will work fine with Drupal 4.6.x.

jvlagsma’s picture

jvlagsma commented

Htmlarea doesn't use input format's, it's creating the input that goes through the filters so it's always going to be first.

I had a go at the cvs version of freelinking (1.11), works fine even with the CamelCase option checked so that solves my problem. Added bonus is extra freelinking functionality ;-) nice new block with to be written pages.

Many thanks for your quick support!
Johan

jvlagsma’s picture

jvlagsma commented

Correction, on prod I do need to switch off CamelCase, fine work around for me. Not sure why test differs but that's for another time.

As an aside, on test I ran into a max for keylength of 500 char (mysql hardly tuned) and on prod the db insisted on lower case tablename for dropping cache. I tinkered with freelinking.mysql and all went well.

Johan

eafarris’s picture

eafarris commented
Status: Active » Fixed

This is fixed for real, now, in revision 1.17 (HEAD) or 1.2.2.8 (4.6). The regular expression that looks for CamelCase words leaves html tags alone.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)