Actinic 10 Changing links??

[robinantill]

I'm thinking a moving from Actinic 9 to 10. So I have downloaded a trial version 10 to ensure I won't get any problems, HOWEVER:-

As an example in one of my fragments I use the following code

<img src="/acatalog/images/front-page/front-wooden-garden-sheds.jpg" width="150" height="125" alt="Timber Garden Sheds" border="0" align="middle" /><br />

When I upload the site to the web this code has now changed to

<img src="acatalog/front-wooden-garden-sheds.jpg" width="150" height="125" alt="Timber Garden Sheds" border="0" align="middle" /><br />

The forward slash has gone from the start of the hyperlink as well as the directory /images/ which means the image does not appear.

In Preview I get the following:-

<img src="file:///C:/Documents and Settings/All Users/Application Data/Actinic v10/Site1/PreviewHTML_Administrator//acatalog/images/front-page/front-wooden-garden-sheds.jpg" width="150" height="125" alt="Timber Garden Sheds" border="0" align="middle" /><br />

In Actinic 9 there is no problem. I don't want to fiddle about with the locations of links on my site, but to move I need to upload a snapshot and upload to the web with the minimum of fuss. I can't see any obvoius reason for this.

I did a search and could not find any threads. Does any one have any ideas what may be going on. Thanks.
Regards,
Robin

[NormanRouxel]

Try (perhaps on a spare system) the 10.0.4 beta that's just been announced.

[robinantill]

Thanks Norman, will give that a try.
What I have found is that on the index.page (outside of the acatalog folder) then ALL images with .jpg have all references to the directory structure removed with the exception of /acatalog/

i.e. /acatalog/images/front-page/front-wooden-garden-sheds.jpg becomes /acatalog/front-wooden-garden-sheds.jpg (/images/front-page is removed)

however if the image is in the acatalog folder then that's not a problem.

If you give the image the full path i.e. http://www.leisurebuildings.net/acat...rden-sheds.jpg then that displays the image correctly.

In the /acatalog/ web pages then ALL images with .jpg have all references to the directory removed just leaving the image name i.e. /acatalog/images/diamond/8x6-classic-apex.jpg becomes just 8x6-classic-apex.jpg (/acatalog/images/diamond/ is removed)

If you give the image the full path i.e.
http://www.leisurebuildings.net/acat...assic-apex.jpg then that displays the image correctly.

Whilst it's probably best to have all your images in the Actinic folder structure the beauty to me was that in the fragments you could use whatever code you wanted and knew it would work. I don't really want to give all the images the full path as this would restrict me moving the shop onto a different domain name, if needed, or just for testing.

Regards,
Robin

[NormanRouxel]

Life (and Actinic) will be much happier if you keep all images that are involved in the site in your Site folder or a sub-folder of said site folder.

If you had an image say <Sitefolder>/images/front-page/front-wooden-garden-sheds.jpg

Then you could refer to it within Actinic layouts (or embedded HTML) as:

<img src="images/front-page/front-wooden-garden-sheds.jpg" width="150" height="125" alt="Timber Garden Sheds" border="0" align="middle" />

And Actinic will be able to find it, upload it into the servers acatalog and change the home page links or acatalog ones as required. So on the home page the SRC attribute will be src="acatalog/front-wooden-garden-sheds.jpg" and within acatalog pages it will be src="front-wooden-garden-sheds.jpg"

[robinantill]

Hi Norman,
Thanks for that. I do agree with you that all the images should go in the Site Folder, which I will now do. Not sure how long this will take as I have about 1500 pages to go through. This will teach me in the future.
Seems strange that Actinic 9 allowed for images outside of the Site Folder whereas Actinic 10 does not. Probably to make us not be too slapdash in the future.
Regards,
Robin

[NormanRouxel]

If you move your Product Images to somewhere new, it should be possible to run an Update Query on ActinicCatalog.mdb / Product table / ImageFileName column to replace all old paths with new. Take care, and backup first of course.

[robinantill]

Would that work on images inside Fragments?

[NormanRouxel]

No idea. Why not look in the database (same table) for a Fragment Image that you know the name of and see what column it's in and what's there?

[robinantill]

Thanks for your help, much appreciated. Regards Robin

[malbro]

The forward slash has gone from the start of the hyperlink as well as the directory /images/ which means the image does not appear.

Hi Robin

I have a similar problem in some custom code

<form method="post" action="../plugins/addToQuote.php">

In preview actinic will add the relevant path to the preview folder to this link but in the uploaded version on site i get

<form method="post" action="addToQuote.php">

which is annoying to say the least.

Update:

A quick test with 10.0.4 shows no problem.

So that is one good reason to move to V10.0.4 .

[NormanRouxel]

Malcolm

Quick fix would be to move addToQuote.php into your Site folder, reference it as

<form method="post" action="addToQuote.php">

And let Actinic upload it for you into the servers acatalog.

Maybe we should lobby for new Actinic flag:

<actinic:block DontAlterMyURLs="true">....</actinic:block>

P.S. Counted to 10 and edited what I initially typed to be Alter.

[malbro]

Malcolm

Quick fix would be to move addToQuote.php into your Site folder, reference it as

<form method="post" action="addToQuote.php">

And let Actinic upload it for you into the servers acatalog.

Maybe we should lobby for new Actinic flag:

<actinic:block DontAlterMyURLs="true">....</actinic:block>

My workaround is to use the Actinic variable WebSiteURL to fix the link, as that file is part of a complete php package that lives in the folder which for reasons that no longer seem relevant I wanted to keep separate from Actinic.

 <form method="post" action="<actinic:variable name="WebSiteURL" />plugins/addToQuote.php">

However as per update above V10.0.4 does not have this particular bug so I will be OK once they release the new version for production.