There are a lot fo postings on the internent forums about a problem people experience with trying to create a new website in Dreamweaver to work with a dynamic serverside technology like PHP/MySQL or ASP.NET or ColdFusion.

When you get to a point to specify the URL of your website, which should be in the form: http://mydomain/mywebiste/, if you happen to be wirking with a brand new website (that by the way may be perfectly well setup) you may get the followig error from Dreamweaver:

“Dreamweaver cannot use the prefix you entered to display live data. Please double-check your site configuration or click on Help for more information on how to correct this problem. (HTTP Error: 12029)”.

Dreamweaver calls the URL you were trying to specify a prefix becuase it intends to correcly use in front of every web page that you are going to have on your website, or in the most complex case – a subdirectory and then page name.

The problem will be experienced especially wiht brand new websites. Again the websites might have been configured perfectly and they may local (on your workstation, PC, Mac) or remote websites.

A working solution:

I was looking for a solution for this problem that I experienced myself.

The text from the error Dreamweaver throws is allover the internet with no practical solution. The most I have found is – “well Dreamweaver needs to be configured” and stuff like that. I played quite a bit with this since I wanted to resolve it. I have webmaster and web development experience now 12 years but never worked with DW. I always used non WYSIWYG editors and I thought I will try the widely admired Dreamweaver. So I wanted to start on the right foot and figure out the problem.

This is what I did.

I was starting a new website on which I had perfectly well installed PHP and MySQL as with the dozens ones I installed before and I even wrote a few short scripts involving both PHP and MySQL to test the HTTP / PHP / MySQL / Apache stack is working fine.

This did not help Dreamweaver identify that there is a working website installed.

Then, though this was the site I wanted to connect with I tried direct DW to one of my existing sites – and that worked – it identified them. “OK, so what is the difference?”, I thought.
Well, one difference I could think of was that all other sides had a default page already set up – one that will return a valid HTML page to the browser if I typed just the website address (http://mydomain.com/mywebsite/ )
even if I do not enter a page name. Of course in most cases on your web server that is set to be index.php, index.html or default.php etc. I mostly use index.php.

So I created as simple index.php – made sure it shows up on a browser and the tried to put the website address (without the page name, as initially instructed by DW) and everything worked.
So when you are at that stage of setting up a new site on DW, in addition to setting the website (which you probably did perfectly already) go ahead and add a default page (if PHP server technology a index.php) and test it responds to the website address. This should let the DW go through that stage perfectly.

Obviously Dreamweaver has no way to identify a healthy response from the website unless there is a page that returns valid HTML when the website address (without a pages name) is requested.

I guess if you are using a different technology – .NET or Cold Fusion you will need a default page like that in the respective technology or simply in html.

Happy webmastering!

TopWebGuy.com