Love or hate CMS?

[Ned Storm]

Quote:I noticed that-- is it something I can simply delete?

It doesn't pose a security risk to me since my ISP blocks port 80 to the outside world (WAN).

Also, in my development environment I don't have any data that I care about in the database.

According to the XAMPP documentation (readme_en.txt):

Quote:To fix most of the security weaknesses simply call the following URL:
http://localhost/security/

But I don't bother on my local machine.

[repowell]

Well, I finally installed Drupal 6.12 on Xampp. Funny enough, I had difficult doing this (SMF posed no problem... it was simply copy, paste, install.) Apparently you have to make a few modifications to the settings.php file before the installation process will work. It all made sense after it was said and done, but locating an appropriate up-to-date article on the subject was irritating.

For anyone who intends to install Drupal 6 on Xampp, please read the following tutorial:
http://drupal.org/node/307956

It is a pretty interesting platform. I spent a few hours yesterday just messing around with menus, blocks, and such.

[Ned Storm]

It's been a while now since I started using XAMPP and I am still very happy with it.

One small thing is that you have to switch off Skype before starting it, otherwise the Apache and MySQL server will not start up. Then you can restart Skype (I guess they are sharing some ports).

As regards web development I am now a great fan of NetBeans. It's an IDE that I use mainly for PHP development and I also use SVN to store versions of my code (this integrates nicely with NetBeans).

When you develop any kind of code/templates for clients, you should keep a released copy that is version stamped. Using SVN is one of the best ways to do this and backup data to another location such as a USB drive.

On my hard disk I have a releases directory and below this there are directories for all my projects and below that the files that are part of the particular release variants. And all this data is backed up.

For example, for a template released to a client have a directory like this holding all the released files and documentation:

c:/releases/templates/wp1/v1/

And you save this to a backup drive too.

Then when you release a new version to a client, you create another directory such as:

c:/releases/templates/wp1/v3/

And the version numbers can copy those of SVN.

Also I run a batch file to save the SVN repository (what SVN uses to track changes) to a backup drive daily.

So this cuts down on stress, keeps us organized and avoids losing vital data due to computer problems.

[Ned Storm]

There is another Open Source CMS that I am looking to use: Jojo cms.org