Showing posts with label PHP. Show all posts
Showing posts with label PHP. Show all posts

2013-08-05

Disable Magic_quotes_gpc in PHP for Joomla 3.1 (Pair Networks)

Joomla logo
Joomla 3.1 requires that magic_quotes_qpc, a PHP setting, be turned off -- for a security reason related to PHP. As others have noted, this can be done in various ways --maddeningly -- depending on numerous configuration permutations.

How can you tell if it is turned off? Check phpinfo if the Joomla preinstallation checklist is not providing that information. 

At Pair networks, changing .htacesss and php.ini did not work. The web host technician advised using user.ini. It is worth reading the PHP documentation (and comments) regarding user.ini. This setting is apparently per-directory, in this documentation, but this StackOverflow post indicates user.ini works recursively. 

Whether this solution works for you depends on the specific configuration, so check that first.

The issue is broad in scope and complex, as pointed out in this lengthy and ongoing post by "AITPro Admin" titled "PHP5.3.X – PHP5.4.X .USER.INI FILE DOES NOT WORK – KNOWN PHP5.3.X .USER.INI FASTCGI WORDPRESS ZEND APACHE ISSUE."  Read this if you are contemplating a career in software and expect it to be smooth technology sailing.

2006-10-26

Open Source and the Easter Egg

My latest task was to be an easy one -- building the Apache - PHP stack for Windows 2003. "Easy," you think. "People are doing this thousands or hundreds of times a day." Very wrong, and yes I did know better.

The error I faced was this one:
  • Cannot load [path]php4apache2.dll into server. The specified file cannot be found.
Search on this error message and you'll see hundreds of instances dating back to 2004.

For the solution I attribute this Devside.net careful posting and bailout.

For a more animated expression of dismay, keep an eye out for the launch of errorprocessing.com. In the meantime, allow me to observe that in the relatively controlled environment of a Windows server, configuration management for the LAMP stack should be the responsibility of the folks at php.net. The information given there provides a hint, but not the solution.

And then there are dozens of misdirected suggestions, such as removing quotes around the pathname . . . This is not about assembling working components into working order. It's an Easter egg hunt, and one no self-respecting child would tolerate.