continue shopping

[Ken Lanxner]

In the Return To Shopping Button option on the Commerce screen, can the
URL be dynamic? Can I use a VAR to get the user back to the product
page rather than More Info?

Or otherwise, is there a way to handle this? I've seena few posts here
about this but haven't spotted a solution. Customers will most
certainly get lost if Return to Shopping takes them to the More Info
page and they use the Back button or browser arrow. Is there a way to
tag the More Info page to display the link from its product page?

Thanks!

[Ken Lanxner]

Cancel that! I finally figured out how to get it working.

Ken

[Chris Moore]

And that solution was???
"Ken Lanxner" <ken@simplelives.com> wrote in message
news:050320041439133548%ken@simplelives.com...

Cancel that! I finally figured out how to get it working.

Ken

[Ken Lanxner]

In article <c2kskt$tt1$1@support.shopsite.com>,
"Chris Moore" <cmoore@alliancedatacom.com> wrote:

Cancel that! I finally figured out how to get it working.

And that solution was???

Sorry.

In my custom page template I assigned variables to the page name and URL:

[-- VAR.local PAGE.FileName --]
[-- VAR.local2 PAGE.Name --]

And in the More Info section of the product template, I use those
variables with:

<a href="[-- VAR.local --]">
Return to [--VAR.local2--]</a>

By the way, ShopSite helpers, if I have the same product on more than
one page, this doesn't always work. PAGE.FileName and PAGE.Name do not
seem to be read from the current page but from the database record
associated with that product. And apparently it uses the page on which
the product was first placed.

Am I right about that? Or maybe something wrong with the way I am using
these variables?

Thanks,
Ken

[Jim]

Ken Lanxner wrote:

In article <c2kskt$tt1$1@support.shopsite.com>,
"Chris Moore" <cmoore@alliancedatacom.com> wrote:


Cancel that! I finally figured out how to get it working.


And that solution was???


Sorry.

In my custom page template I assigned variables to the page name and URL:

[-- VAR.local PAGE.FileName --]
[-- VAR.local2 PAGE.Name --]

And in the More Info section of the product template, I use those
variables with:

a href="[-- VAR.local --]"
Return to [--VAR.local2--]</a

By the way, ShopSite helpers, if I have the same product on more than
one page, this doesn't always work. PAGE.FileName and PAGE.Name do not
seem to be read from the current page but from the database record
associated with that product. And apparently it uses the page on which
the product was first placed.

Am I right about that? Or maybe something wrong with the way I am using
these variables?

Thanks,
Ken

You are correct. There is only one moreinfo page for a product. It
gets generated the first time that a product is assigned to a page and
that page is generated. In your case it may get generated differently
if another page, that the product is assigned to, has something changed
and that page and the product have to be regenerate. But it will only
get generated once per any store publish.

Jim

[Ken Lanxner]

In article <c2lrd0$4mm$1@support.shopsite.com>,
Jim <jstavast@xmission.com> wrote:

You are correct. There is only one moreinfo page for a product. It
gets generated the first time that a product is assigned to a page and
that page is generated. In your case it may get generated differently
if another page, that the product is assigned to, has something changed
and that page and the product have to be regenerate. But it will only
get generated once per any store publish.

Thanks, Jim. So is there a better way to handle returning from a More
Info page than what I described in my previous message? Any way to work
around the single generation of a more info page?

I don't consider it a major problem if the shopper is "returned" to a
different page than she might have expected. Just curious to know if
there are better solutions than what I am using.

Ken

[Jim]

Ken Lanxner wrote:

In article <c2lrd0$4mm$1@support.shopsite.com>,
Jim <jstavast@xmission.com> wrote:


You are correct. There is only one moreinfo page for a product. It
gets generated the first time that a product is assigned to a page and
that page is generated. In your case it may get generated differently
if another page, that the product is assigned to, has something changed
and that page and the product have to be regenerate. But it will only
get generated once per any store publish.


Thanks, Jim. So is there a better way to handle returning from a More
Info page than what I described in my previous message? Any way to work
around the single generation of a more info page?

I don't consider it a major problem if the shopper is "returned" to a
different page than she might have expected. Just curious to know if
there are better solutions than what I am using.

Ken
You might be able to use some javascript to go back to the page you came

from using the history like the browser back button uses.

Jim

[Chris Moore]

Jim,

How can we tie the Jscript into the Continue Shopping button?

Chris
"Jim" <jstavast@xmission.com> wrote in message
news:c2m246$621$1@support.shopsite.com...

Ken Lanxner wrote:
In article <c2lrd0$4mm$1@support.shopsite.com>,
Jim <jstavast@xmission.com> wrote:


You are correct. There is only one moreinfo page for a product. It
gets generated the first time that a product is assigned to a page and
that page is generated. In your case it may get generated differently
if another page, that the product is assigned to, has something changed
and that page and the product have to be regenerate. But it will only
get generated once per any store publish.


Thanks, Jim. So is there a better way to handle returning from a More
Info page than what I described in my previous message? Any way to work
around the single generation of a more info page?

I don't consider it a major problem if the shopper is "returned" to a
different page than she might have expected. Just curious to know if
there are better solutions than what I am using.

Ken
You might be able to use some javascript to go back to the page you came
from using the history like the browser back button uses.

Jim

[Chris Moore]

On I usually use
<a href="javascript:history.go(-1)">Go Back</a>
or a variation of that. But I cant find a way to tie this into the "Continue
Shopping" button on the Shopping Cart. Is there a way?

Chris

"Chris Moore" <cmoore@alliancedatacom.com> wrote in message
news:c2nb8n$iv8$1@support.shopsite.com...

Jim,

How can we tie the Jscript into the Continue Shopping button?

Chris
"Jim" <jstavast@xmission.com> wrote in message
news:c2m246$621$1@support.shopsite.com...
Ken Lanxner wrote:
In article <c2lrd0$4mm$1@support.shopsite.com>,
Jim <jstavast@xmission.com> wrote:


You are correct. There is only one moreinfo page for a product. It
gets generated the first time that a product is assigned to a page and
that page is generated. In your case it may get generated differently
if another page, that the product is assigned to, has something
changed
and that page and the product have to be regenerate. But it will only
get generated once per any store publish.


Thanks, Jim. So is there a better way to handle returning from a More
Info page than what I described in my previous message? Any way to
work
around the single generation of a more info page?

I don't consider it a major problem if the shopper is "returned" to a
different page than she might have expected. Just curious to know if
there are better solutions than what I am using.

Ken
You might be able to use some javascript to go back to the page you came
from using the history like the browser back button uses.

Jim

[Jim]

I was thinking of the MoreInfo page not the shopping cart (that's what I
get for thinking after working hours .

I don't think this will work in the shopping cart because there can be
cases where the shopping cart is redirected back to itself. Like
Recalculate or coming from the registration screen. In those cases
history -1 wouldn't be the page the shopper came from would it?

Jim

Chris Moore wrote:

On I usually use
a href="javascript:history.go(-1)">Go Back</a
or a variation of that. But I cant find a way to tie this into the "Continue
Shopping" button on the Shopping Cart. Is there a way?

Chris

"Chris Moore" <cmoore@alliancedatacom.com> wrote in message
news:c2nb8n$iv8$1@support.shopsite.com...

Jim,

How can we tie the Jscript into the Continue Shopping button?

Chris
"Jim" <jstavast@xmission.com> wrote in message
news:c2m246$621$1@support.shopsite.com...

Ken Lanxner wrote:

In article <c2lrd0$4mm$1@support.shopsite.com>,
Jim <jstavast@xmission.com> wrote:



You are correct. There is only one moreinfo page for a product. It
gets generated the first time that a product is assigned to a page and
that page is generated. In your case it may get generated differently
if another page, that the product is assigned to, has something

changed

and that page and the product have to be regenerate. But it will only
get generated once per any store publish.


Thanks, Jim. So is there a better way to handle returning from a More
Info page than what I described in my previous message? Any way to

work

around the single generation of a more info page?

I don't consider it a major problem if the shopper is "returned" to a
different page than she might have expected. Just curious to know if
there are better solutions than what I am using.

Ken

You might be able to use some javascript to go back to the page you came
from using the history like the browser back button uses.

Jim

[Ken Lanxner]

In article <c2ni6a$kd1$1@support.shopsite.com>,
Jim <jstavast@xmission.com> wrote:

I was thinking of the MoreInfo page not the shopping cart (that's what I
get for thinking after working hours .

I don't think this will work in the shopping cart because there can be
cases where the shopping cart is redirected back to itself. Like
Recalculate or coming from the registration screen. In those cases
history -1 wouldn't be the page the shopper came from would it?

I assumed you meant use JS on the MoreInfo page and was about to answer
Chris when I saw your message to him. The script would need to send the
user back three pages in history. The cart is back one page and the
MoreInfo page itself is back two.

Ken

[Chris Moore]

Hey guys,

I could send them back 3 pages, no problem. But how do I tie the jscript
into the "Continue Shopping" button?

Chris


"Ken Lanxner" <ken@simplelives.com> wrote in message
news:ken-AF8DA5.14373010032004@news.shopsite.com...

In article <c2ni6a$kd1$1@support.shopsite.com>,
Jim <jstavast@xmission.com> wrote:

I was thinking of the MoreInfo page not the shopping cart (that's what I
get for thinking after working hours .

I don't think this will work in the shopping cart because there can be
cases where the shopping cart is redirected back to itself. Like
Recalculate or coming from the registration screen. In those cases
history -1 wouldn't be the page the shopper came from would it?

I assumed you meant use JS on the MoreInfo page and was about to answer
Chris when I saw your message to him. The script would need to send the
user back three pages in history. The cart is back one page and the
MoreInfo page itself is back two.

Ken

[Ken Lanxner]

In article <c2puuh$9eg$1@support.shopsite.com>,
"Chris Moore" <cmoore@alliancedatacom.com> wrote:

I could send them back 3 pages, no problem. But how do I tie the jscript
into the "Continue Shopping" button?

You will get a more authoritative answer from the ShopSite gurus. But I
would guess that you can't modify the action on the Continue Shopping
button. But if Continue Shopping takes the customer back to the MoreInfo
page, you can use js on that page to direct them elsewhere.

Ken

[loren_d_c]

You can easily change the Continue Shopping button via a custom shopping
cart template in ShopSite v7 (and by being tricky in v6, i.e. use an
invisible gif for the regular Continue Shopping button and putting your
custom one in one of the Preferences -> Store Text -> Shopping Cart
fields that show up on the cart screen somewhere within the form tags).

However I do not believe this is really a good direction to go with this
to get the results you want, you cannot guarantee what page is one, two,
three, etc back in the browser history. The shopper may have gone to the
checkout screen and then hit the return to cart button. Two back in the
history from that point would likely just put you right back on the
shopping cart screen (which would probably confuse the heck out of a
shopper). Or they could have entered their zip code or changed a
quantity or selected a shipping option, and then hit the recalculate
button (and recalculated any number of times). Etc etc.

-Loren



Ken Lanxner wrote:

In article <c2puuh$9eg$1@support.shopsite.com>,
"Chris Moore" <cmoore@alliancedatacom.com> wrote:


I could send them back 3 pages, no problem. But how do I tie the jscript
into the "Continue Shopping" button?


You will get a more authoritative answer from the ShopSite gurus. But I
would guess that you can't modify the action on the Continue Shopping
button. But if Continue Shopping takes the customer back to the MoreInfo
page, you can use js on that page to direct them elsewhere.

Ken

[loren_d_c]

"and by being tricky in v6, i.e. use an invisible gif for the regular
Continue Shopping button and putting your custom one in one of the
Preferences -> Store Text -> Shopping Cart fields that show up on the
cart screen somewhere within the form tags"

Actually, I guess if your 'new' Continue Shopping button was not
submitting to the ShopSite form action, then you are not confined to
fields that appear within the form tags. I guess I was just thinking of
people who wanted to move the Continue Shopping button up higher in the
screen but keep the same functionality.

-Loren


Loren wrote:

You can easily change the Continue Shopping button via a custom shopping
cart template in ShopSite v7 (and by being tricky in v6, i.e. use an
invisible gif for the regular Continue Shopping button and putting your
custom one in one of the Preferences -> Store Text -> Shopping Cart
fields that show up on the cart screen somewhere within the form tags).

However I do not believe this is really a good direction to go with this
to get the results you want, you cannot guarantee what page is one, two,
three, etc back in the browser history. The shopper may have gone to the
checkout screen and then hit the return to cart button. Two back in the
history from that point would likely just put you right back on the
shopping cart screen (which would probably confuse the heck out of a
shopper). Or they could have entered their zip code or changed a
quantity or selected a shipping option, and then hit the recalculate
button (and recalculated any number of times). Etc etc.

-Loren



Ken Lanxner wrote:

In article <c2puuh$9eg$1@support.shopsite.com>,
"Chris Moore" <cmoore@alliancedatacom.com> wrote:


I could send them back 3 pages, no problem. But how do I tie the jscript
into the "Continue Shopping" button?



You will get a more authoritative answer from the ShopSite gurus. But
I would guess that you can't modify the action on the Continue
Shopping button. But if Continue Shopping takes the customer back to
the MoreInfo page, you can use js on that page to direct them elsewhere.

Ken