Location(s) of images and name of Media directory

[Randall]

When I browse for an image, SS shows only the Media directory and
those under it. (Due to the number of images, I'm limited to using the
pop-up window.) Can I configure SS so that it offers the root (or
store) directory and I navigate down from there?

If that's is possible, I'd prefer to be able to put images under the
html directories they serve, because that's the way the site I'm
converting to SS is currently set up.

If it's not possible, can I at least change the name of "Media"
directory to "Images"?

[jim]

All images must be in the "media" directory of the store, which is a
subdirectory of the html output directory. That directory can not be
renamed. You can create subdirectories under the media directory but
images can not be outside of that directory structure. That being said
if you were to make the "media" directory a symlink to some other
directory you might be able to put your images in a different location
but they will always be referenced through the "media" directory.

Jim

Randall wrote:

When I browse for an image, SS shows only the Media directory and
those under it. (Due to the number of images, I'm limited to using the
pop-up window.) Can I configure SS so that it offers the root (or
store) directory and I navigate down from there?

If that's is possible, I'd prefer to be able to put images under the
html directories they serve, because that's the way the site I'm
converting to SS is currently set up.

If it's not possible, can I at least change the name of "Media"
directory to "Images"?

[Randall]

if you were to make the "media" directory a symlink

It sounds like that would just overlay one complication with yet
another, so I probably won't be trying that.

For future reference, though, what's a "symlink"? The term's not
found in the Help and Resource Center.

Somewhere there, I thought I understood that the Media directory might
be given another name during installation. I understand from the post
"Shopsite Data Directory" (May 10) that it *is* possible to install
the store in the root directory rather than the store directory, but
it has to be done during installation. Possibly the media directory
can be named "images" at that time, too?

I guess I understand why they call it "media" -- so that music files
can also go there, for example. I just don't understand why ShopSite
chose to lock in that unconventional terminology. After all, the 7.1
doc says "ShopSite does not have any buttons or other built-in
functions for using those files in your store"!

This may be academic in my case anyway. Verio says they may not be
willing to create a custom .auth file on a shared-hosting account.

I'm not usually so rigid, but in this case I'm trying to convert an
existing store from another cart, and would have preferred not to have
to revise every link, the directory architecture and install redirects
for visitors expecting to find pages elsewhere.

[jim]

See answers marked with ***** in message

Jim

Randall wrote:

if you were to make the "media" directory a symlink

It sounds like that would just overlay one complication with yet
another, so I probably won't be trying that.

For future reference, though, what's a "symlink"? The term's not
found in the Help and Resource Center.
***** a "symlink" is a symbolic link similar to a shortcut on a windows

system. It is a reference to another directory or file instead of
actually being the directory/file. You need server access to create one
so you couldn't do this on a Verio server.

Somewhere there, I thought I understood that the Media directory might
be given another name during installation. I understand from the post
"Shopsite Data Directory" (May 10) that it *is* possible to install
the store in the root directory rather than the store directory, but
it has to be done during installation. Possibly the media directory
can be named "images" at that time, too?
****** you can not rename the directory to "images" it has to be

"media". When installing you can specify directory paths for lots of
things but the pages will be generated with the authorized url specified
in the <storeid>.auth file so the url specified during install for the
output directory must match the auth file.

I guess I understand why they call it "media" -- so that music files
can also go there, for example. I just don't understand why ShopSite
chose to lock in that unconventional terminology. After all, the 7.1
doc says "ShopSite does not have any buttons or other built-in
functions for using those files in your store"!
***** yes it is "media" because it can contain images, music, video etc.

There is no built in way to create links to anything other than images
but you could do it with a custom template.

This may be academic in my case anyway. Verio says they may not be
willing to create a custom .auth file on a shared-hosting account.
***** The way the directory structure is configured on Verio's shared

servers it is not possible to have the store pages in the domains root
directory. You could have it configured this way on one of Verio's VPS
accounts. I don't know how much difference there is in cost between the
two type of accounts but it might be worth looking into.

I'm not usually so rigid, but in this case I'm trying to convert an
existing store from another cart, and would have preferred not to have
to revise every link, the directory architecture and install redirects
for visitors expecting to find pages elsewhere.
***** I understand your frustrations. If you are using ShopSite to

generate your pages it will revise the links for you.

[Randall]

***** a "symlink" is a symbolic link similar to a shortcut on a
windows system.

FWIW, the site's on a Unix box, so maybe .htaccess redirects would be
analogous? I can do that, but even if it would work, starting out with
everything based on a kludge doesn't seem wise.

****** pages will be generated with the authorized url specified in
the <storeid>.auth file so the url specified during install for the

Although Verio has been stubborn about it, I understand from them that
it *is* possible for them to change output directory specified in the
store's .auth file. I've understood the SS help doc correctly, each
store has it's own .auth spec, which I presume means even on a shared
server. So I'm still hopeful that they confirm that tomorrow. The
store has, after all, been a Verio customer for 6 years.

***** yes it is "media" because it can contain images, music, video
etc.
snip> but you could do it with a custom template.

In which case those other media could go anywhere, right? But that's a
relatively minor point, so I'll let that dog rest and put all the
images under "media".

***** The way the directory structure is configured on Verio's
shared servers it is not possible to have the store pages in the
domains root directory.

Odd. We've had the Mercantec store for 6 years, and the store has been
in the root directory all along. There's been a goofy need for a
splash page, but that's SoftCart, not Verio.

***** If you are using ShopSite to generate your pages it will
revise the links for you.

Thanks, but those aren't the links I meant. I meant people have
bookmarks, and search engines link to pages at the site (and we used
to have PPC links to them). Since those paths will all have changed,
I'll have to build .htacess redirects for all of them.

It's ironic. One reason I recommended we switch to SS is because of
its more robust and current marketing capabilities, and ultimately
easier updating. Instead, I'm having to deal with technical details I
really don't want to mess with. Technical simplicity, and cost, are
why I didn't move to a VPS account. (I'm not ruling out the
possibility of another SS provider, though.)

For now, I've managed to build a functioning customer-template store
page and may just swipe the SS code and hard code the whole site. Then
I can convert to dynamic SS a bit at a time.

Thanks.

[Randall]

Please let me amend a couple things...

I've understood the SS help doc

That should have read "If I've understood..."

The store has been a Verio customer for 6 years.

I didn't realize I'd said that twice, but maybe just as well, because
that's the basis of my kvetching. ShopSite continues to look like a
marvelous product from here, and appears infinitely better supported
by its publisher than the cart we've been using ever was. It's also
the choice of other hosting services that I have respect for.

For someone setting up a *new* store, ShopSite looks good right out of
the box.

However, when converting an store that was not laid out with ShopSite
in mind, these issues are complications that I hope could have been
avoided at set-up for an existing customer.

not ruling out the possibility of another SS provider

I would not leave Verio on the basis of this issue. Phone support has
been very good (that they offer it at all is a distinction) and email
support, although checkered, appears to be improving. However, matters
involving other sites, and recommendations of coworkers on those, keep
me "open minded" as to alternatives.

swipe the SS code and hard code the whole site

To be fair, if I recall correctly this was my original game plan and
may be why these issues didn't arise when I discussed our plans with
reps during the pre-sales process.