Stripping Forward Slashes

[auztin100]

Hi, I'm sure this has been flagged up before with V10, but I have only seen threads relating to php problems.

I have the problem in normal html where the / are being stripped.

Actinic Code says - "../large/image.jpg"

When uploaded source says just "image.jpg"

[leehack]

Actinic Code says - "../large/image.jpg"

Can you give an example of why and when this would be used?

[auztin100]

I have a folder on my server with a selection of images in, it is in the root, i.e. not in the Acatalog folder, therefore I need to navigate back ?

[AdieB]

Backslash

I have found that if you import product details, the path must use backslash, ie, Images\product.jpg
If you ue forwardslash it removes the path.

[NormanRouxel]

Actinic is designed to automatically upload all images into your acatalog (or whatever you've renamed it to) folder. This is why it's renaming these relative pathed filenames.

You want to do something different than that default behaviour.

Use full URL's for external images and Actinic should leave these alone.

[leehack]

I have found that if you import product details, the path must use backslash, ie, Images\product.jpg
If you use forwardslash it removes the path.

This is correct and normal, it's always a backslash when pointing to a local file.

[leehack]

I have a folder on my server with a selection of images in, it is in the root, i.e. not in the Acatalog folder, therefore I need to navigate back ?

Not sure why you'd confuse things and do it this way, but as advised go full URL if you insist. Actinic is designed to have image defined locally and upload them for you to a set location. You're going against the grain and thus causing the problems.

[auztin100]

It was fine in version 9, I have just upgraded, so its obviously something that has been updated in V10, that I have missed in the small print ??

To be honest I was using another folder so to keep the number of files in the acatalog folder lower, as its rammed anyway ... ahh well, guess I will have to change it to the full URL then ..

Thanks.

The back slash did not make any difference by the way.

[leehack]

Something was changed in v10 yes to address the missing of files that we did want uploaded, this has had a knock on effect in other areas as you've found out though.

[MJS]

Use full URL's for external images and Actinic should leave these alone.

I would then presume we cannot use

../

either for links?

What would be the best way to include links or images that are relative to the domain name, but not include the top level domain name

So I would prefer to use

../acatalog/link.html

rather than

mydomain.com/acatalog/link.html

I think we could use javascript? but I would prefer that we could add links in this way. It worked in the v10.0.3 special build afterall, but v10.0.4 has removed this again

What is the best way to work around this?

[NormanRouxel]

You need the full path. However you can use Actinic Variables instead of hard-coding anything. There's CatalogHomeURL for the URL of the root of your site and CatalogURL for the URL of the acatalog folder.

So

<a href="<actinic:variable name="CatalogURL" />link.html">Click me</a>

Will link to http://www.mydomain.com/acatalog/link.html regardless of you changing your domain name or acatalog directory name.

[MJS]

Thanks Norman

[auztin100]

LivePerson

The problem now effects the running of my liveperson monitor tag code, it's basically stripping out important slashes in the script code, causing it not to work correctly, and from reading a little into the code that is running, this string is built up and accessing a liveperson URL, rather than on my own domain, therefore there is no hard coding work around for this!

Any ideas please ?

<!-- BEGIN LivePerson Monitor. --><script language='javascript'> var lpMTagConfig = {'lpServer' : "server.iad.liveperson.net",'lpNumber' : "4279496",'lpProtocol' : "http"}; function lpAddMonitorTag(src){if(typeof(src)=='undefined'||typeof(src)=='object'){src=lpMTagConfig.lpMTagSrc?lpMTagConfig.lpMTagSrc:'/hcp/html/mTag.js';}if(src.indexOf('http')!=0){src=lpMTagConfig.lpProtocol+"://"+lpMTagConfig.lpServer+src+'?site='+lpMTagConfig.lpNumber;}else{if(src.indexOf('site=')<0){if(src.indexOf('?')<0)src=src+'?';else src=src+'&';src=src+'site='+lpMTagConfig.lpNumber;}};var s=document.createElement('script');s.setAttribute('type','text/javascript');s.setAttribute('charset','iso-8859-1');s.setAttribute('src',src);document.getElementsByTagName('head').item(0).appendChild(s);} if (window.attachEvent) window.attachEvent('onload',lpAddMonitorTag); else window.addEventListener("load",lpAddMonitorTag,false);</script> <!-- END LivePerson Monitor. -->

extract from this :- lpMTagConfig.lpMTagSrc:'/hcp/html/mTag.js';}

is being uploaded as :- lpMTagConfig.lpMTagSrc:'mTag.js';}

[auztin100]

Ok, think I have a work around for this, in case anyone else needs to know ..

This extract becomes :-

lpMTagConfig.lpMTagSrc:'/hcp/html/mTag.js';}

lpMTagConfig.lpMTagSrc:'http:server.iad.liveperson.net/hcp/html/mTag.js';}

[auztin100]

Next problem this causes is with the Facebook LIKE button, which was working in V9, and now is not working in V10, I'm guessing there will be a similar issue which I haven't worked out as yet.