Dreamweaver - Templates - Image Swaps

1. Store a short path in the database. Something like -
"/list_number/photo_name". Then I can build a root relative path for each
image to get from the root to the "photos" folder and the remainder of the
link
will be in the filename.

Perfect. So what you would do is always concatenate the path field with the
image name field and use that string for the link.

P.S. I owe you lunch.

Something expensive sounds great.

Thanks so much for your help.

You're welcome.

Are you paid to do this?

No - like many others, I volunteer for this.

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"gwalt" <webforumsuser (AT) macromedia (DOT) com> wrote

The light is starting to come on! Thanks a bunch.

One last question and I will let this one be done.

The main reason that I am storing the full path to my images in the
database
is that I am dynamically creating a folder for images as each listing is
created (photos uploaded). Now, if I only store the image name I will
need to
dynamically build the path when I insert each image in page and call it.
Not a
big problem, until I reach my master list page. Here I have a record set
that
brings in my listings with photos and displays a preview for selection. I
now
need to prefix my image path (/photos/list_number/photo_name.jpg) with the
listing number that's in the recordset, but I can't.

I see two options at this point:

1. Store a short path in the database. Something like -
"/list_number/photo_name". Then I can build a root relative path for each
image to get from the root to the "photos" folder and the remainder of the
link
will be in the filename.

2. Store only the file name and figure out a way to completely build the
root
relative path on the fly. Don't know how to do yet as I mentioned above.

P.S. I owe you lunch. Thanks so much for your help. Are you paid to do
this?

Thx,
Mark

Here are five ways to make changes not propagate from Template to child -

1. Rename the Templates folder
2. Move the Templates folder to some other folder level in the site other
than root level
3. Move a template out of the Templates folder.
4. Make changes to an editable region of the template (which will not
propagate)
5. Corrupt the site cache so that the link between template and child page
is broken

The latter problem can be repaired by using SITE | Advanced > Recreate Site
Cache, and the three others can be fixed by just not doing them. Have you
done any of those?

Two expensive lunches would be nice.

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"gwalt" <webforumsuser (AT) macromedia (DOT) com> wrote

I fibbed - I have one more question that is bothering me about the
template
update issue.

I understand the "root relative" link issue and how when updating the
child
files DW does not find my image swap links. However, all of my updates so
far
have been minor. I simply made a text change yesterday and the links
didn't
work. Can you explain this one?

P.S. Now two lunches.

Thx,
Mark

I think I am free and clear on each of the five propogating issues.

My changes propogage from template to child just fine. I corrected a typo,
for example, and all of the child files were updated fine including the
ad_preview page. However, once the ad_preview (file w/ the image swaps) was
updated and reloaded to the server, the image swaps acted like they were
working but the images were transparent or not there. Several of the images
are different sizes so the screen would jump as each thumb was clicked, but
there was just a blank screen present.

Is this still symtomatic of a "root relative" link issue?

Thx,
Mark

No - it's symptomatic of using Norton Internet Security, or some other
program that edits your pages to remove "offending" images.

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"gwalt" <webforumsuser (AT) macromedia (DOT) com> wrote

I think I am free and clear on each of the five propogating issues.

My changes propogage from template to child just fine. I corrected a
typo,
for example, and all of the child files were updated fine including the
ad_preview page. However, once the ad_preview (file w/ the image swaps)
was
updated and reloaded to the server, the image swaps acted like they were
working but the images were transparent or not there. Several of the
images
are different sizes so the screen would jump as each thumb was clicked,
but
there was just a blank screen present.

Is this still symtomatic of a "root relative" link issue?

Thx,
Mark