pommehomme wrote on Saturday, June 12, 2010:
I am a surgeon and reasonably familiar with the Mac OS. I can use the command line interface but am a noobie there. I would love to install OpenEMR on my exclusively Mac office but need a little assistance: I have downloaded Open EMR 3.2.0 and XAMPP for Mac. If someone can give me directions on the best way to proceed, I am good at following directions and would love to be able to contribute to the OpenEMR project.
Thanks in advance!
pommehomme
pommehomme wrote on Sunday, June 13, 2010:
Okay, I have made some progress to the OpenEMR Setup Screen. This is where I am stuck because of the following messages:
UNABLE to open directory ‘’ for writing by web server.
(configure directory permissions; see below for further instructions)
UNABLE to open directory ‘’ for writing by web server.
(configure directory permissions; see below for further instructions)
What is the directory "?
Seems like I am close…but not there yet.
ytiddo wrote on Sunday, June 13, 2010:
Pardon me if this advice is completely wrong, its quite possible i’m the blind leading the blind. 
I would say look though interface/globals.php. there is a section in there for finding the webroot. see where that’s pointing to.
since you’ve got the setup page to open, can you quote the page in its entirety? the context of where these errors are popping up may be important.
pommehomme wrote on Sunday, June 13, 2010:
Here is the setup page:
OpenEMR Setup
Welcome to OpenEMR. This utility will step you through the installation and configuration of OpenEMR for your practice.
* Before proceeding, be sure that you have a properly installed and configured MySQL server available, and a PHP configured webserver.
* Detailed installation instructions can be found in the ‘INSTALL’ manual file.
* If you are upgrading from a previous version, do NOT use this script. Please read the ‘Upgrading’ section found in the ‘INSTALL’ manual file.
We will now ensure correct file and directory permissions before starting installation:
Ensuring following files are world-writable…
‘/Applications/XAMPP/xamppfiles/htdocs/library/sqlconf.php’ file is ready.
‘/Applications/XAMPP/xamppfiles/htdocs/interface/globals.php’ file is ready.
Ensuring following directories have proper permissions…
‘/Applications/XAMPP/xamppfiles/htdocs/documents’ directory is ready.
UNABLE to open directory ‘’ for writing by web server.
(configure directory permissions; see below for further instructions)
UNABLE to open directory ‘’ for writing by web server.
(configure directory permissions; see below for further instructions)
‘/Applications/XAMPP/xamppfiles/htdocs/library/freeb’ directory is ready.
‘/Applications/XAMPP/xamppfiles/htdocs/custom/letter_templates’ directory is ready.
‘/Applications/XAMPP/xamppfiles/htdocs/gacl/admin/templates_c’ directory is ready.
‘/Applications/XAMPP/xamppfiles/htdocs/interface/main/calendar/modules/PostCalendar/pntemplates/compiled’ directory is ready.
‘/Applications/XAMPP/xamppfiles/htdocs/interface/main/calendar/modules/PostCalendar/pntemplates/cache’ directory is ready.
You can’t proceed until all directories are ready.
In linux, recommend changing owners of these directories to the web server. For example, in many linux OS’s the web server user is ‘apache’, ‘nobody’, or ‘www-data’. So if ‘apache’ were the web server user name, could use the command ‘chown -R apache:apache directory_name’ command.
Fix above directory permissions and then click the ‘Check Again’ button to re-check directories.
ytiddo wrote on Sunday, June 13, 2010:
Reading through the installation guide, the screenshot there shows that those directories are for edi and era.
edi and era are directories for containing billing files (remittances and such), and you will need to have them writeable.
I can’t really advise why openemr is not coming up with a name for the path to those directories.
pommehomme wrote on Sunday, June 13, 2010:
OK, I didn’t have the edi and era directories in the correct place. Did that and got further…here is where I am stuck now:
OpenEMR Setup
Step 3
Configuring OpenEMR…
Connecting to MySQL Server… OK.
Creating database… ERROR. Check your login credentials.
Can’t create database ‘openemr’; database exists (#1007)
pommehomme wrote on Sunday, June 13, 2010:
Now I have gotten as far as panel 6: configuring the APACHE server. Please advise…I’m really close now!!
bradymiller wrote on Monday, June 14, 2010:
Just copy/paste the code on this screen to bottom of your apache configuration file (check out xampp documentation to find out where it’s kept). Then re-start the apache server. If this works for you, would be nice to document it:
http://www.openmedsoftware.org/wiki/OpenEMR_Installation_Guides
To make it easier for you, just let me know what you needed to do at each step in the folllowing instructions:
http://www.openmedsoftware.org/wiki/OpenEMR_3.2_Linux_Installation
I then gladly merge your isntructions with above to make an OS-X install with screenshots.
-brady
pommehomme wrote on Monday, June 14, 2010:
It appears my apache configuration file was in Applications>XAMPP>xamppfiles>etc>httpd.conf. I gave myself read and write permissions, opened in TextEdit and added:
<Directory /Applications/XAMPP/xamppfiles/htdocs/documents>
order deny,allow
Deny from all
</Directory>
<Directory /Applications/XAMPP/xamppfiles/htdocs/edi>
order deny,allow
Deny from all
</Directory>
<Directory /Applications/XAMPP/xamppfiles/htdocs/era>
order deny,allow
Deny from all
</Directory>
to the end of the file. When I try to save the changes, I get this message:
The document “httpd.conf” could not be saved.
What am I doing wrong?
Thanks for EVERYONE’S HELP!!!
pommehomme wrote on Monday, June 14, 2010:
So close!!!
Changed permissions for the etc directory to let me read and write. Then I was able to add the above at the end of the apache configuration file and save the changes. When I tried to restart the APACHE server I got this error message:
SYNTAX ERROR!
httpd: Syntax error on line 502 of /Applications/XAMPP/xamppfiles/etc/httpd.conf: /Applications/XAMPP/xamppfiles/etc/httpd.conf:502: <Directory> was not closed.
Huh?
visolveemr wrote on Monday, June 14, 2010:
Hi,
Please check the ‘Directory’ configuration in httpd.conf file. Probably this could be due to the improper closing of <Directory> tag.
Please paste the contents of httpd.conf here or else send the same to vicareplus_support@visolve.com for better evaluation.
Thanks,
Vicareplus Team,
www.vicareplus.com
pommehomme wrote on Tuesday, June 15, 2010:
Will do later this evening.
Also, should I copy ALL files in the OpenEMR folder to the XAMPP folder? If so, where should they go? I still have a number of items left in the OpenEMR folder.
pommehomme wrote on Tuesday, June 15, 2010:
Reply to #11:
#
# This is the main Apache HTTP server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do. They’re here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server’s control files begin with “/” (or “drive:/” for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with “/”, the value of ServerRoot is prepended - so “logs/foo.log”
# with ServerRoot set to “/Applications/xampp/xamppfiles” will be interpreted by the
# server as “/Applications/xampp/xamppfiles/logs/foo.log”.
#
# ServerRoot: The top of the directory tree under which the server’s
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path. If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk. If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
#
ServerRoot “/Applications/XAMPP/xamppfiles”
#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 12.34.56.78:80
Listen 80
#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule’ lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l’) do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
LoadModule authn_file_module modules/mod_authn_file.so
LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_anon_module modules/mod_authn_anon.so
LoadModule authn_dbd_module modules/mod_authn_dbd.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule auth_basic_module modules/mod_auth_basic.so
LoadModule auth_digest_module modules/mod_auth_digest.so
LoadModule file_cache_module modules/mod_file_cache.so
LoadModule cache_module modules/mod_cache.so
LoadModule disk_cache_module modules/mod_disk_cache.so
LoadModule mem_cache_module modules/mod_mem_cache.so
LoadModule dbd_module modules/mod_dbd.so
LoadModule bucketeer_module modules/mod_bucketeer.so
LoadModule dumpio_module modules/mod_dumpio.so
LoadModule echo_module modules/mod_echo.so
LoadModule case_filter_module modules/mod_case_filter.so
LoadModule case_filter_in_module modules/mod_case_filter_in.so
LoadModule ext_filter_module modules/mod_ext_filter.so
LoadModule include_module modules/mod_include.so
LoadModule filter_module modules/mod_filter.so
LoadModule charset_lite_module modules/mod_charset_lite.so
LoadModule deflate_module modules/mod_deflate.so
LoadModule ldap_module modules/mod_ldap.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule logio_module modules/mod_logio.so
LoadModule env_module modules/mod_env.so
LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule expires_module modules/mod_expires.so
LoadModule headers_module modules/mod_headers.so
LoadModule ident_module modules/mod_ident.so
LoadModule usertrack_module modules/mod_usertrack.so
LoadModule unique_id_module modules/mod_unique_id.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule mime_module modules/mod_mime.so
LoadModule dav_module modules/mod_dav.so
LoadModule status_module modules/mod_status.so
LoadModule autoindex_module modules/mod_autoindex.so
LoadModule asis_module modules/mod_asis.so
LoadModule info_module modules/mod_info.so
LoadModule suexec_module modules/mod_suexec.so
LoadModule cgi_module modules/mod_cgi.so
LoadModule cgid_module modules/mod_cgid.so
LoadModule dav_fs_module modules/mod_dav_fs.so
LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule dir_module modules/mod_dir.so
LoadModule imagemap_module modules/mod_imagemap.so
LoadModule actions_module modules/mod_actions.so
LoadModule speling_module modules/mod_speling.so
LoadModule userdir_module modules/mod_userdir.so
LoadModule alias_module modules/mod_alias.so
LoadModule rewrite_module modules/mod_rewrite.so
#LoadModule apreq_module modules/mod_apreq2.so
LoadModule ssl_module modules/mod_ssl.so
<IfDefine JUSTTOMAKEAPXSHAPPY>
LoadModule php4_module modules/libphp4.so
LoadModule php5_module modules/libphp5.so
</IfDefine>
<IfModule !mpm_winnt_module>
<IfModule !mpm_netware_module>
#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User nobody
Group nogroup
</IfModule>
</IfModule>
# ‘Main’ server configuration
#
# The directives in this section set up the values used by the ‘main’
# server, which responds to any requests that aren’t handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#
#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents. e.g. admin@your-domain.com
#
ServerAdmin you@example.com
#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn’t have a registered DNS name, enter its IP address here.
#
#ServerName www.example.com:80
# XAMPP
ServerName localhost
#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot “/Applications/XAMPP/xamppfiles/htdocs”
#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the “default” to be a very restrictive set of
# features.
#
<Directory />
Options FollowSymLinks
AllowOverride None
#XAMPP
#Order deny,allow
#Deny from all
</Directory>
#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something’s not working as
# you might expect, make sure that you have specifically enabled it
# below.
#
#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory “/Applications/XAMPP/xamppfiles/htdocs”>
#
# Possible values for the Options directive are “None”, “All”,
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that “MultiViews” must be named *explicitly* – “Options All”
# doesn’t give it to you.
#
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs/2.2/mod/core.html#options
# for more information.
#
Options Indexes FollowSymLinks ExecCGI Includes
#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be “All”, “None”, or any combination of the keywords:
# Options FileInfo AuthConfig Limit
#
AllowOverride All
#
# Controls who can get stuff from this server.
#
Order allow,deny
Allow from all
</Directory>
#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
DirectoryIndex index.html index.php index.htmls index.htm
</IfModule>
#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch “^\.ht”>
Order allow,deny
Deny from all
</FilesMatch>
#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host’s errors will be logged there and not here.
#
ErrorLog logs/error_log
#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn
<IfModule log_config_module>
#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
#
LogFormat “%h %l %u %t “%r” %>s %b “%{Referer}i” “%{User-Agent}i”” combined
LogFormat “%h %l %u %t “%r” %>s %b” common
<IfModule logio_module>
# You need to enable mod_logio.c to use %I and %O
LogFormat “%h %l %u %t “%r” %>s %b “%{Referer}i” “%{User-Agent}i” %I %O” combinedio
</IfModule>
#
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here. Contrariwise, if you *do*
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and *not* in this file.
#
CustomLog logs/access_log common
#
# If you prefer a logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#
#CustomLog logs/access_log combined
</IfModule>
<IfModule alias_module>
#
# Redirect: Allows you to tell clients about documents that used to
# exist in your server’s namespace, but do not anymore. The client
# will make a new request for the document at its new location.
# Example:
# Redirect permanent /foo http://www.example.com/bar
#
# Alias: Maps web paths into filesystem paths and is used to
# access content that does not live under the DocumentRoot.
# Example:
# Alias /webpath /full/filesystem/path
#
# If you include a trailing / on /webpath then the server will
# require it to be present in the URL. You will also likely
# need to provide a <Directory> section to allow access to
# the filesystem path.
#
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the target directory are treated as applications and
# run by the server when requested rather than as documents sent to the
# client. The same rules about trailing “/” apply to ScriptAlias
# directives as to Alias.
#
ScriptAlias /cgi-bin/ “/Applications/XAMPP/xamppfiles/cgi-bin/”
</IfModule>
<IfModule cgid_module>
#
# ScriptSock: On threaded servers, designate the path to the UNIX
# socket used to communicate with the CGI daemon of mod_cgid.
#
#Scriptsock logs/cgisock
</IfModule>
#
# “/Applications/xampp/xamppfiles/cgi-bin” should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory “/Applications/XAMPP/xamppfiles/phpmyadmin”>
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>
#
# DefaultType: the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, “text/plain” is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use “application/octet-stream” instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain
<IfModule mime_module>
#
# TypesConfig points to the file containing the list of mappings from
# filename extension to MIME-type.
#
TypesConfig etc/mime.types
#
# AddType allows you to add to or override the MIME configuration
# file specified in TypesConfig for specific file types.
#
#AddType application/x-gzip .tgz
#
# AddEncoding allows you to have certain browsers uncompress
# information on the fly. Note: Not all browsers support this.
#
#AddEncoding x-compress .Z
#AddEncoding x-gzip .gz .tgz
#
# If the AddEncoding directives above are commented-out, then you
# probably should define those extensions to indicate media types:
#
AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz
#
# AddHandler allows you to map certain file extensions to “handlers”:
# actions unrelated to filetype. These can be either built into the server
# or added with the Action directive (see below)
#
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add “ExecCGI” to the “Options” directive.)
#
#AddHandler cgi-script .cgi
AddHandler cgi-script .cgi .pl
# For files that include their own HTTP headers:
#AddHandler send-as-is asis
# For server-parsed imagemap files:
#AddHandler imap-file map
# For type maps (negotiated resources):
#AddHandler type-map var
#
# Filters allow you to process content before it is sent to the client.
#
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add “Includes” to the “Options” directive.)
#
AddType text/html .shtml
AddOutputFilter INCLUDES .shtml
</IfModule>
#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
#MIMEMagicFile etc/magic
#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 “The server made a boo boo.”
#ErrorDocument 404 /missing.html
#ErrorDocument 404 “/cgi-bin/missing_handler.pl”
#ErrorDocument 402 http://www.example.com/subscription_info.html
#
#
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall is used to deliver
# files. This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
#
EnableMMAP off
EnableSendfile off
# Supplemental configuration
#
# The configuration files in the /Applications/xampp/etc/extra/ directory can be
# included to add extra features or to modify the default configuration of
# the server, or you may simply copy their contents here and change as
# necessary.
# Server-pool management (MPM specific)
#Include /Applications/XAMPP/etc/extra/httpd-mpm.conf
# Multi-language error messages
Include /Applications/XAMPP/etc/extra/httpd-multilang-errordoc.conf
# Fancy directory listings
#Include /Applications/XAMPP/etc/extra/httpd-autoindex.conf
# Language settings
#Include /Applications/XAMPP/etc/extra/httpd-languages.conf
# User home directories
Include /Applications/XAMPP/etc/extra/httpd-userdir.conf
# Real-time info on requests and configuration
#Include /Applications/XAMPP/etc/extra/httpd-info.conf
# Virtual hosts
#Include /Applications/XAMPP/etc/extra/httpd-vhosts.conf
# Local access to the Apache HTTP Server Manual
#Include /Applications/XAMPP/etc/extra/httpd-manual.conf
# Distributed authoring and versioning (WebDAV)
#Include /Applications/XAMPP/etc/extra/httpd-dav.conf
# Various default settings
#Include /Applications/XAMPP/etc/extra/httpd-default.conf
# Secure (SSL/TLS) connections
#Include /Applications/XAMPP/etc/extra/httpd-ssl.conf
<IfModule ssl_module>
<IfDefine SSL>
Include etc/extra/httpd-ssl.conf
</IfDefine>
</IfModule>
#
# Note: The following must must be present to support
# starting without SSL on platforms with no /dev/random equivalent
# but a statically compiled-in mod_ssl.
#
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>
#XAMPP
Include etc/extra/httpd-xampp.conf
pommehomme wrote on Tuesday, June 15, 2010:
After doing a lot of reading, I decided to start over. I have moved all the OpenEMR files into the XAMPP folder (directory, sorry) and given myself read and write permissions for the XAMPPfiles directory, but still get:
OpenEMR Setup
Welcome to OpenEMR. This utility will step you through the installation and configuration of OpenEMR for your practice.
* Before proceeding, be sure that you have a properly installed and configured MySQL server available, and a PHP configured webserver.
* Detailed installation instructions can be found in the ‘INSTALL’ manual file.
* If you are upgrading from a previous version, do NOT use this script. Please read the ‘Upgrading’ section found in the ‘INSTALL’ manual file.
We will now ensure correct file and directory permissions before starting installation:
Ensuring following files are world-writable…
UNABLE to open file ‘/Applications/XAMPP/xamppfiles/htdocs/library/sqlconf.php’ for writing.
(configure file permissions; see below for further instructions)
UNABLE to open file ‘/Applications/XAMPP/xamppfiles/htdocs/interface/globals.php’ for writing.
(configure file permissions; see below for further instructions)
You can’t proceed until all above files are ready (world-writable).
In linux, recommend changing file permissions with the ‘chmod 666 filename’ command.
Fix above file permissions and then click the ‘Check Again’ button to re-check files.
bradymiller wrote on Tuesday, June 15, 2010:
hey,
You should basically move the entire openemr folder into the web directory (which you have done). Since your starting over, read through the linux instructions (OS-X will be very similar):
http://www.openmedsoftware.org/wiki/OpenEMR_3.2_Linux_Installation
As I recall, the file permissions are where some os-x users have had problems in the past. Apache is the “user” that needs write access to these files and folders (see linux link above for full listing, and I’d suggest trying these commands with the osx apache user). To get the user type ‘ps -aux’ in console and see which user owns the httpd.conf processes.
-brady
pommehomme wrote on Tuesday, June 15, 2010:
This time I flew through the installation by changing permissions in Terminal for all directories that needed changing with chmod 666 <directory> and got to the screen that said openemr had been successfully installed. Restarted XAMPP Apache server and clicked link to start openemr…this is what I got:
It Works!
What did I miss…seems like I am so close…
bradymiller wrote on Tuesday, June 15, 2010:
Ensure you point to your web browser to directory where openemr is (where you were running the setup.php script from).
-brady
bradymiller wrote on Tuesday, June 15, 2010:
hey,
move the index.html file from /Applications/XAMPP/xamppfiles/htdocs/ to somewhere else (apache is defaulting to running this over the openemr index.php file)
-brady
pommehomme wrote on Wednesday, June 16, 2010:
Thanks, brady. I installed again with no problem on a PowerMac running 10.6.3. setup.php says openemr is installed. but when I point firefox to http://localhost/openemr, I get:
Object not found!
The requested URL was not found on this server. If you entered the URL manually please check your spelling and try again.
If you think this is a server error, please contact the webmaster.
Error 404
localhost
Tue Jun 15 21:45:49 2010
Apache/2.2.14 (Unix) DAV/2 mod_ssl/2.2.14 OpenSSL/0.9.8l PHP/5.3.1 mod_perl/2.0.4 Perl/v5.10.1
I moved the index.http file out of htdocs. I hope it was the correct one, as there are a number of them. When I copied the openemr folder contents to the xampp htdocs folder, it asked if I wanted to replace the index.html with the one I was copying. Figuring that the one I was copying was from openemr, I said yes.
So now I have been able to install successfully on two Macs with OS10.6.3, but can’t find it!!
visolveemr wrote on Wednesday, June 16, 2010:
Hi,
Please paste the contents of apache error log file. It seems the error related to configuration of the relative path and web root directory path to be given in interface/globals.php file. Could you please paste the web-root variable from interface/globals.php?
Please refer following thread where the similar issue is discussed
http://sourceforge.net/projects/openemr/forums/forum/202505/topic/3547741
Thanks,
Vicareplus Team,
www.vicareplus.com