by dabempire | Feb 26, 2011 | Knowledgebase, Scripting (HTML, PHP, Perl/CGI)
Please login to your control panel and click on “security notes” in front of PHP4 Version in the left column. You can find all the details on how to make changes to php e.g. register_globals etc. In short, you need to use your own php.ini file in the folder where the php script executes. For php5, you can use one php.ini file in your public_html folder. For more details click on “Click to View” in front of PHP5 Version in your control panel. Note: This applies to all JaguarPC shared and semi-dedicated hosting accounts. You can download the stock version of php4 and php5 files from here as well: php4: http://www.jaguarpc.com/support/php4.txt php5: http://www.jaguarpc.com/support/php5.txt Please rename the file to php.ini and edit it to make changes to php settings. NOTE again for php4 that you need to place php.ini in the folder where php script executes. So if you place php.ini in public_html/ and your script executes at public_html/somefolder/ (or via web the address is http://www.example.com/somefolder/) then it will not load the php.ini settings. The php.ini file needs to be in public_html/somefolder/ as well. For php5, please place your php.ini in public_html and it will be used for all sub-foloders. IMPORTANT NOTE: you need to place entire php.ini file with all settings in it. You can not place just a few...
by dabempire | Feb 26, 2011 | Knowledgebase, Scripting (HTML, PHP, Perl/CGI)
This is because of the secure php environment on our servers (phpsuexec). This usually happens with OSCommerce and ZenCart web applications. You need to change the file permissions of configure.php to 440 using ssh. chmod 440 ~/path/to/configure.php And this warning will go...
by dabempire | Feb 26, 2011 | Knowledgebase, Scripting (HTML, PHP, Perl/CGI)
Here is a brief list of php4 modules that come standard with our shared/sdx/reseller servers: bcmath, calendar, ctype, curl, dom, domxml, exif, ftp, gd (with FreeType), gettext, iconv, imap, mbstring, mbregex, mcrypt, mhash, mm, mysql, mysqli, openssl, overload, pcre, pdflib, pear, posix, pspell, sablot, session, sockets, standard, tokenizer, wddx, xml, xmlrpc, xslt, zip, zlib – and Zend Optimizer php5 modules: bcmath, calendar, ctype, curl, date, dom, exif, filter, ftp, gd (with FreeType), gettext, hash, iconv, imap (with ssl), json, libxml, mbstring, mcrypt, mhash, mysql, mysqli, openssl, pcre, PDO, pdo_mysql, pdo_sqlite, posix, pspell, Reflection, session, SimpleXML, soap, sockets, SPL, SQLite, standard, tidy 2, tokenizer, wddx, xml, xmlreader, xmlrpc, xmlwriter, xsl, Zend Optimizer, zip, zlib. If you need any other module that is officially supported by php, or one of the above module is missing from your server, please open a support ticket and we can evaluate if it is possible to install...
by dabempire | Feb 26, 2011 | Knowledgebase, Scripting (HTML, PHP, Perl/CGI)
1. Upload your encoded RealAudio or RealVideo files (files with the .ra or .rm extensions) to your account. 2. Use a text editor (such as Notepad) to create a metafile containing a RealAudio URL. For example, the contents of your file should be in the following form: http://yourdomain.com/path/file.ra or http://yourdomain.com/path/file.rm where yourdomain.com is the name of your website here. 3. Save your metafile in as text using a .ram filename extension. 4. In your HTML document, reference the metafile in a hyperlink. For example: <A HREF=”filename.ram”> or <A HREF=”http://yourdomain.com/file.ram”> You can use relative or complete paths. If you use complete paths, you must include both the yourdomain.com and the complete path. For example: <A HREF=”http://yourdomain.com/directory/file.ram”> 5. When a user clicks on the link, the audio file(s) begin to download. The RealAudio Player begins playing after a few seconds; it does not need to wait for the entire file to be...
by dabempire | Feb 26, 2011 | Knowledgebase, Scripting (HTML, PHP, Perl/CGI)
One of the first things you must do when configuring a script, is set the correct path to the Perl interpreter, which is the engine responsible for processing the script. The path to Perl on our servers is: #!/usr/bin/perl