Hi Ludwig,

Here are a few things addressing your requests below:

1. Stop from getting logged out of the admin panel

See:  http://wiki.earlyimpact.com/widgets/thirdparty/adminsessionkeepalive?&#brief_summary" rel="nofollow - http://wiki.earlyimpact.com/widgets/thirdparty/adminsessionkeepalive?&#brief_summary

2. Extend the default date range for "view all orders"

In resultsAdvancedAll.asp, find:

if request("dd")="1" then dtFromDate=Date()-13

Replace the "-13" with the number of days you want to go back to on the report.

4. Edit order confirmation emails

See:  http://wiki.earlyimpact.com/widgets/thirdparty/htmlemails" rel="nofollow - http://wiki.earlyimpact.com/widgets/thirdparty/htmlemails

5. Make phone number required field on billing and shipping addresses

I had notes on this but lost them. I'll have this sorted out again in the next day or two and just edit the wiki for instructions. There definitely is an inconsistency here in that it's require if one goes straight to register an account, or if admin adds/edits a customer record: the phone field is required in those places, and in the latter situation there's a problem.

6. Make the comment box in 4.5 open by default so you don't have to click on it

Haven't had time to look at that one yet, but I agree that it would be the preferable default. It's been bothering me since 4.0, but I've just never had a moment it bothered me enough to go look into it.

Hi Ludwig,

I don't really see what difference it makes, but you could do it by editing the following files in the /pc/ folder:

atc_instprd.asp

Affgenlinks.asp

tellafriend.asp

pcSeoLinks.asp

I honestly don't see why this would be worth the effort, even with wanting to keep the extensions the same as with other pages. Honestly, though, who's really going to care?

On the generation side of it all, I believe the file list I mentioned should be complete. So, as long as everything on the link generation side uses .html and everything in 404.asp mirrors that, it should work.

The tricky part (or at least the part that would require experience) is with the trimming off the ".htm" parts of the process in 404.asp

For example:

' Trim Off .htm from Product ID  If ((Mid(intProductId,Len(intProductId),1)="m") And _ (Mid(intProductId,Len(intProductId)-1,1)="t") And _ (Mid(intProductId,Len(intProductId)-2,1)="h") And _ (Mid(intProductId,Len(intProductId)-3,1)=".")) Then intProductId = Left(intProductId,Len(intProductId)-4) End If

Instances of this procedure would need to be changed like so:

		' Trim Off .htm from Product ID
		If	((Mid(intProductId,Len(intProductId),1)="l") And _
			(Mid(intProductId,Len(intProductId)-1,1)="m") And _
			(Mid(intProductId,Len(intProductId)-2,1)="t") And _
			(Mid(intProductId,Len(intProductId)-3,1)="h") And _
			(Mid(intProductId,Len(intProductId)-4,1)=".")) Then
			intProductId = Left(intProductId,Len(intProductId)-5)
		End If

This would essentially tell IIS to look in a sub-directory which doesn't exist (very different than looking for a file that doesn't exist) and would have to be handled via URL rewriting or when the server.transfer occurs, it's going to load the page as if it were in the wrong directory. Here's an example for you:

http://pc45a-wms-net.3060.wmsmerchantservices.com/productcart/pc/my-prodname/" rel="nofollow - http://pc45a-wms-net.3060.wmsmerchantservices.com/productcart/pc/my-prodname/  

Here's an example of that sort of thing being handled just for a proper 404 handling page on a PC site:

http://www.nancyboy.com/my-prodname/" rel="nofollow - http://www.nancyboy.com/my-prodname/

First of all, in the interest of being "pretty", we've rewritten away the /productcart/pc/ sub-directories, and we've made sure that in our URL Rewriting we can find the correct locations for JavaScript libraries & such and assure that all of the images and CSS & links are called from the root on down, etc.

Now, imagine all of the work you'd have to do in addition to that if this were a category or product page. I dunno. I'd have to think about it a bit more an play with it.

That's not to say it can't be done. But that's about all the time I can give to it for now.

If you are super serious about it to the point of wanting to pay for a customization here, we could do it, but we'd most likely need to use URL rewriting inside IIS to avoid having to literally rewrite a whole lot of ProductCart.