redbullmarky

often if you have shared hosting, you cannot run shell scripts via PHP. http://www.php.net/shell_exec To be honest though, you're pissing up the wrong tree here IMO - if you get this script to work, it will remove the said trouble lines. however - you should probably be looking for the code that was used to cause the exploit in the first place so that it CANT happen again. Else you're just gonna be running this script only for them to come back and do it again.

many job boards are started by people from the recruitment industry who have specific experience dealing with certain clients. I know someone that started a construction job board after working as a construction recruitment consultant. There are two ways he explained: 1, contacting his old favourite clients (especially the big ones that are familiar to the jobseekers in the particular industry) and telling them what you're doing and for a limited period they can list jobs for free.There's a lot of job boards out there so yours had better have something unique that you believe in so you can make the client believe that they're going to benefit. 2, asking clients if you can take their jobs from their site and publish them on your own. 3, subscribing to job sites that allow you to use their listings. all the above is done before a proper launch, just to let Google have a little look around your site. Plenty of facilities such as "tell a friend", etc all help to get things moving by word of mouth, although the chap I know kept in touch with many of his old jobseekers and started from there. once things start moving a bit - invest in some advertisements.

erm ... can you give more information? are these even written in PHP? have you read any of the module docs to see if they have any information about integration? or contacted the module developers? have you tried anything yet? or considered anything? please - you need to be FAR more specific in your question, including things you've already tried so we don't waste time helping when it's something you've already covered. we're not mind readers.

using __set and __get magic methods can have all sorts of nice uses. personally i use it for 'models'. So: <?php class User { private $data = array(); // holds user record data public function __set($varname, $value) { $this->data[$varname] = $value; } public function __get($varname) { return isset($this->data[$varname]) ? $this->data[$varname] : null; } } $user = new User(); $user->email = 'test@test.com'; // sets User::$data['email'] ?> this way, i know that the $data property ONLY holds info about the user, not tonnes of other unrelated properties. You can also use these magic setters and getters to control what can or cannot be set from outside the class - ie, enforcing a certain way of using your class.

to be honest, with offline promotions, using subdomains in this way is probably your best bet - you're right when you say it's far easier to remember, because i personally wouldnt both with the query string if that was presented to me. Doesn't have to be subdomains though. A similar (though maybe easier to set up) is a method we use frequently at work - mysite.com/promoname where promoname is the short representation of your promo. eg: mysite.com/miami

as in: nothing works = blank screen? or nothing works = loads of errors? the differences i've found between 4 and 5 are fairly big but when i upgraded my server that's got a fair few sites on it, only a few "broke" but very minor and easy to fix issues. Often they were my site throwing 'Notices' due to the error reporting being set differently and the odd one or two things that threw Warning messages in PHP5 that didn't in PHP4.

i'd possibly suggest "I didn't bother looking on Google for 'php user management script'" as the title http://www.google.co.uk/search?q=php+user+management+script

Fan sites are also grey-areas, falling under the "Why bite the hand that feeds?" unwritten rule of how not to massively piss off your fans. No fans = no club. As Daniel said - get permission first, but I really can't see the issue. In effect, if your site is completely dedicated to the club, they're getting a site and exposure for free. If it was me personally - I'd register the domain first, ask questions later, then build the website once you've got the thumbs up. on the other hand - pop the name of a football team into google, followed by "fan site". You'll see domains referencing famous things regarding the club without actually mentioning the club itself. For example - I'm sure you can guess which club the following fansites are dedicated to: www.redandwhitekop.com www.thisisanfield.com www.lfconline.com www.koptalk.com www.anfield-online.co.uk www.ynwa.tv etc etc

not 100% but Apache directives could be case sensitive. so rewritecond != RewriteCond rewriterule != RewriteRule http_host != HTTP_HOST etc you might want to have a look at the docs for examples with the correct case.

Tools >> Add-ons >> Extensions pick the one you want to disable and click 'Disable'

like a kick in the nads...

sure - i just mean that if he has [WLX]AMP[P] installed, the MySQL service runs so that other software on the computer not necessarily having anything to do with the package can still use MySQL without having to further "configure WAMP" or anything else for that matter. Just the details requested should do the trick

just install WAMP (or XAMPP), get it running as a service and put in the details as required. you shouldn't have too much difficulty - MySQL is not completely "confined" to WAMP as far as I know, it just runs as its own separate service. and to be honest i've not heard of the software in question so not a clue what it does, so if you can give more info or a link, maybe others will be able to help further?

personally, as long as the site posted for critique is not complete turd, or trying to sell me viagra, and doesn't break the forum rules, I'm cool - I've learnt a fair bit myself about what I do/don't like in websites just by seeing what other "non-professionals" come up with and what people say. So even if I don't actually offer a critique, I can still get something out of it.

i suppose in a way, you could say that you're using multiple pages in that each page has their own file. the difference being in the implementation - instead of using files and directories and calling the file straight from the URL, you set your server up to "funnel" everything through one single index file, and include the page-specific content as required based on the URL parameters.

messy. the advice given before is sort of achieving the same thing in a similar way, just far more maintainable. using opening/closing tags left, right and center in this way will just confuse you and whoever else has to maybe deal with your code in the future. your example has just a few basic lines. imagine sneaking an entire webpage in there, and then trying to navigate around your code page to find certain pages to make amendments....

no offense cordoprod, but your response to mine was almost as if you dismissed it without reading - and now i'm starting to sort of wonder if there's a difference between you asking for someone to supply you with a name and someone supplying you with your ideas for you. considering you'd be the one making the big bucks off it should it take off, i'm sure you can see why i'm personally not really keen on sharing ideas or names. chances are - if i find a name that's good, i'll take it for myself. good domain names are hard to come by these days... additionally, site names are very personal and specific to a project/person/company so it's probably better you try and come up with a name yourself. take my previous advice, if you like.

having everything feed through one single script is my own way of doing things, as it makes cross-site updates much easier - ie, just adding an include to one single file to affect the entire site, etc. however i wouldn't recommend you put all your code in one page, but rather include in the files and keep specific page code in their own files. might be worth taking a look at a framework to see how they go about it - CakePHP, Zend, CodeIgniter et al all operate in this sort of manner.

depending on what you want will determine what you need to store. if you just want a relatively simple "how many online", then on each page hit, store the user's ID (if applicable, else store zero to signify a guest), IP address and the timestamp in the database. after that, just an SQL "SELECT" to get the number of unique IP's from the table created since a particular time (ie, within 5 mins). problem - if a group of users from, say, a company, log in - ie, they all share the same IP address - then you might cause confusion. best way (though still not 100% accurate) is to use custom sessions as I mentioned in my last post. Regardless of IP, the session id will be unique to each user. So get your custom session handler to store the session id, user id and timestamp (along with the session data - read the notes within the manual for session_set_save_handler) when the user hits the page and do the query as with the other method. like i say, this is the most common way of doing it as used by many forums and CMS's, so is probably your best and most reliable bet.

not quite that harsh. basically they persuaded him to hand it over and in return gave him some little bits and pieces. http://www.theregister.co.uk/2004/01/26/mike_rowe_goes_soft_hands/ personally I reckon he didn't stand his ground nearly enough, especially as (in his case) he had a legitimate reason (or could have) for owning that particular name. He could have got more than a bloody Xbox....

for that sort of price, and seeing how much work is involved in a decent cart, i'd say that it's 99% certain they build around an existing one.

sounds like you need to work out the logic before you start coding. once that's sorted, you shouldn't have too much difficulty coding it. what are you trying to emulate? ie, what sport?

it's not really anything specifically OOP - it can be done in a number of ways. The way I do it is to use custom sessions - ie, storing the sessions in a database so that sticking stuff in $_SESSION will put it into the database instead of into files. This way I can query who is online, where they are, etc. SMF I believe does this, as does phpBB etc. Take a look at session_set_save_handler() for more info to see if this is what you want. Simpler ways would just be to log a URL and a timestamp each time someone hits a page, then just querying who has been on a certain page within a certain time. 2-5 minutes is realistic enough as there's no real nice way of knowing whether someone is still actually viewing the page, just idle, or closed their browser tab.

CMS Made Simple probably one of the better ones for 'intermediate' stuff. It's easy enough to modify and comes with a fair few plugins to get you started. Like any of them though - they will take some work and effort to learn its internals to get it to work how you want it or to write plugins for it. Other CMS's, e.g Joomla, might offer more to get you started but I've found it to be quite complex when it comes to extending it to do custom stuff. Best bet - go to Open Source CMS website and play around with a few. You might find one or two that do what you need without any/much modification at all.

try Plugin::$plugins = $plugins; as it's a static property