mattinahat99

Was it that obvious?!

Hi, Just wanted to let everybody know we're offering, for a limited time, a free website review. We'll take a look at your website for free and let you know if there is any room for improvement or potential to make your website more effective for your business or organisation. All we need is your name and website address and we'll do the rest. To take advantage of this just follow the link below! http://www.bluestagstudio.co.uk/freereview.php Many Thanks, Matt.

You'll need AJAX to make the form gray out before submission. Alternatively you can use a javascript function when the form is submitted to check for any "no" answers, if it finds any then it will display an error and return to the page. HTML form <form id="feedback" onSubmit="return checkform()"> <input type="radio" id="field1" value="yes" />Yes <input type="radio" id="field1" value="no" />No <input type="radio" id="field2" value="yes" />Yes <input type="radio" id="field2" value="no" />No </form> Javascript Code function checkform() { if (!document.feedback.field[0].checked || document.feedback.field[1].checked) { // field[0] would be the yes button, field [1] would be the no button alert ("cannot proceed as you have answered no to one of the questions"); return false; } if (!document.feedback.field[2].checked || document.feedback.field[3].checked) { // field[2] would be the yes button, field [3] would be the no button alert ("cannot proceed as you have answered no to one of the questions"); return false; } return true; } To be honest, this is a crude and not very well thought out solution, if you have a lot of questions it might take a while to check. I think you'll need AJAX for this one. Anyone good with that? Cos i aint!

Ok, not sure where you are in the process but here are the basics. 1. In the HTML form you need to define your form like so <form name="uploadform" enctype="multipart/formdata"> 2. Assuming you have already created the PHP file upload script you should have a variable somewhere in the script that looks like (where imgfile is the name of the file upload field in the html form) $_FILES['imgfile']['name']; 3. To create your link path for the database all you need is a string that looks like "graphics/imagename.jpg" which you cna get by using the following code. $dblinkpath = "graphics/" . basename( $_FILES['imgfile']['name']); 4. Just add $dblinkpath to the database in the normal way. Clearly, there is a hell of a lot more to uploading a file than this, but i'm assuming you already have the upload script and just need to put the link to the image in the database. It may be worth adding some sort of timestamp to the image so that it can't be overwritten by another user uploading an image with the same filename To do this you would need to add the timestamp to both the image upload script and the databaes link

Just to highlight another point by OP! In fact, it goes even deeper than that, one of the hardest things to implement in a CMS is the What You See Is What You Get feature, for example a Microsoft Word type editor in the CMS that allows you to change font size, colours, insert images etc. Out of all of the web based CMS sytems I've seen I'd say over three quaters of them use something called TinyMCE. It's a very clever javascript application that converts a HTML text area into a full fledged CMS within itself. I've used it in my CMS too! Point being that whichever route you go down (build your own CMS, joomla, BlueStagStudio CMS - well you never know!) you will probably encounter TinyMCE. Why am I telling you all this? It's buggy as heck and it might take a while to get it working as it should, but they do have very good support forums and a massive following because its used in so many CMS systems. There we go, another essay style answer with hardly anything relevant in it. Slow day. lol.

I'm probably going to start world war three here but i disagree! There are indeed many CMS's out there, and some of them offer amazing functionality for free. The problem is, the whole point of a CMS is to make it easy for a solicitor, florist or artist to update their website without any intervention or training from a website developer. While I have found many useful CMS's, I have found very few that I would happily pass on to my technophobe Mother to use! The problem I find with most CMS systems is that they are just a cut down, slightly harder to use version of Dreamweaver. And while they offer huge functionality, non-web development businesses won't be interested, all they will want to do is add another image to their gallery or change a phone number or add their latest press release or news article. There are of course exceptions. When we started our web development and marketing company we were looking at plune, a popular open source CMS. But after it took me about a day to work out how the hell to use it it suddenly dawned on me our clients would hate it. So we built our own. It's a small system and it doesn't do much but it does 99% of the things our clients will want to do and makes it a hell of a lot easier to do it. So, long story short, if you want a CMS that even the worst technophobes could use without having a panic attack then building a CMS for that purpose isn't reinventing the wheel, it's improving the wheel and adding more grip because you're making it from scratch with your clients needs in mind, something the original wheel makers won't have done. Well, that's my two cents anyway!

I know this may sound obvious, but if you need help in the future it's best not to display your database password, I know you didn't give us a link to the website but there are some people out there that scan forums looking for situations like yours, finding your site and hacking in. Also, if you're gona get into alllowing people to insert data into your database I'd strongly advise you learn about "SQL Injection Attacks" before hosting anything live. Just a quick heads up!

What this is saying is that you haven't set a background colour but you have set a text colour. So if your footer just happened to be displayed on top of something else that was white, or your page background was white, then you wouldn't see the text. This is a WARNING though and not an ERROR. It's simply suggesting that if you wanted to redesign your site at any point and you decided to have #fff as your background colour then you wouldn't be able to see the text. If you want to get rid of the warning you'll need to set a background color for the footer, just match it to the rest of your site. So...for example. .footer{ font:bold 11px/12px Verdana, Arial, Helvetica, sans-serif; background-color:#000; color:#fff;} Hope that helps.

looks like rachael got there first!

looks like rachael got there first!

As long as you delete index.html and only have index.php then index.php will be your homepage.

Download the latest version of Opera, it is by far the most standards compliant browser. That means that if you can get it to look good in Opera it should look good in Firefox, Safari and IE8. You'll still have to test it on IE7 and IE6 as, has been mentioned before, they're pants and dont interpret correct code correctly. So you may have to add or modify your code to make sure that it is still standards compliant but also in a way that IE will display it correctly.