Linux, Windows, MacOS? Who cares. Just give me something that works!
Whats new in Drupal 5.0 videocast
Looks great and this is a final release [not beta or rc] but with all things application related, it will be awhile before true stability and production-readiness is achieved. Not to mention all the modules and themes that might need to be ported.
I’m not quite sure if I will update from 4.7 to 5.0 in the next Suite release. Its 50/50 as of right now.
The other project that I mentioned, that has been in the wind since 2003, has been uploaded to the server…
Some of you are probably scratching your heads right now, but it has possibilities.
Right now, the backend is not connected, its just out to get indexed. In a few days I’ll add the needed database entries and a wget script, and it should go live.
In the mean time I need to do some work on DynamicSide.NET [which should be live within the next 7 days]. This dynamic dns project is turning out to be fairly complicated, since I’m not turning out a hack and am implementing an actual user system that validates, has features, and can be maintained and upgraded. Lots of php and sql code.
I also have a 3rd project, but I think I’ll put it aside for the time being, if I can resist temptation.
I’m not sure why some instructions make simple task difficult, but here is how I upgrade WordPress…
Backup current ‘wordpress’ directory and database.
cp -a wordpress/* /usr/local/bk/wordpress/mysqldump --user=root --password=XXX wordpress > /usr/local/bk/wordpress/wordpress.sqlDownload and extract latest version of WordPress.
This will unpack a directory called ‘wordpress’ so be careful where you do this and how.
wget http://wordpress.org/latest.tar.gztar -xzf latest.tar.gzCopy the newer wordpress files over the current base. This will not overwrite files ‘.htaccess’ or ‘wp-config.php’, or anything else that was placed or generated after the initial install.
cp -r --reply=yes wordpress/* /path/to/current/wordpress/dir/
Run upgrade script.
http://www.example.com/wordpress/wp-admin/upgrade.php
I’ll make this one short and simple, about something I’ve learned.
Don’t try to design your own website from scratch unless you’re a website designer.
Use a template, or use a CMS. Otherwise it will not look professional no matter what you do or believe.
You might find the following Google Search query invaluable…
Google Search:
“creative commons” OR “open source” website template
And if you can’t locate what you are looking for, you can always buy a template for $60 and save your time and effort for something else.
All in all, I like it.
It generates valid html/css and has more administrative options than phpBB. Though in someways it does feel a bit more complicated to setup and use properly [keep in mind that *I have* been accustomed to using phpBB since 2003, and I did have to perform the extra steps of setting everything up and converting the old forum db to SMF].
On the plus side, it is much more secure than the nightmare called “phpBB”; though I do not like the fact you have to chmod 777 all the files — or at least some subset. Nor the fact that SMF does not seem to have as large of a community base as phpBB, which translates into “good luck finding the info you require, or locating a solution to a problem.”
The biggest hassle right now is with losing all the old URLs that have been indexed, that have good SE positions…
Indexed phpBB URLs are primarily of a post number while SMF uses a system where you have to start with a thread number and only then can you work to the post number. And since I have no way of knowing the thread number, all I can do is redirect back to index.php.
I’m going to stick to the default theme as it has a very clean and simple look. One other theme that I liked was called ‘DilberMC’, with the light silver color and an 800px width.
And just as a note to anyone interested in SMF, while it is free software, it is not GPL. The licensing termed specifically prohibit you from distributing the software in any way, modified or not. All generated copyright notices must also be retained.
As of the 1st of January, 2007 I have put up the DynamicSide.NET Dynamic DNS (ddns) site.
Be warned, its very beta right now. You can see the site and do a couple of things, but for the most part it is not integrated with the backend.
This project turned out to be much more complex that I originally hoped for… A solid week and a half of work in what you are seeing, a good 4-8 hours a day. The layout was simple, but the rest is another story. I would say its 75% complete. I just have to go over a few things and put up the backend.
So its out in the wild primarily to get indexed and to let everyone see a bit of the future.
Developed and tested on the Web-Developer WAMP Server Suite. [That would be a nice type of banner/stamp to put up.]
There is another project that I think I will work on before I complete this one, but its much more simpler and once the site layout is done, it should not take more than a few days to do.