Adam

I think it's difficult to understand what you're saying because "table" is a database term. Do you have the data within a CSV file, or within a database table? Or is it both? If both, is the CSV file created from the database table, or the other way round? Do you have access to both?

You should detect the key code sent within the event object and act accordingly. You'll need to post your code if you're having any specific issues.

Have you considered styling a submit button as a link by the way, to avoid the JS dependency?

I think you need to change the top banner, just to give the site its own identity rather than looking like every other Bootstrap site. The layout of the pages are good though; everything seems straight forward and easy to use. Obviously Bootstrap handles a lot of the design aspect for you, but you've managed to keep things well organised, balanced and clean. While I think you've made a cracking start though, you're site is too much like Facebook to compete with Facebook. You're not going to convince millions of people to switch to a near identical service, that lacks a lot of the features and friends they've grown accustomed to. Instead you need to find a niche within social networking you can exploit; like Twitter and LinkedIn did for example. Not enough people want a new Facebook. You also need to consider how you're going to open up your database for people to integrate with. An API is just as important as the actual site these days. How have you written the internals of the site?

Merry Christmas one and all! I'm off to see the folkes for a few days tomorrow, so all the best and have a merry new year!

I got accuracy of 81.6%, 44.2 words p/minute. Not sure if that's good or bad?

There's no need to use an extension, just hit F12 to open developer tools.

How do you expect Facebook to reference the page, unless you have a unique identifier for it? You need to have a unique URL for each post.

You seem to be forgetting backwards compatibility! I don't really see the need for #2 - why would you need to define a class or interface within a class? Doesn't that break single responsibility? I'm not keen on the sytnax proposed for #5, doesn't seem to add anything other than changing "const" for "enum" and wrapping them within curly braces. Out of the two, I prefer the current way. What would be better IMO, would be to name the enum so you can group constants, and have some way of accessing them and being able to check if a given variable exists within the group. Perhaps something more like: class Foo { enum BAR = { BAZ = 1, QUX = 2 }; } // Either Foo::BAR->BAZ // 1 // Or Foo::BAR_BAZ // 1 // Then Foo::BAR // [1, 2]

Okay, think you should have introduced your project a little earlier The comments I wrote at #8 were answered on the next page.

Also.. Shouldn't there be an option to optionally define a type for each parameter, like in #4? Forcing a type is going to break about 99% of PHP scripts out there.

The backgrounds are transparent because you're using rgba values, which some versions of IE (probably all except 9) don't support. Fortunately with CSS, any property value that isn't valid is ignored. That means you can stack up multiple values for the same property, with your safety first: background: #000000; background: rgba(0, 0, 0, 0.; /* IE will ignore this */ Edit As for the tool you mentioned, Browser Shots is useful for testing your website looks okay across a wide range of OS' and browsers. Unfortunately though there's no tool that can tell you what's actually wrong. You have to work it out.

Sounds like you're approaching this the wrong way round; you need to change the styles so that the website is by default fit for 1024x768, but then allowed to stretch for larger monitors. Generally this can be done by specifying a min-width instead of a width, however I can't say on what elements because you're not posting your mark-up. There isn't really a 'one size fits all' solution to this, because it's not just the header wrapper that needs to grow, but you have to consider every single individual element within the header wrapper as well. Again though, we need to see what you have in your header to know what you need to do.

Fiddle I created to test it, if it's any use to anyone else: http://jsfiddle.net/MEJKK/

Not bad, though I would have it display immediately, as opposed to waiting a second before showing itself. Also there's not much room for customisation, and I think more people would use it they could set the date/time of an event, as opposed to an arbitrary number of seconds. Lastly, the API leaves a lot to be desired. I would bet that after meeting the functional requirements, the next decision maker for people looking for scripts to use would be the API. They want it easy. Is there no reason you can't just pass in an element and the function update the styles?

How exactly do you want it to resize? You need to be a little more specific - a screenshot or link would help a lot.

Can't spot anything wrong with it. Is the error definitely coming from that line?

I think this is probably the major issue for me as well. "How the story started" doesn't really draw attention as the first entry, it sounds more like the quirky title of an about us page. Given it also follows directly on from the rules with no change to the format, that doesn't help make it stand out either. I would use a different font for any story text along with a subtle background, consistently across the site. That will allow people to easily recognise what's the story and what's not. Perhaps experiment with some nice serif webfonts (for example, search for "mate" and switch to size 14.) Just be careful with serif fonts; they can make a website look great when used sparingly and selectively, but there's a thin line before they start to ruin a site. I can't see one working with your current design though to be honest, you need to liven it up a bit first. As for the idea of the site, I quite like it. I think in it's current form though you're going to struggle to get regulars. You need to integrate with the likes of Facebook and tap into a huge user base rammed with people that love this kind of thing. I know you have a like button, but I mean proper integration. Write an app people can add that will post entries to their wall and that, which will increase traffic to the site. Perhaps allow them to login with Facebook too, so the transition between the two is seamless. Did you draw the image yourself by the way? I would digitalise it to improve the colours and sharpen it up a bit.

Perhaps capacity wise, but until you get those users you don't know how much resource each website will suck up.

Ok so you definitely have the PHP extension installed, what about the libmemcached library? Does Apache report any errors during start-up? Run this in a terminal: tailf /var/log/apache2/error.log Then restart Apache and observe the log lines. Anything suspect?

Ah, well spotted kicken!

The PDO constructor throws an exception if the connection failed. You keep posting different code; can you modify the original code to this and report back what it says: //PDO Fetch Statement $query = $db->query("SELECT `id` FROM `Admin`"); if (!$query) { var_dump($db->errorInfo()); exit; } while($row = $query->fetch()){ echo $row['id']; } FYI this isn't the way to handle erors, it's just to debug the problem.

That means there are no results from the query.

Well for one, the SQL in your PHP4 example is different. That doesn't change that the query is failing though. Have a look at PDO::errorInfo() to get more insight into what's going wrong.

Have a read of the manual for PDO::query(). If the query fails, false is returned, not a statement object.