Archive for category Web Development
Many of you may be die-hard GoDaddy users. GoDaddy's support of the SOPA has led many people to start looking for a new registrar, including myself. After a boycott, GoDaddy broke away from its support of SOPA. However, their initial support for the legislation was enough to turn me away. I do not plan to do any further business with them and will be slowly migrating my existing sites over to another registrar as time goes by.
In my search for a GoDaddy alternative, I found that I really like NameCheap.com. They offer good rates on domain transfers and registration. I also like their control panel much better than GoDaddy. They don't have as much up-selling going on when you register a domain. I always found that annoying about GoDaddy. I also didn't care for GoDaddy's domain manager. Once, I tried out GoDaddy's Windows hosting as well. It was terrible. So if you are looking for a viable alternative to GoDaddy, you should definitely give NameCheap.com a try.
I'll make this post short and sweet. Let's say you've forgotten your login for a WordPress site. To reset the password to something new, you can simply use a SQL query. If you have access to PHPMyadmin or the MySQL command line, this is really straight forward.
From PHPMyAdmin, open the database for the WordPress installation. If you don't know which database to use, check out your wp-config.php file inside your main WordPress installation folder. You'll find constants defined in that file for your database name and database user. Once you've found the database, you can execute a SQL statement by clicking the SQL button. In there, type:
UPDATE wp_user SET user_pass = MD5("yourpassword") WHERE user_login = "admin";
That's assuming that your username is "admin". Change it to whatever username you are using. Once you run that SQL statement, your password will be set to whatever you put in "yourpassword". Both the username and password need to be quoted in the SQL statement.
To do the same thing in the MySQL command line, connect to the database with:
mysql -u<username> -p
Substitute <username> with your actual username from the wp-config.php file.
You will be prompted for a password. Use the password from the wp-config.php file.
Once you are logged into the mysql command problem type:
Substitute the actual database name from the wp-config.php file.
Finally, type the update statement above and hit enter.
After you've updated the table via SQL, you should be able to login to your WordPress installation.
Anyone who has had programming classes knows that one of the primary things they push on you is that all good programmers comment their code. They don't always tell you how much commenting you should do, although some do give good advice. How does one decide how much is enough.
Comments are great because they are basically communications between programmers to help with the logic that is going on in the code. Sometimes the two programmers are the same person. I think a good rule of thumb is to comment just below your own skill level. This means to comment just enough to help someone of almost the same skill as yourself along. You don't want to comment your code to the point that it clutters up the rest of the source, but you want to be able to read through your own code and quickly find the cause of any potential bugs. You never know when you'll have to go back through your own code. Chances are you won't remember what exactly is going on at any particular point, especially if you work on a lot of projects.
Of course, there are always conventions that are mapped out beforehand for most developing teams, but if you are working solo, you should comment as if you are in a team environment.
I personally find comments distracting and ugly when viewing code. I don't particularly care for method and class header comments. They rarely give any useful information. Inline comments are very valuable, however. So if if the coding standards of your team require class and method headers, put them in, but if you are solo or there's no coding standards in place that require these types of comments, don't use them. You should be able to look at any method and tell what kind of parameters it takes, and you should be able to quickly find the return type. These aren't necessary and break down code readability in the end.
Comment changes. If you have to remove some code, comment it out instead of deleting it. This will help you revert changes or come up with better solutions if it is later found that the new code is buggy itself. If you have some bit of logic that is complicated even to your own eyes, comment it and explain how it works. Other than that, keep comments to a minimum.
Due to its support of SOPA, many people are calling for a boycott on GoDaddy. At first GoDaddy was laughing because of the planned boycott. After about 24 hours, their tone changed and they proclaimed that they were no longer supporting the legislation. Many people are looking for alternatives to Godaddy.
I searched for a bit and found that about the best deal in town is namecheap.com. There is a transfer fee for moving domains over to them, but you get a free year of registration with the transfer. So for around $7 bucks you can transfer and renew a .com. If you have a few months left before it's time to renew your .com, you can still transfer the domain and get a free year along with the remaining time of your current registration.
Check out their deals. Let's show GoDaddy that we do not like their support of this unconstitutional legislation.
I just started a new website devoted to teaching people how to develop websites. The site is PHP Video Tutorials. So far I have about 20 videos uploaded. There are nine in the first series which teaches basic HTML and CSS. The second video series goes into PHP and MySQL. I think these videos will be very helpful to anyone who wants to get into web development.
I searched for the best PHP framework for a while. I tried CakePHP, Zend, Yii, Symfony, and Codeigniter. Some of them frustrated me to the point that I was ready to write my own mini-framework. I think the problem with some of them, at least from my perspective, is that they try to do too much. Some were just poorly documented. Sure, you can find all the information you need to find about all the features, but they don't make it very easy. For this post, I want to compare two of the most recent frameworks I've worked with, Codeigniter and Symfony.
I use Codeigniter for all of my personal projects these days. Recently, I had to use Symfony for some other work I was doing. I can see positive and negative aspects of each system at this point, and this is an overview of their main differences.
First, I'll talk about Symfony. It includes two ORMs, Doctrine and Propel. I was using Doctrine. It relies heavily on the ORM as it should, but I found utilizing an ORM to be overly complex. This may be due to my own ignorance, but when using an ORM, you have to get into a different mindset. Most people would view the ORM as a feature. For me, it was unwanted. Symfony is a great framework and is used by many people. My distaste for it should not be a deciding factor in choosing your own framework.
However, I would like to point out other things about Symfony that I didn't like. First of all, the directory structure is overly complex, especially when your job is to maintain code that is already in place. You may find yourself looking at a page and going through 10 different files trying to find where the code is located. Symfony has a ton of plugins, many of which have auto-generated forms and templates. There are times that you won't find the code that generates the form and from what I saw, your only option is to override the plugin's actions and templates. If the code you're maintaining doesn't override the plugin, you will have to check cache files for the auto-generated PHP and then implement this in the override.
While we are talking about caching, I'll point out that this is a good feature and it's implemented by default in Symfony. During the development maintenance of a site, however, it gets on my nerves. So, you'll spend a lot of time clearing your cache from the command line. Symfony depends on command line usage. While I like using a command line in most cases, I don't want to be jumping back and forth between my IDE, command line, and web browser so much. Since Symfony auto-generates a ton of code for you through the use of the command line, I can see the advantage, but I prefer the Codeigniter way.
So, let me talk about Codeigniter and why I prefer it to all other frameworks I've tried.
First of all, it stays out of your way. It arranges your site into three folders, as I think it should, models, views, and controllers. You can then arrange your files in sub-directories under these main folders as you wish. So if you have a user system on your site, you can put all your views for that section under views/user.
While I'm on the subject of views, let me touch on Symfony's templates and layouts. It's actually a good system and cuts back on the amount of code one has to write, but it depends on yaml config files in various locations. I liked the idea, but hated the implementation. I much prefer having the view source where I can easily find it. In Codeigniter, I get all my data ready to send to a view, then load that view. In this view, I can load other views as needed. So if my page has a top navigation menu, I can just load that menu from within my view. This templating system works best for me, and I don't have to search through config files at various locations to find out where the HTML is located.
Finally, documentation is much better in Codeigniter. If you want to know how a library or helper works, their documentation makes it simple to understand. Symfony's documentation is terrible in comparison. There's a reference but it's just not that good. Plus much of the documentation you'll need is actually on the Doctrine site.
Symfony has many features that Codeigniter doesn't. Codeigniter is much easier to use, has the best documentation, and is much easier to maintain. These three things are why I prefer Codeigniter. Maintainability and ease of use are the two main reasons to implement a Framework anyway. Without these two things, one would be much better off using straight OOP PHP.
I've been really interested in using a PHP framework. One thing holding me back is deciding which one to work with. It seems that every time I start looking at frameworks, I end up deciding to just code everything manually. The major contenders seem to be Yii, Zend, Symfony, CakePHP, and CodeIgnitor. However, I have no idea which one I'm going to use. It's hard to decide without learning the ins and outs of each one and making a good decision based on that knowledge.
My latest attempt was with the Zend framework. I was getting into it and realized that most of the documentation for setting it up bases the setup from a virtual host in Apache. This would be fine, but it actually makes development and deployment overly complicated for me. My development environment is a Linux machine that is my main desktop. My production server is my own dedicated server with CPanel. Zend doesn't work very well with this setup from what I can tell.
I want my site to transfer easily between the two environments. I like them to be self-contained as well. I want to throw the framework into a lib folder or link to it in some way. I don't like that the forward-facing web site is in the "public" folder. I want the root of the website to be the forward-facing public website.
I would really like to use Zend because it has a lot of good extensions for utilizing various web services.
I'd like to hear from others. Which framework would you recommend and why?