 |


buy now |
download |
support |
forum |
user survey |
user guide |
testimonials |
version history |
news2me
AdminPro User Guide
AdminPro Troubleshooting FAQ
AdminPro is designed to be as simple to install and use as possible. However, some users have encountered difficulties that are often quickly resolved by going through the following items:
Invoking AdminPro results in a "server 500 error" What can I do?
Your server's path to Perl must be set correctly in the "adminpro.cgi" and "adminpro-u.cgi" documents. Most administrators have located it at "/usr/bin/perl" or "/usr/local/bin/perl" Just copy the first line from a CGI script that is known to be working on your server and paste it into the first line of the "adminpro.cgi" and "adminpro-u.cgi" CGI documents.
For Windows servers: The "properties" for the "adminpro.cgi" program may need to be set as executable by your server administrator.
Just as with HTML and other text files, Perl scripts must be uploaded to the server in "ASCII text mode" rather than binary. Many FTP clients, in "auto" or "intelligent" mode, do not correctly upload in "text" mode so you may have to "force an ASCII text mode" upload for both the "adminpro-u.cgi" and "adminpro.txt" documents.
File permissions for the "adminpro.cgi" and "adminpro-u.cgi" script should be 755 (world executable).
It's been reported that, after extraction of the "adminpro-u.cgi" document by some desktop zip extraction utilities, the end of line string (CR LF) may be stripped or corrupted To remedy this issue, download the uncompressed document.
Your server may not be set to execute files with a ".cgi" extension and you may need to change the name of the "adminpro.cgi" and "adminpro-u.cgi" file to a common alternative such as "adminpro.pl" or "adminpro.plx" just note the extension on any other CGIs known to be working on your server and give that a try.
Some servers are configured by your server administrator to only execute scripts located in the /cgi-bin On such servers, a script located anywhere else may not execute.
When attempting to invoke AdminPro, I get an "Application Access Error" page.
AdminPro's optional Access-Restriction feature can help ensure AdminPro's powerful functions are not accessed by users you haven't authorized. If incorrectly configured, however, it will prevent your access to AdminPro altogether.
Within the "adminpro.txt" document in the "Access Restriction" section of User Preferences, you'll see there are two steps: 1) provide the static IP Address of all authorized users and 2) turn on access restriction.
If you do not have a static IP Address for the computer from which you administrate your website, you cannot use the Access-Restriction feature and you must leave Step 2 turned off (0).
If you have a static IP Address but can't remember it, leave the Access-Restriction featured turned off, upload and invoke AdminPro. Your IP Address is reported in the top-left corner of the AdminPro interface in your browser window.
If you can invoke AdminPro operating in "default" mode without encountering that error page, but get that error when switching to "administrator" mode, your server administrator may not have authorized you to use AdminPro in "administrator" mode on that server. Toggle the mode preference back to "default" or contact your server administrator to add you to the list of users who can use AdminPro in "administrator" mode.
Note: AdminPro is a powerful administrative tool NEVER link to your "adminpro.cgi" application from a publicly-accessible page as the security of your domain and the server itself could be compromised. Further, we suggest checking with your server administrator before uploading AdminPro to a virtual domain (not your own in-house or dedicated server) as use of this application may represent a compromise of the security of your domain and the server in general.
If you do not have a specific need nor authority to navigate the server beyond your domain, we encourage you to leave the AdminPro mode preference set to "default."
The size of the file editing box is too large/small for my monitor.
You may increase or decrease the default settings for the width and height of that textarea form field on the Text File Edit page by opening the adminpro.txt document on your local desktop in Notepad, SimpleText or other ASCII text editor. Modify the defaults for the width and height options in the User Preferences section. Then just re-upload adminpro.txt overwriting the original version.
When I click on the "download" icon, I am not automatically prompted to save the file and, when I right click to "save this link as..." the file I'm downloading does not have the correct file name in Internet Explorer.
While Netscape browsers seem to respond appropriately to the download function and prompts users to save the file, Microsoft is aware of these bugs in Internet Explorer versions 4x and 5x and they claim to have resolved them in Internet Explorer 6. Read more about these issues here and here at the Microsoft Knowledge Base. A workaround is to right-click on the "file download" icon, choose "download link to disk" and, when prompted, change the file name to the correct filename.ext.
When I run AdminPro, it reports no paths and no files It doesn't even see itself.
Some server administrators set up the /cgi-bin/ path or other directories and files as symbolic links (aliases) for some added security. They may also be using CGIwrap which can prevent AdminPro from seeing and, therefore, testing your CGIs. The ability to perform in such environments is the primary reason to run AdminPro in "administrator" mode. Open the adminpro.txt document and toggle the mode from default mode (0) to administrator mode (1). Re-upload the adminpro.txt file overwriting the original the invoke AdminPro again in your browser.
If the expected paths and files still do not display, you may be able to click on the navigation links in the top left corner of the AdminPro directory table to traverse up the path tree "behind your domain root" then back down into the actual path containing your website content where your files will be visible.
If your files and folders still
fail to display, contact your server administrator for a way to allow AdminPro to debug your scripts without compromising the server's security.
|
|
|
 |