next »

[greeves]

I've been unsuccessful in trying to determine why, on some machines, the Menu items (Grid, List, various views etc.) will resolve the pages successfully, while on others it won't. I've had two machines on the same LAN, side by side, both Win98 with one seeing everything, while the other sees only the main calendar, and gets the infamous "Page Cancelled" whenever an item from the menu is selected.  Has anyone else seen this happen? I've seen this happen on both Win98 and XP machines all running IE 6.0 or better.  I have to think it is a browser issue, but I'm at a loss to find where.

URL:  http://www.epschools.k12.oh.us/district/calendar.html  

Thanks.

greeves

[DanO]

** the Menu items will resolve the pages successfully **

What exactly do you mean by that?

** gets the infamous "Page Cancelled"  **

I've never heard of that message being displayed when using CalendarScript.

Dan O.

------------------

[greeves]

Actually, I should have said "Action Cancelled" or "Page cannot be displayed."  It's the message typically seen when the connection to the web server can't be established.  I have no trouble reaching other sites and resolving their pages on the machines in question.  And actually have no problem viewing the main calendar.  It is only when I choose to change view or login, that the error occurs.  I'm fairly certain that it is not a problem with the script, but with over 500 machines to support, I'd like all to be able to take full advantage of the calendar.  I've checked the network settings on the machines and all seems to be in order.

Thanks.

greeves

------------------

[DanO]

** It's the message typically seen when the connection to the web server can't be established. **

... if using Internet Explorer.

** It is only when I choose to change view or login, that the error occurs. **

Copy an offending link URL and paste it into a text editor (or here). Then do the same to a working calendar URL pasting it on the very next line. Compare them closely to see if you can see any differences (besides the obvious query string).

If you can't see any obvious problems, you may need to show them to the system administrator to see if they know why it is occurring. Maybe the network isn't accepting certain character combinations in a URL??

Dan O.

------------------

[greeves]

After some more investigation, with a variety of OS's both outside and inside the LAN, I've found that the browsers which are capable of properly displaying the various views within the calendar are handling the pages differently.  One thing is consistent, all can handle the first calendar, URL http://www.epschools.k12.oh.us/district/calendar.html   without difficulty.   The browsers which cannot move to different views or display other months are having the action cancelled.  They seem to be unable (or unwilling) to accept any URL such as http://epschools.k12.oh.us/cgi-bin/calendar.pl?style=List    On these systems, I have been able to force them to display the pages only after copying the shortcut and placing a www after the http:// in the address.   Is there a way of forcing the www in the address?

Thanks.

GReeves

------------------

[DanO]

** Is there a way of forcing the www in the address? **

You must have set up the calendar using the non-www... URL and that is what was stored in the configuration files.

You will need to manually edit the config.txt files located in the /calendarscript/ directory to correct the URLs recorded there. Either that or check with the network administrator to see if there's anything they can do which will allow the non-www... URLs to work.

Dan O.

------------------

[musicvid]

"One thing is consistent, all can handle the first calendar, URL http://www.epschools.k12.oh.us/district/calendar.html  without difficulty."

Then its most likely a DNS issue, esp. if your system maintains its own DNS server. Not too much experience with this, but I just went through an identical issue where the domain name was originally registered with the "www." as part of it, and wouldn't resolve on all browsers without it.

When you call up the domain without the "www." some browsers and nameservers will try to fill it in, others won't.

The solution is to have your sysadmin change the registration to resolve the name WITH or WITHOUT the "www." at the DNS level. (I think our registrar called it a "WWW A" tag, but I'm not sure.)

------------------

[This message has been edited by musicvid (edited May 20, 2004).]