Hi..
i need help on installing Magento at Mac OS X 10.4.
In MAMP i can run the Magento’s installer, but after that the pages of the frontstore, except for the homepage, are empty!
In XAMPP i can’t run the Magento’s installer because when i go to /localhost/magento/ i get a “500 Internal Server Error”
I have seen this problem with some other Zend Framework examples when trying to run them on os X. Somehow the paths get garbled. Mod_rewrite is enabled.
The requested URL /magento/install/ was not found on this server.
--so I added /magento between Documents/app in Mage.php
--Now it will get past the magento/install.php not found error
Instead will throw these errors which appear to be caused by doubling up the /magento/ in the path.
Warning: include(Mage/Core/functions.php) [function.include]: failed to open stream: No such file or directory in /Library/WebServer/Documents/magento/app/Mage.php on line 37
Warning: include(Mage/Core/functions.php) [function.include]: failed to open stream: No such file or directory in /Library/WebServer/Documents/magento/app/Mage.php on line 37
Warning: include() [function.include]: Failed opening ‘Mage/Core/functions.php’ for inclusion (include_path=’.:/usr/local/php5/lib/php:/Library/WebServer/Documents/magento/magento/lib:/Library/WebServer/Documents/magento/magento/app/code/core:’) in /Library/WebServer/Documents/magento/app/Mage.php on line 37
Fatal error: Class ‘Varien_Profiler’ not found in /Library/WebServer/Documents/magento/app/Mage.php on line 344
It happens to all scripts i’ve tried to install and only when i remove the .htaccess file it seems to work. So i suspect it is the mod rewrite module that is not working as expected.
I’ve heard only MAMP Pro version (commercial) seems to work fine though i haven’t tried it.
For everyone having the problem with “install directory not found” and using XAMPP on a Mac OSX, you have to enable .htaccess support by editing httpd.conf file in /Applications/xampp/etc/httpd.conf:
If the 302 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
Note: RFC 1945 and RFC 2068 specify that the client is not allowed
to change the method on the redirected request. However, most
existing user agent implementations treat 302 as if it were a 303
response, performing a GET on the Location field-value regardless
of the original request method. The status codes 303 and 307 have
been added for servers that wish to make unambiguously clear which
kind of reaction is expected of the client.
If the “http://pb3.local:80/magento/” or “http://localhost:80/magento/” is entered directly in a browser, the initial install screen displays.
Tried with three different browsers on os X, Opera 9.23, Safari 2.04, Firefox 2.0.0.6.
The “www” user in os X has RW access to the entire magento directory structure.
Edited php.ini and set “allow_url_fopen” and “allow_url_include” to “On”, did an “apachectl restart” and get:
Url “https://localhost:443/magento/” is not accessible
On the settings screen, changed the https info to “localhost” and “80”.
Now when I hit continue, it takes a while, but eventually get to a screen to enter login credentials. For the record, max_memory is set to 128M and max_execution is 30 in php.ini.
Entered all the info, everything seems to work well.
In my browser, browsed to “front-end”, browsed to “back-end” all works.
Then I set url_fopen and allow_url_include back to “Off” in php.ini, and magento still seems to be working. It sure looks pretty and loads like lightning on my local machine.
I run too many different experimental php scripts to feel good about leaving url_fopen set to “On”.
