requinix

It's right there in your $s query. Why do you think they're defined at that point? You do define them later on, that's true, but it doesn't help $s.

If you've figured it out yourself, how about posting what you did so everybody else can know about it too?

:selected + .text() is the simplest answer...

What's your code.

The rest of the code is using mysqli so you need to use mysqli for that check too.

Then what do SHOW CREATE TABLE whatever_your_table_is SHOW VARIABLES LIKE '%char%'output? And is this site somewhere we can look at?

Where's this "__getLastRequest" coming from? It's the $_last_request and $_last_response properties. As in $proxySales->_last_request

I wasn't sure but it seems RewriteRule .* -[L]the space you're missing there is required after all (mod_rewrite considers the replacement to be "-[L]" instead of "-" with the L flag). The PHP error is due to you using parse.php to handle a file that isn't *.php, which is very clearly cannot support. It also won't work for files that are two or more directories below the web root. I suspect there are other problems too but I'm tired and need to go to bed.

That URL you gave is not to a WSDL. Go to it yourself and see.

How would you, as a human, know what to change about the markup? How do you know which item gets two fas (really?) or whether it should be called "cutlery" or "rss" or "refresh"? Once you have that answered it shouldn't be hard to make the code do it.

The rule is forbidding access so you don't want it. At least not in that form. Does the image exist at that path (if so, are you absolutely sure?) or are you trying to route it through parse.php?

And the script was not working before? With your .htaccess as Options -Indexes RewriteEngine On RewriteCond %{REQUEST_FILENAME} -f [OR] RewriteCond %{REQUEST_FILENAME} -d RewriteRule .* -[L] RewriteRule ^(.*)$ parse.phpthen existing files and directories (the RewriteConds) will be served unchanged (the following RewriteRule) and the remaining stuff that does not exist will go through parse.php. What you're saying is that with the above .htaccess, - images do not work - are you still getting a 403? - /style.css does not work - are you still getting a 403? - parse.php does work Right?

IDs are unique. You cannot label more than one thing on a page with the same ID. Use classes instead. A class, in this case.

Well, there's the RewriteCond %{REQUEST_FILENAME} -f [OR] RewriteCond %{REQUEST_FILENAME} -d RewriteRule .*\.(jpg|jpeg|gif|png|bmp)$ - [F,NC]that explicitly forbids access to images... And you know that RewriteCond only applies to the next RewriteRule? So the RewriteRule .* -[L]will always execute? If you were relying on parse.php to handle /style.css then this would explain why it doesn't work. Also, include() is only for PHP code. If style.css does not contain PHP code then do not include() it.

Not really. Set the "trace" option, then look at SOAP_Client's $_last_request and $_last_response properties.

I'll try again: What is the output of the query SHOW CREATE TABLE userdata

- The table columns (the text ones) need to be in utf8 format - The table itself and the database should also have it as the default encoding - You need to be connected to the database using utf8 encoding before any data is exchanged - Your code needs to treat all strings as multibyte strings - that means no strlen() or substr() (and others) and instead using the mbstring extension's equivalents - Your Content-Type response header and/or webpages need to mention the utf-8 encoding

What does SHOW CREATE TABLE userdata say?

Can you get the raw XML generated during the request? That'll make it easier to understand what's going wrong.

That tutorial sucks. You need to find another one. Bad/outdated information, poor practices, SQL injection, XSS, deprecated extensions... a whole host of problems with it that are showing up in your code too. Did you happen to create your table using something like CHAR(16) for the password column?

There's a lot of overlap though. "foo.jpg" is actually a valid domain name (which does not exist but that's not the point). So is "localhost". I'd say the determination between domain name and path should be done explicitly in code. For starters I wouldn't expect domains to be mixed up in routes - more like routes are added to configured domains. But with your current structure I'd think something like public function add_route($path, array $args, $domain = null) Router::add_route('/', array('controller' => 'shop', 'action' => 'items'), 'shop.bisi.bid');

PHP 5.3 has been entirely unsupported for almost a year now. Even 5.4 is only receiving security fixes. Their inability to keep up with changing times is worrisome. PEAR's SOAP is not the same as the bundled version. For one, it doesn't have the SoapVar class which is why you're getting that fatal error. There is a SOAP_Value which sounds equivalent, but it's not identical. Maybe 'Item' => new SOAP_Value( 'Item', // name 'Service', // type array('ID'=>'1357') // value ),

Sounds like $pwd is wrong. What's the rest of the code? Be sure to use tags when you post it.

Not many people are familiar with SOAP. Are you sure SOAP is installed at all? And why are you using PEAR for it? And why are you still on PHP 5.3?

"Valid domain" is broader than you probably realize, what with IP addresses and IDNs and such. How are you going to use this and how strict/precise does it need to be?