2005-08-21 10:51:35
When trying to run the accessibility checker on newly created page content I receive the following error message:
Error: Can't find file "http://www.chin.gc.ca:81/ATutor/get_acheck.php/48.html"
I wonder if this is related to the problem with I am having uploading themes - perhaps my ATutor installation is unable to write to these directories?
Any suggestions would be appreciated. Thanks.
2005-08-21 11:11:08
Is suspect based on your other posts that write permissions are not set properly on the content/ directory.
it should have been:
chmod -R a+rwx content/
The -R switch must be used, or you will not be able to write to sub directories.
2005-08-21 11:30:58
I have two installations of ATutor - XAMP and SunAMP.
I get this achecker error in both environments. I know that all directories are writable on the XP version as I was able to import themes etc. therefore I suspect file permissions are not the problem here.
Permit me to speculate a little..
The path in the error message looks odd in that get_acheck.php looks like a file not a directory name? Is 48.html supposed to be a querystring arg?
Thanks
2005-08-23 12:18:24
As suggested - rights were changed yet still same err msg when using Accessibility checker:
Error: Can\'t find file \"http://www.chin.gc.ca:81/ATutor/get_acheck.php/50.html\"
Platform specs:
OS - Solaris 2.8
PHP 4.3.8
Apache 2.0.49
MySQL 3.23.49
2005-08-23 15:12:42
I assume that Accessibility checker function builds the HTML file and then provides the url of the temporary HTML file to the Accessibilty checker web site?
If yes - then this external checking service would require access to this file at the stated URL. If the development environment is not accessible to the www then the checker would throw a file not found error correct? For me - both development environment are not directly accessible to www.
Am I totally out to lunch here?
2005-08-23 18:03:26
AChecker is a web service, so yes ATutor does need to be able to access the Web, and inturn AChecker needs to be able to access ATutor in order to do its work.
It sounds like there needs to be some more explanatory errors messages, or an easy way to disable the checker. You can disable it by commenting out the accessibility tab in the get_tabs () function in include/lib/editor_tab_functions.inc.php
At some point AChecker will be distributed publicly so you can install locally.
Same same will be true for the TILE repository, which also needs to be able to talk back and forth with ATutor and will eventually be distributed publicly.