Archive

Archive for the ‘Webmasters Resources’ Category

Another Nice Looking Multi-Level Context Menu in Mootools

March 18th, 2009 No comments

After publishing Mootools ContextMenu few days ago, our reader, Temuri has suggested another really nice looking context Menu using Mootools which is called Mif.Menu. There are ART style and shadow style context menu for you to choose from. It supports multi-level and key navigation as well. Mif.Menu is released under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 License.

 

another

Highly Customizable Mootools ContextMenu Plugin

March 18th, 2009 No comments

MooTools ContextMenu Plugin is a highly customizable, compact context menu script written with CSS, XHTML, and the MooTools javascript framework. ContextMenu allows you to offer stylish, functional context menus on your website.

The most dynamic part of the ContextMenu instance is the “actions” option, where you define what action should be taken per menu item. The action is passed the element clicked on and the reference to the context menu.

 

highly

Categories: Webmasters Resources Tags:

A New Look for BlogHash

March 18th, 2009 No comments

Over the last couple of weeks I had been busy working on a new template for BlogHash and finally it’s ready. If you are reading this post from your RSS reader, visit the home page once and take a look at the new theme of Bloghash.
A New Look for BlogHash

BLOGHASH

Why did I do it myself?

In the last few months I have contacted at least 5-6 WordPress theme designers but none of them seems to have had any interest in designing a theme for my site; no one replied to my email. Hence, I took it upon myself to design a theme for my blog site. I knew it wouldn’t be easy but then I wanted to learn.

Thank you for the inspiration

First it was John Chow, then Problogger and Keith also got a new design. When they got a new theme loaded up, it was perhaps the last spark needed to start the fire in my mind; I wanted a new one too!

The components of my theme

Before even I started with the design plan, I visited at least over 100 different blogs, thanks to the great list of WP designs on SmashingMagazine, and made a note of the different features on each of those blogs. Most of them had common set of things on their home page and almost everyone’s single view pages were left aligned with one sidebar on right. I wanted to design something different.

The new home page shows excerpts of most recent posts, on the right there are two sidebars showing some of the most visited posts under various categories. This helps in flow of page rank to those pages from the home page.

The single post view has one sidebar on either side. The one on the left is to show ads while the one on the right is to show related popular posts which I am still working on. I intend to show the most relevant post depending on the category of the post viewed.

Please give me feedback

Please spend a few minutes browsing the new theme on my blog and provide me with your valuable suggestions and feedback. Do let me know if you have any tips to help me improve my blog’s design.

Categories: Webmasters Resources Tags:

Website Audience

March 18th, 2009 No comments

Understanding the type of people who visit your site is a very important task because you can use that information to enhance your site to suit them. As a result, you will gain more loyal returning visitors that come back again and again for more.

What is the age level and what kind of knowledge does your audience have? A layman might linger around a general site on gardening, but a professional botanist might turn his nose at the very same site. Similarly, a regular person will leave a site filled with astronomy abstracts but a well educated university graduate will find that site interesting.

Take your audience’s emotional state into consideration when building your site. If a very irritated visitor searches for a solution and comes across your site, you will want to make sure you offer the solution right up front and sell or promote your product to him second. In this way, the visitor will put his trust in you for offering the solution to his problems and is more likely to buy your product when you offer it to him after that.

When you design the layout for your site, you have to take into account the characteristics of your audience. Are they old or young people? Are they looking for trends or are they just looking for information served without any icing on the cake? For example, introducing a new, exciting game with a simple, straightforward black text against white background page will definitely turn prospects away. Make sure your design suits your site’s general theme.

Try to sprinkle colloquial language in your sites sparingly where you see fit and you will create a sense that your audience is on common ground with you. This in turn builds a trusting relationship between you and your audience, which will come in useful should you want to market a product to your audience

Categories: Webmasters Resources Tags:

Making Merchant Websites Easy

March 18th, 2009 No comments

Convincing your prospects to purchase from you is a hard job, but have you ever thought that you’re making the process twice as difficult for both parties if your prospects are convinced but don’t know how to buy from you? No matter how good you are at convincing your prospects, they won’t buy if they find the process cumbersome.

First, you will want to check that people can find your order form easily and hassle-free. You can write a clear, concise paragraph to direct your prospects to your order form so that you can minimize the chances of them getting lost. You can also reduce the chances of losing prospects by putting a prominent link to your order page from every other page on your site.

Also, do you offer multiple payment options? Some people may feel comfortable paying via PayPal, some may only want to pay with their credit card and others might want to send a check. The more options you offer, the better your chances of covering your prospects’ desired payment method. After all, it wouldn’t make any sense to sell hard to a prospect only to find that they won’t be able to pay you when they want to.

On the other hand, you will want to prove that you are a credible merchant. Is your order form secured using encryption technology? You would want to look into SSL for this. You can also offer a money back guarantee so that people will feel confident about buying from you. How about after sales support? Who do they contact when they have problems after purchasing?

Alternatively, you can add customer testimonials, your contact information, address, and so on to boost your prospects’ confidence. Make them feel safe about buying something from you, a total stranger to them on the other end of the Internet.

As a conclusion, it would be very pitiful if you sold hard and sold well to a prospect and something goes wrong when he or she is ready to pay. Eliminate any chances of that to maximize your profits!

Floats, CSS, Divs, the Refresh Button, Firefox, and Frustration

March 17th, 2009 No comments

WordPress is a funny beast, really it is.  Usually, building a WordPress site involves something like digging through a hundred pages of templates until you find one that’s merely passable.  Once you do, you grab it and start hacking away at everything to make it your own – CSS, HTML, everything.  And it’s fine.  Really, it is – the internet’s built on sharing ideas.  The problem appears once you start inheriting other people’s problems.  In this case, I had to hit the refresh key just to get my divs to float correctly.

The thing with using a tableless design is that people tend to create an outer division to put other inner divisions into.  Usually this looks like a main content box with two columns in it, which is what I had.  In order to get those columns to line up side by side, you tell the css of those divs to float:left;.  Here’s where we inherit the problem, however.  When I visit the page for the first time, or reload the page without using the cache, the floats start clearing one another, even though I have never set a clear css property on either of the divisions.  (If you don’t know what I mean by “clearing”, imagine you want to put two columns side by side, and instead they stack on top of one another.)  The whole ordeal was rather frustrating, until I noticed one thing.

The outer, main content division had a property from before I started editing the css.  The outer div was set to display:table;.  I don’t know if it’s a bug, but the issue remains:  If you have an outer div set to display:table, the inner divs will clear each other regardless of how you float them. The solution?  I didn’t need the outer div to act like a table, so I just removed the display:table; property and now all is well.

I don’t know if you’ll be able to remove the display:table; property from your outer div, but you’ll have to find a way around it if this problem occurs in Firefox for you.  I hope this helps someone track their problem down.

Going full circle: could falling back to Flash solve IE’s lack of canvas support?

March 17th, 2009 No comments

There is an interesting blog post* and demo code on Azarask explaining Flash Canvas as a solution for IE’s lack of support for Canvas:

    How does FlashCanvas work?

    FlashCanvas is modeled after ExplorerCanvas which means it is a turn-key solution for adding Canvas support to IE. You can code away, happily using open standards and then use FlashCanvas to forcefully and silently upgrade IE to also being standards compliant.

    There are two main components in FlashCanvas: the base FlashCanvas.swf flash file (a mere 688 bytes), and the FlashCanvas.js wrapper. I’ve used the excellent swfobject.js to embed the Flash into the page.

    The FlashCanvas.js file implements a fake-canvas object and converts all existing canvas element into a flash object. The javascript intercepts canvas commands and forwards them to the FlashCanvas.swf movie file using the ExternalInterface provided by the flash player. The flash movie clip then interprets the command and draws accordingly.

Aza originally thought that this would also solve the performance problems other fallbacks to VML have but found out that sadly enough this is not the case because of the lag between ActionScript and JavaScript via ExternalInterface.

    Each call via the ExternalInterface is taking approximately 0.5 ms. Since we know the time it takes to call an actionscript method from javascript, we can deduce the amount of time it takes for Flash to render. For the example1.htm page it takes ~24 ms to render 20 anti-aliased lines. In Safari a call into actionscript takes roughly 0.4 ms — this is only the call time, it doesn’t include the time to render anything. For example1.htm a single “particle” calls actionscript 3 times with the commands: [lineStyle,moveTo,lineTo]; each particle takes 1.2 ms in JS-to-AS calls; to take 1 second to render the frame ~833 particles need to be rendered.

There are few more ideas in the comments to the article and this might be an interesting concept to take further. Somehow it seems ironic to go back to Flash to make IE render standards, but then again VML is proprietary, too.

Categories: Webmasters Resources Tags:

Real time Traffic Statistics And Analysis From FeedJit

March 17th, 2009 No comments

You probably noticed “Live Traffic Feed” widget that I have in the right sidebar and today I took a deeper look what else I can get from it… Turned out this little widget is quite more powerful than it looks from outside.

In the basic view FeedJit display visitors in real time with the link to the referring page so you can check who sending you traffic right from your front page. If you click on “Watch in real time” link on the bottom of the widget it will forward to the FeedJit website where you can see more extended results.

For example if visitor was referred by the search engine – there will be exact search term he used to find your site. Also it shows browser and operating system visitors are using and if they left your site by clicking on one of the links – you’ll see which link it was. Two more options – visitors map and statistics for most popular pages.

This little widget could be a very nice analytical tool but the drawback is – it does not provide any historical data. All you can get is real time 20 or so results. If at some point developers decide to add some historical traffic results it can be very useful tool, probably even better than Google analytics which is far from being accurate.

Good thing I noticed – this widget loads very fast (much faster than Digg of Feedburner) and does not affect speed of your pages. Everything is external – all you do is insert small code snippet (can use sidebar text widget).

So if you want to have some fun watching who is knocking in the door and how they found you – go check out FeedJit.com and let me know what you think of it. Widget is free to use and does not require registration.

 

feedjit

Have something to say regarding the subject in my post? Post your comment and I will be happy to thank thank most active commentators with direct link!
Did you learn something new today or like my point of view? Subscribe to my full RSS feed in the your favorite reader or get new posts delivered by Email directly to your inbox.

Categories: Webmasters Resources Tags:

Magento Installation Guide for Dreamhost

March 17th, 2009 No comments

I’ve been watching the Magento e-commerce project for about the last month and a half – since Ben sent me a link to it. It’s an open-source e-commerce package, that primarily aims to pickup and improve where OSCommerce, Joomla + VirtueMart, and ZenCart have left off – streamlining a CMS (Content Management Sytem) and E-commerce shopping cart. This also means built-in SEO (Search Engine Optimization), Google Checkout integration, varied customer groups, and much more…. straight out of the box. The problem appears to be that there are a lot of people on the Magento forums who are running into problems, and don’t have a clue on how to get it running under their Dreamhost hosting account. Unfortunately it also looks like the previous article(s) for Magento+Dreamhost installs have disappeared, or are outdated. And that’s where this article comes in…

If you just so happen to be one of those whining idiots, or clueless n00bs, then you’re in luck! I’ll take you through a step-by-step process of installing Magento on your Dreamhost account. But please be forewarned: This requires some “advanced” techniques, so if you don’t know what Putty/SSH or a command-line are, then STFU and GTFO, n00b. Just kidding. Hopefully I can explain those things too, and increase your knowledge. In fact, it may even get you laid! But probably not.

   1. Step 1 – Dreamhost: Create domain
      Obviously we need a domain to work with here. I’ll be using ‘magento.webinade.com’ as my test domain. Be sure to set it up to use PHP5, that’s a Magento Requirement.

Step 2 – Dreamhost: Give User Shell Access
We need to have shell access in order to connect to the command line and configure magento. In the Dreamhost Control Panel, go to Users > Manage Users and then click Edit next to the user you chose for your domain. It should take you to a screen like this, where you can set the Account Type to Shell Account. Step 3 – Dreamhost: Create MySQL Database
We need a MySQL database setup for Magento prior to the install. Magento stores data and configuration settings in MySQL. In Dreamhost go to Goodies > Manage MySQL. Then scroll to the bottom to set up a new database. If this is your first database, you’ll also want to set up a hostname – typically something like mysql.yourdomain.com will work. Step 4 – SSH in to Server
And now the fun begins. Let’s start by SSH’ing into Dreamhost. If you don’t know how to do this, go download Putty if you’re on a Windows machine. Open it up. Type in the domain you’re hosting magento on (magento.webinade.com in my case), make sure the Port is set for 22, and connection type is SSH. You will then be prompted for a username and password. Type them in (don’t be alarmed if you don’t see anything when typing your password). If you are successful, putty will return something along the lines of ‘[server_name]$’ like in the picture below. You’re now logged into the command line of your Dreamhost linux server. Step 5 – Download Magento from Linux Command Line
Now that we’re logged in, we need to download Magento. To do so, type the following command:
wget

I’ve been watching the Magento e-commerce project for about the last month and a half – since Ben sent me a link to it. It’s an open-source e-commerce package, that primarily aims to pickup and improve where OSCommerce, Joomla + VirtueMart, and ZenCart have left off – streamlining a CMS (Content Management Sytem) and E-commerce shopping cart. This also means built-in SEO (Search Engine Optimization), Google Checkout integration, varied customer groups, and much more…. straight out of the box. The problem appears to be that there are a lot of people on the Magento forums who are running into problems, and don’t have a clue on how to get it running under their Dreamhost hosting account. Unfortunately it also looks like the previous article(s) for Magento+Dreamhost installs have disappeared, or are outdated. And that’s where this article comes in…

If you just so happen to be one of those whining idiots, or clueless n00bs, then you’re in luck! I’ll take you through a step-by-step process of installing Magento on your Dreamhost account. But please be forewarned: This requires some “advanced” techniques, so if you don’t know what Putty/SSH or a command-line are, then STFU and GTFO, n00b. Just kidding. Hopefully I can explain those things too, and increase your knowledge. In fact, it may even get you laid! But probably not.

   1. Step 1 – Dreamhost: Create domain
      Obviously we need a domain to work with here. I’ll be using ‘magento.webinade.com’ as my test domain. Be sure to set it up to use PHP5, that’s a Magento Requirement.

Step 2 – Dreamhost: Give User Shell Access
We need to have shell access in order to connect to the command line and configure magento. In the Dreamhost Control Panel, go to Users > Manage Users and then click Edit next to the user you chose for your domain. It should take you to a screen like this, where you can set the Account Type to Shell Account. Step 3 – Dreamhost: Create MySQL Database
We need a MySQL database setup for Magento prior to the install. Magento stores data and configuration settings in MySQL. In Dreamhost go to Goodies > Manage MySQL. Then scroll to the bottom to set up a new database. If this is your first database, you’ll also want to set up a hostname – typically something like mysql.yourdomain.com will work. Step 4 – SSH in to Server
And now the fun begins. Let’s start by SSH’ing into Dreamhost. If you don’t know how to do this, go download Putty if you’re on a Windows machine. Open it up. Type in the domain you’re hosting magento on (magento.webinade.com in my case), make sure the Port is set for 22, and connection type is SSH. You will then be prompted for a username and password. Type them in (don’t be alarmed if you don’t see anything when typing your password). If you are successful, putty will return something along the lines of ‘[server_name]$’ like in the picture below. You’re now logged into the command line of your Dreamhost linux server. Step 5 – Download Magento from Linux Command Line
Now that we’re logged in, we need to download Magento. To do so, type the following command:
wget http://www.magentocommerce.com/downloads/assets/0.8.16100/magento-0.8.16100.zip

That should download the 0.8.16100 beta version of Magento to your home directory, and should look like this:
Step 6 – Unzip Magento & Move it to the Live Domain
Run the following command to unzip Magento. You’ll get several hundred lines, telling you which files it is extracting where. It should extract everything into a folder called magento.
unzip magento-0.8.16100.zip

Run this command to move the contents of the magento folder into your live site:
mv magento/* magento.webinade.com/
mv magento/.htaccess magento.webinade.com/.htaccessObviously replace magento.webinade.com with the folder your domain is in. You will not receive output from the above two mv commands, unless there is an error. It will simply return you to the command line. The commands and output should look similar to this:
Step 7 – Magento Install
Now that we’ve got the files extracted, and hopefully in the right folder, let’s load up the website. It should show a page like this:

To continue, agree to the license. The next page is localization information – defaults are good for most, but feel free to change these. The third page is for downloading updates to Magento. This is important, and this is where some problems often arise. You can ignore the first two section, SVN Installation & Package Management Through The Web. The third part of that page is what’s important. Open up putty again and type the following command, changing the name of the folder of course to match yours:
cd magento.webinade.com/
./pear mage-setup

That should produce some output similar to this:

Good! Now, the next line:
./pear install mage-core/Mage_Pear_Helpers mage-core/Lib_ZF mage-core/Lib_Varien

This should produce similar output:

Unfortunately, we can’t run the third line just quite yet. We need to change the PHP variable in the ./pear file. Right now it just makes a call to “php” on the system – which by default on Dreamhost is PHP4. Let’s modify the file with Midnight Commander – a file manager similar to that of the old Windows 95/98 or XTree Gold. We need to change it to reference PHP5. Run this:
mc

You’ll then need to navigate (with your arrow keys!) down to the pear file, and hit F4 to edit it. Scroll down to line 62 (again, with the arrow keys!). Line’s 61-63 will look like this:
else
PHP=php
fi

Change them to this:
else
PHP=/usr/local/php5/bin/php
fi

Hit F2 to save, agree. Then hit F10 to quit. All of the above should look like this:

Now we can run the third command:
./pear install mage-core/Mage_All mage-core/Interface_Install_Default

It should look like this now:
#

Unfortunately, that may update/overwrite the ./pear file we just modified. You’ll know if it does, when you try to run the next command:
./pear install mage-core/Interface_Frontend_Default mage-core/Interface_Adminhtml_Default

And you get an error saying “Permission Denied” or “No valid packages found.”
#

Step 8 – Rinse & Repeat (Fix Permissions on ./pear and Update Again)

If you get one of the above two errors (which you should), you’ll need to do two things. First, you need to change the file permissions on the ./pear file, like so:
chmod 755 ./pear

Second, you need to modify ./pear again to fix the PHP version it is referencing (like above). Run this:
mc

You’ll then need to navigate down to the pear file, and hit F4 to edit it. Scroll down to line 62 (again, with the arrow keys!). Line’s 61-63 will look like this:
else
PHP=php
fi

Change them to this:
else
PHP=/usr/local/php5/bin/php
fi

It’s not so bad. Just really annoying. I’m hoping the Magento guys will update the scripts in newer versions to run a check on the ./pear file, and hopefully carry over any modifications done to it. Or maybe make some of these configurations more “user friendly” or st00pid n00bs.

Now that that is done, we can run the last command and continue:
./pear install mage-core/Interface_Frontend_Default mage-core/Interface_Adminhtml_Default

Victory! Hopefully it looks like this for you:
Step 9 – Finish Magento Install
Now that is all done, we can continue on with the Magento install. Click the “Continue After Manual Download” button in your browser (You’ve still got your browser open, right?). Some of you may or may not receive an error here. I didn’t on my first install of Magento, but I did on my webinade test install. If you do, it may say and look like this:
Path "/home/.donald/magento/magento.webinade.com/app/etc" must be writable
Path "/home/.donald/magento/magento.webinade.com/var" must be writable
Path "/home/.donald/magento/magento.webinade.com/media" must be writable
Image:

Don’t worry! These are easy fixes. Run these commands at the command-line (in Putty):
chmod 777 ./app/etc/
chmod 777 ./var
chmod 777 ./media

Now click the “Continue” button in the browser and the errors should be gone. You’re now presented with a Configuration page, with all kinds of great MySQL settings and textboxes. Fill them in to match whatever you created you MySQL database with earlier. You’ll also want to check the box that says “Use Web Server (Apache) Rewrites” – this is good for SEO. You can check the Box for SSL URLs, but only if you have an SSL certificate installed and configured for your Dreamhost account. My page looks like this:

   9.

      Click Continue, and the next page will present you with form fields to setup your Administrator account as well as create an Encryption Key. Follow the instructions, fill in the boxes, and click Continue.
  10. Step 10 – All Done!
      You’re now done setting up Magento. Sit back, relax, crack open a cold beer (or bottle of wine), and let the gorgeous chicks flock to you. Maybe not?I suggest you login to the backend and start playing around. There is a lot of configuration that needs to happen before your store will go live, including customizing your own store design. There is a lot of great documentation available on Magento’s site, as well as a well populated forum, with several knowledgeable developers and supporters.

Please Note: Magento is in BETA! This means that you will more than likely run into problems, small or big. I don’t suggest running a live site on Magento until it reaches a stable release – hopefully by the end of March. Be sure to follow the forums.

And please don’t go whining on the forums, and posting ridiculous threads like “It’s broken! OMGz!!!!!!11!1” or “Magento doesn’t work! MY LIFE IS OVER! KILL ME NOW!” It doesn’t solve the problem. Others can’t help you, and you look like an idiot. Have some respect for the developers and supporters, and post knowledgeable threads, detailing what specifically doesn’t work. And please, please, please search the forums before posting. Odds are, someone else has had the same problem.

Feel free to post any questions or comments below. I’m always open to discussion and support. I’ll be playing with Magento over the next week, and hopefully will have a positive, thorough review.

That should download the 0.8.16100 beta version of Magento to your home directory, and should look like this:
Step 6 – Unzip Magento & Move it to the Live Domain
Run the following command to unzip Magento. You’ll get several hundred lines, telling you which files it is extracting where. It should extract everything into a folder called magento.
unzip magento-0.8.16100.zip

Run this command to move the contents of the magento folder into your live site:
mv magento/* magento.webinade.com/
mv magento/.htaccess magento.webinade.com/.htaccessObviously replace magento.webinade.com with the folder your domain is in. You will not receive output from the above two mv commands, unless there is an error. It will simply return you to the command line. The commands and output should look similar to this:
Step 7 – Magento Install
Now that we’ve got the files extracted, and hopefully in the right folder, let’s load up the website. It should show a page like this:

To continue, agree to the license. The next page is localization information – defaults are good for most, but feel free to change these. The third page is for downloading updates to Magento. This is important, and this is where some problems often arise. You can ignore the first two section, SVN Installation & Package Management Through The Web. The third part of that page is what’s important. Open up putty again and type the following command, changing the name of the folder of course to match yours:
cd magento.webinade.com/
./pear mage-setup

That should produce some output similar to this:

Good! Now, the next line:
./pear install mage-core/Mage_Pear_Helpers mage-core/Lib_ZF mage-core/Lib_Varien

This should produce similar output:

Unfortunately, we can’t run the third line just quite yet. We need to change the PHP variable in the ./pear file. Right now it just makes a call to “php” on the system – which by default on Dreamhost is PHP4. Let’s modify the file with Midnight Commander – a file manager similar to that of the old Windows 95/98 or XTree Gold. We need to change it to reference PHP5. Run this:
mc

You’ll then need to navigate (with your arrow keys!) down to the pear file, and hit F4 to edit it. Scroll down to line 62 (again, with the arrow keys!). Line’s 61-63 will look like this:
else
PHP=php
fi

Change them to this:
else
PHP=/usr/local/php5/bin/php
fi

Hit F2 to save, agree. Then hit F10 to quit. All of the above should look like this:

Now we can run the third command:
./pear install mage-core/Mage_All mage-core/Interface_Install_Default

It should look like this now:
#

Unfortunately, that may update/overwrite the ./pear file we just modified. You’ll know if it does, when you try to run the next command:
./pear install mage-core/Interface_Frontend_Default mage-core/Interface_Adminhtml_Default

And you get an error saying “Permission Denied” or “No valid packages found.”
#

Step 8 – Rinse & Repeat (Fix Permissions on ./pear and Update Again)

If you get one of the above two errors (which you should), you’ll need to do two things. First, you need to change the file permissions on the ./pear file, like so:
chmod 755 ./pear

Second, you need to modify ./pear again to fix the PHP version it is referencing (like above). Run this:
mc

You’ll then need to navigate down to the pear file, and hit F4 to edit it. Scroll down to line 62 (again, with the arrow keys!). Line’s 61-63 will look like this:
else
PHP=php
fi

Change them to this:
else
PHP=/usr/local/php5/bin/php
fi

It’s not so bad. Just really annoying. I’m hoping the Magento guys will update the scripts in newer versions to run a check on the ./pear file, and hopefully carry over any modifications done to it. Or maybe make some of these configurations more “user friendly” or st00pid n00bs.

Now that that is done, we can run the last command and continue:
./pear install mage-core/Interface_Frontend_Default mage-core/Interface_Adminhtml_Default

Victory! Hopefully it looks like this for you:
Step 9 – Finish Magento Install
Now that is all done, we can continue on with the Magento install. Click the “Continue After Manual Download” button in your browser (You’ve still got your browser open, right?). Some of you may or may not receive an error here. I didn’t on my first install of Magento, but I did on my webinade test install. If you do, it may say and look like this:
Path "/home/.donald/magento/magento.webinade.com/app/etc" must be writable
Path "/home/.donald/magento/magento.webinade.com/var" must be writable
Path "/home/.donald/magento/magento.webinade.com/media" must be writable
Image:

Don’t worry! These are easy fixes. Run these commands at the command-line (in Putty):
chmod 777 ./app/etc/
chmod 777 ./var
chmod 777 ./media

Now click the “Continue” button in the browser and the errors should be gone. You’re now presented with a Configuration page, with all kinds of great MySQL settings and textboxes. Fill them in to match whatever you created you MySQL database with earlier. You’ll also want to check the box that says “Use Web Server (Apache) Rewrites” – this is good for SEO. You can check the Box for SSL URLs, but only if you have an SSL certificate installed and configured for your Dreamhost account. My page looks like this:

   9.

      Click Continue, and the next page will present you with form fields to setup your Administrator account as well as create an Encryption Key. Follow the instructions, fill in the boxes, and click Continue.
  10. Step 10 – All Done!
      You’re now done setting up Magento. Sit back, relax, crack open a cold beer (or bottle of wine), and let the gorgeous chicks flock to you. Maybe not?I suggest you login to the backend and start playing around. There is a lot of configuration that needs to happen before your store will go live, including customizing your own store design. There is a lot of great documentation available on Magento’s site, as well as a well populated forum, with several knowledgeable developers and supporters.

Please Note: Magento is in BETA! This means that you will more than likely run into problems, small or big. I don’t suggest running a live site on Magento until it reaches a stable release – hopefully by the end of March. Be sure to follow the forums.

And please don’t go whining on the forums, and posting ridiculous threads like “It’s broken! OMGz!!!!!!11!1” or “Magento doesn’t work! MY LIFE IS OVER! KILL ME NOW!” It doesn’t solve the problem. Others can’t help you, and you look like an idiot. Have some respect for the developers and supporters, and post knowledgeable threads, detailing what specifically doesn’t work. And please, please, please search the forums before posting. Odds are, someone else has had the same problem.

Feel free to post any questions or comments below. I’m always open to discussion and support. I’ll be playing with Magento over the next week, and hopefully will have a positive, thorough review.

Categories: Softwares, Webmasters Resources Tags:

Magento 1.0 Released! (finally)

March 17th, 2009 No comments

Wooooo! It seems the big 1.0 has finally be released, and is out of beta. From the Magento Blog:

    To everyone who spread the word about Magento, told a friend, wrote in blogs, posted and commented in the Magento forums, subscribed to our newsletter, downloaded one (or more) of our 11 preview releases, reported bugs, participated in the Magento community, to the online merchants who waited for Magento 1.0, developers and designers who convinced their clients to wait for the product and our partners who recognized the potential — Thank you for believing

Looks like there are plenty of bug fixes and even some new features in this version! Hooray! Looks like it’s time to update the Dreamhost Magento Installation Guide.

Categories: Softwares, Webmasters Resources Tags: