I’ve developed this plugin a while ago, i’ve now updated it to a releasable version, already working up to wordpress 2.5.1

ROT13 Email Protection at Worpress Plugins

Download ROT13 Email Protection Plugin v0.1!

In order to install it, as most wordpress plugins, just put the rot13_email_protection.php file  inside your /wp-content/plugins folder.

Any bugs, give me a comment, i’ll check on it.

- ok, so it’s a biased opinion… :/

NaturePhp itself is basically a plug-in system for the coolest functionalities around – most of the upcoming functionalities are either gathered from wordpress, joomla!, CodeIgniter and others, as well as a few of our own – *and a few RubyOnRails original ideas implemented in php ;)

The functionalities are organized into classes, and the classes are organized into namespaces, providing a great deal of “space” for future plug-in developments.
It uses __autoload() for all classes, meaning it is just as fast no matter how many plug-ins you have installed.
NaturePhp does not aim being labeled as a framework, but, being a pluggable toolkit itself, it allows future developers to build their own frameworks as plug-ins. – The idea is to provide a stable ground for common development and lot’s of easy to use functionalities for developers – much like Phyton’s libraries.

We are currently using Namespace_Class::method() instead of Namespace::Class::method() and Class::callStatic($func_name, [$arg1, $arg2... $argN]) instead of Class::func_name([$arg1, $arg2... $argN]) to workaround the lack of “Namespaces” and method overloading “__callStatic()” support on PHP 5.2.6, as these two features are required for most of the toolkit functionalities.
It’s ugly, but it keeps the toolkit usable and developed while we wait for PHP 5.3.0.

As soon as PHP 5.3.0 comes out we’ll implement the necessary namespaces and change all the Class::callStatic($func_name, [$arg1, $arg2... $argN]) calls to Class::func_name([$arg1, $arg2... $argN]) – so probably a couple of weeks after PHP 5.3.0′s release we’ll have a NaturePhp 0.1 out ;)

While we wait, we’re also finishing the NaturePhp’s website at http://naturephp.org ;

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

class Test{
 
    //public props
    public $var1="Value 1";
    public $var2="Value 2";
    public $var3="Value 3";
 
    //private props
    private $var4="Value 4";
 
    //public method
    public function public_function(){
         return true;
    }
 
    //private method
    private function private_function(){
         return true;
    }
 
}

You can cycle through the public object properties as you would with an array:

1
2
3
4
5
6

$test=new Test();
 
foreach($test as $prop_name=>$prop_value){
    print $prop_name.'=>'.$prop_value;
    print "<br".">";
}

The result will be:

var1=>Value 1
var2=>Value 2
var3=>Value 3

in order to use Stored Procedures in MySQL through PHP you usually either use pdo or mysqli connections.
However if do not wish to redo your application connections and you don’t require any out parameters you can use “mysql_connect($host, $user, $password, true, 65536);” on connection, using the 65536 ( CLIENT_MULTI_STATEMENTS ) internal magic constant. But you can make only one stored procedure call per connection, and there is no support for OUT parameters. It is not currently documented, but can be found in the php header file.

If you do not use this connection method, you’ll get a “#1312 – PROCEDURE database.procedure can’t return a result set in the given context” error whenever you CALL a procedure that returns a result set.

Simply put: reinstall php – worked for me.

1. Download the latest stable .zip from php.net at windows binaries –> PHP x.x.x zip package
2. unzip the package to c:\php
3. move the content ( extension dlls ) from c:\php\ext to c:\php
4. create a test file at one of your local websites ( c:\Inetpub\wwwroot\test.php ? ) with “<?php phpinfo();?>”
5. open IIS
6. right-click on your “website” ( where you stored test.php ) and select “Properties”
7. Select the “Home Directory” tab and choose “Configuration”
8. Choose “Add”
9. Add “C:\php\php5isapi.dll” (including quotes) to “Executable” and add .php as extension. Then limit the verbs to GET,HEAD,POST,TRACE and click on OK
10. Now choose the “Documents” tab and select “Add”
11. Enter index.php and click on OK
12. Finally, select Web Service Extensions on the left side and choose “Add a new Web service extension”
13. Select “Add” and enter as path C:\php\php5isapi.dll and click on OK
14. Then enter php5 as extension name and check “Set extension status to Allowed”. Then click on OK to enable this extension
15. Now go to My Computer>Right-Click>Properties
16. Click on “Environment Variables”
17. Scroll to “path” and click “Edit”
18. add “;C:\php\” and click OK
19. Restart IIS
20. Open your  “test.php” in a browser window ( http://localhost/test.php ? )

Should be done.

To add php extensions ( curl, etc ) uncomment the dll call lines on php.ini .

Why?

- Autoload libraries ( Modules – similar to naturePhp’s toolkit system ) is a default system;
- a small core;
- namespaces and modules;
- indentation is used to mark out block structure rather than curly braces – much cleaner code;
- everything is a reference!
- a simple array slicing syntax;
- lambdas and other built-in functional programming constructs;

I always asked myself why Google uses so much python, now i know.

I’ll still be working on naturePhp and with PHP in general, i still think PHP is much more easy to setup and learn, as well as more resourceful, and most of the shared server environments use PHP, so naturePhp toolkit is continuing to be a must have – especially with the oncoming namespaces on PHP 5.2.3 ;)