TheunisP
Posts: 342
|
| Posted: 03/17/2011, 11:07 AM |
|
ok, this might not be what you want to hear but, your clienti18n.asp need that function at the bottom - your current common.asp has this line:
.PathRes = Server.MapPath(PagePathToRoot)
in the newer version of of CCS it was replaced with:
.PathRes = Server.MapPath("/Intranetb/")
the value being whatever the folder(s) is that you have in the Server URL
I think you might have a version of CCS that had a bug and it was never patched - the fix is either to directly fix the common.asp or uncomment the lines in the clienti18n.asp file
if you have access to CCS support, you can see if they have a patch for you - but there is no 2 ways about it - it is not the JS failing, it just doesn't load and the fact that the PagePathToRoot function is not defined is the reason for it not loading.
|
 |
 |
flipandboef
Posts: 107
|
| Posted: 03/17/2011, 11:13 AM |
|
So to be clear Theunis,
I uncomment in ClientI18N.asp:
'Function PagePathToRoot @0-FE5E6FF2
'Function PagePathToRoot
'PagePathToRoot = "./"
'End Function
'End Function PagePathToRoot
and in the Common.asp (on line 69):
.PathRes = Server.MapPath("intranet/123")
to:
.PathRes = Server.MapPath(PagePathToRoot)
So I understand this correctly? Or just 1 of them?
|
|
|
|
TheunisP
Posts: 342
|
| Posted: 03/17/2011, 11:19 AM |
|
no just one would work, either uncomment these lines not the start and end:
'Function PagePathToRoot
'PagePathToRoot = "./"
'End Function
to
Function PagePathToRoot
PagePathToRoot = "./"
End Function
or you change
.PathRes = Server.MapPath(PagePathToRoot)
to
.PathRes = Server.MapPath("/123/") ' my best guess without testing
------
but just uncomment the lines after publishing and test it
warning: generating & publishing you project might overwrite the changes e.g. the uncommenting at a later stage
|
|
|
|
flipandboef
Posts: 107
|
| Posted: 03/17/2011, 11:26 AM |
|
I've tried to uncomment the lines --> still the js error
Then tried changing the PathRes = Server.MapPath
1st tried: "/123/" as you suggested --> still error
then tried: "intranet/123/" and also "/intranet/123" --> still js error as well 
It's extremely strange isn't it?
|
|
|
|
TheunisP
Posts: 342
|
| Posted: 03/17/2011, 11:32 AM |
|
what happens when you run:
http://intranet/123/ClientI18N.asp?file=Functions.js&locale=en-US
do you see the javascript output, nothing or an error?
|
|
|
|
TheunisP
Posts: 342
|
| Posted: 03/17/2011, 11:59 AM |
|
the txt you sent, was it before or after you uncommented the lines?
|
|
|
|
flipandboef
Posts: 107
|
| Posted: 03/17/2011, 12:02 PM |
|
that was after uncommenting the lines
|
|
|
|
TheunisP
Posts: 342
|
| Posted: 03/17/2011, 12:19 PM |
|
ok does CC_FaqMaint.asp run and what does it do? e.g. is the JS binding the events etc
because I hope that, that is only because we called the internal file directly and not something else
I know we should have the same versions now - but a lot differs between our environment - e.g. how we setup IIS, our browsers etc.
The last way to go maybe to open a folder for us on the server uploading the files so we know that we at least work in the same server environment
|
|
|
|
flipandboef
Posts: 107
|
| Posted: 03/17/2011, 12:49 PM |
|
CC_FaqMaint.asp does run, but the confirmation on Delete does not show because of the JS error.
The record will be deleted however without this confirmation.
Adjusting the line that refers to the JS (taking out the ClientI18N in that line), results in a full working page, with the confirmation active.
Have a look at:
http://www.worldofrugs.com/123/CC_FaqList.asp
Son of a #$@#$%@$ There it's working!!! So it must be within the "Abyss webserver" that runs locally (Abyss always ran perfectly and was recommended by CodeCharge during ver. 3 for XP machines)
Well, at least we now (prob.) know, the issue is there, so now I'll have to figure out, why Abyss webserver behaves strangely now...
ps.: I feel now so dumb, that I never thought about this and to put it on another server....
Thanks for your help Theunis and I'm SOOO SORRY I made you waste all this time on CCS, while the issue is with Abyss somewhere...
|
|
|
|
TheunisP
Posts: 342
|
| Posted: 03/17/2011, 1:04 PM |
|
no probs - for the local server - throw this in an asp test file and run it - it should have some valid response - somewhere to start 
<%=Session.CodePage%>
|
|
|
|
TheunisP
Posts: 342
|
| Posted: 03/17/2011, 1:05 PM |
|
ps. you will find that the 1st error PagePathToRoot might exist on both, the Codepage error I thought might be due to the server - since you query the server for value - an invalid value points to a missing setting in the setup of the server
|
|
|
|
flipandboef
Posts: 107
|
| Posted: 03/17/2011, 1:07 PM |
|
Not 100% what that line should do, but I created a file and it shows:
0
on the page
|
|
|
|
TheunisP
Posts: 342
|
| Posted: 03/17/2011, 2:11 PM |
|
remember the last error you got? line 49 where the code is trying to set the codepage value
SessionObject- Error 'ASP 0204'
Invalid CodePage value
/123/ClientI18N.asp, line 49
An invalid CodePage value was specified.
ps. why don't you ask the boss just to upgrade - I have a fair idea it is going to save you a lot of time & trouble
|
|
|
|
flipandboef
Posts: 107
|
| Posted: 03/17/2011, 2:28 PM |
|
If only I could convince the cheap a..ho.. ehmmm my boss 
Still, as we discovered, the issue is somewhere with the Abyss webserver and NOT with CCS as I initially thought.
So upgrading to V.4 (yes I would wet my pants over it! hahaha), would still throw me errors I'm assuming...
I'll try to see if I can figure out the issue on the web-server part. If not... I guess I'll just throw everything over to a real IIS server (As this does work, as we noticed on our website-server)
OR
Just deal with it and change the call JS line (as this does seem to work as well)
Regardless,
I really would like to thank you Theunis, for all your help with this and the time you've spend on this!
Regards,
Paul R.
"Keep in Touch, with the Dutch!"
|
|
|
|
TheunisP
Posts: 342
|
| Posted: 03/17/2011, 3:24 PM |
|
no problem, was a pleasure - good luck with the rest of the project
regards
T
|
|
|
|
