trq

com

This topic has been moved to mod_rewrite. http://www.phpfreaks.com/forums/index.php?topic=352032.0

You should be able to find plenty of example on this board. Or google a tutorial.

You do that by using mod_rewrite. Nothing to do with creating a new directory for each user. With mod_rewrite you can rewrite a url such as example.com/member to example.com/profile.php?user=member allowing you to use a single profile.php page for all users.

This topic has been moved to MySQL Help. http://www.phpfreaks.com/forums/index.php?topic=350684.0

1. Yes, check with your hosting. 2. A user needs to add an image themselves.

You learn JavaScript and then you learn about the extra functionality that jQuery provides. In fact, jQuery is so simple that allot of people skip learning JavaScript all together. Though I wouldn't recommend that approach in the long run, jQuery is pretty darn easy to get started with. See http://docs.jquery.com/Main_Page

You can write JavaScript with any text area. Dreamweaver will just write bad code.

1. That completely depends on your hosting. 2. that has nothing at all to do with php.

Including a file via a url is not the same as including a file directly. You will only receive the output from the file, not the variables, classes and all the good stuff.

Firstly, we have tags that you should use when posting code. Notice how all the other posts are nicely formatted and easy to read? Now, on to your issue. PHP's mail function cannot send email via mail servers that require authentication. You will need to look into and use a third party library such as SwiftMailer (Google it).

Where exactly are you stuck?

It definitely doesn't look like it is configured properly. This has nothing to do with php.

This topic has been moved to Other Libraries and Frameworks. http://www.phpfreaks.com/forums/index.php?topic=351896.0

Do you have a mail server installed and configured?

Your question makes little sense. The .tpl extension is not generally related to php. We are going to need more details.

No you don't have to put the [ and { in there manually. json_encode encodes php arrays and objects into json notation. Without seeing your current data structure we can't be of anymore help. Not that we are here to write code for people in the first place. Have you actually tried to have a go at this yourself? Why not post your problematic code?

It's likely your servers user doesn't have sufficient permissions.

This topic has been moved to Other Libraries and Frameworks. http://www.phpfreaks.com/forums/index.php?topic=351914.0

Actually, that is probably going to be more difficult than it seems as PHPUnit swallow most of the output. I might have to mock up some tests outside of PHPUnit. What a fucking waste of time.

Yeah, I'mg going to have to do something like that when I get home. I'll let you know what I discover.

This topic has been moved to JavaScript Help. http://www.phpfreaks.com/forums/index.php?topic=351866.0

I din't look at your code but if your trying to use Google's smtp server with php's mail function you can't. PHP's mail does not support authentication.

Generally you wouldn't even need to call "use Chain" because Chain is in the same namespace so you can just go ahead and use it. As the link to the "cascading filesystem" stuff points out however, it's not so simple in this case. All classes within Proem are actually created in the Proem\Api\ namespace. However, when you go to use one you must always use it from Proem\ Lets use Foo as an example: use Proem\Foo;{/php] This searches the Proem namespace for Foo, when not found, it will then search Proem\Api. Once located it will alias the class to Proem\Foo and give you access to it. Interanally all classes are declared in Proem\Api\ yet used from Proem\ This means that a user can override the functionality of Foo throughout the entire framework without needing to hack the framework itself. You would simply create a file within the Proem namespace and extend Proem\Api\Foo [code=php:0] namespace Proem; class Foo extends \Proem\Api\Foo {} Now, anywhere (including within the framework itself) that access Proem\Foo will get your new class instead of the original one declared within Proem\Api\Foo which it would normally get. I understand that there is a bit going on here, but this functionality allows great flexability and for the most part it is working. I'm at work at the moment but will be investigating this issue tonight when I get home as it is blocking progress. I'll let you guys know if I find a solotion. I already had an idea of moving all components into there own namespace anyway (not because of this issue), so this might be the raod I end up travelling down. Thanks for taking a look.

Oh, and using Proem\Chain should (under the hood) end up calling Proem\Api\Chain. This cascades down into Proem\Chain.