www.pudn.com > gmail-mobile-1.2.zip > SERVER_HELP
SERVER_HELP
This file includes previously reported server restrictions or
configuration problems and their solutions to help you get Gmail
Mobile working on almost any server.
If you need to use more than one solution, put ALL relevent lines into
the SAME .htaccess file.
After adding the relevent lines, if you get a "500 Internal Server Error"
then remove the .htaccess file or comment out the lines you added by placing
a "#" at the beginning:
# this line has been commented
this line is NOT commented
and then look for another server! ;-)
PHP Safe Mode
=============
There is no solution to this restriction. For full functionality of
gmail-mobile, another server WITHOUT PHP Safe Mode ON must be used.
PHP Safe Mode is a server's or admin's way to limit PHP functions
which can or are abused. This is common in shared server
environments, though, there are also many webhosts which do not place
this restriction on its users.
gmail-mobile tries to use only the most widely available and
compatible functions of PHP. Some of the latest, more advanced
features require a few PHP functions which may be restricted on
servers in safe mode.
The following features of Gmail will not work properly or at all.
Technical reasons are in [square brackets].
1) Loading the cURL extension it is not already loaded [dl() disabled]
2) Attachment downloading [fopen() and passthru() restricted]
3) PIN code signin [fopen() and unlink() restricted]
4) Login challenge, where gmail displays a graphic with characters to
be entered (future feature) [passthru() restricted]
5) Attachment upload (future feature) [fopen() and directory restrictions]
This is not an exhaustive list. All varieties of safe mode are not
created equal. A server may place additional or arbritrary
restrictions on certain php commands than the standard set. There may
also be hidden effects related to cURL.
Short Open Tags
(a.k.a. Require "