You may also be interested in this page which has a scan of an early Tintagel guide book with an advert for Ocean Cove inside.  When I posted that it estimated the date at around 1953, but from your comment, it would have to have been a few years later.

http://www.kevinleah.co.uk/cornwall/tintagel/

And the image is my father and grandfather in the bottom field at Ocean Cove.

With regard to the config file, how are you creating it? Can you open up the Terminal App from Utilities and type:
ls -l /fullpathtowordpress/wp-config.php
e.g.
ls -l /ServiceData/Web/wordpress/wp-config.php
(-l is a lowercase L)

Post the output here.

With regard to creating a SQL user. I use either phpMyAdmin or Webmin – both provide a web based GUI for managing MySQL

I have done what you said, but I am have trouble getting my WordPress site up and running, I got to the point where WordPress tries creates a WP-config.php file, it makes me copy the text and create my own, which I do. But then it does not recognize the file I make and keeps asking me to create on, even showing a web page displaying the config file date to any that go to the URL, which is not cool like my passwords and stuff. So I have to change the config files’ name, at which point it asks for all the data needed to create a config file again.

I have a feeling this may have to do with permissions, but I don’t really know what that is or how to change it.

I would also like to know how to create another MySQL log-in besides root so I don’t have to use root.

Scoopz

I recently bought the new Mac Mini Server with Snow Leopard Server (SLS) installed to take over from my Mac Pro. Setting up SLS was much easier than I thought and I have two websites hosted on their successfully including a wordpress site. Which seems fully operational BUT I cannot utilise the auto-update plugins/themes feature.

I have enabled the FTP service, added the folder hosting the site as an Alias and that eliminated the “Cannon find wp content folder error” and it now finds the folder correctly, it downloads the updates, unpacks into the update folder, deletes the old version but then fails trying to copy the updated files back to the plugin directory.

I don’t know what else to do. If I FTP from a normal FTP client I can read and write to the plugins directory perfectly.

Has any body come across this before?

Scoopz

I've installed wp-super-cache and it seems to work now.

Thanks for your help!
Javier

This one took a long time to figure out, alot of late nights and hairpulling and so on!

I have narrowed it down to be the way that OS X Server handles HTTP Header caching, it is totally fine and works really good on static content and alot of dynamic content to but for some reason WordPress doesnt play so well with it!

Go to your Sites folder in /etc/apache2/sites and open the text file that corresponds to your WordPress domain (make sure you have write permissions in that folder)

Once you open the file you will se the <directory “folder”></directory> directive

Inside the <directory> directive simply add these lines:

Header Set Cache-Control “max-age=0″
<FilesMatch “.(ico|pdf|flv|jpg|jpeg|png|gif|swf|mp3|mp4)$”>
Header set Cache-Control “public”
Header set Expires “Thu, 15 Apr 2011 20:00:00 GMT”
Header unset Last-Modified
</FilesMatch>
<FilesMatch “.(js|css)$”>
Header set Cache-Control “public”
Header set Expires “Thu, 15 Apr 2011 20:00:00 GMT”
Header unset Last-Modified
</FilesMatch>

The first line will remove the OS X Server Header caching and the FilesMatch function will then add back Header Caching to files that you want to cach directly, if you dont use the FileMatch function nothing will be cached!

So if you wanna use caching for your PHP files just install wp-super-cache and now EVERYTHING will be cached right, atleast for me it does!

So if this works for you, please reply back so i can start using this workaround in a bigger scale!

Regads,
Javier