Package:
Summary:
Store and retrieve cached values from single file
Groups:
Author:
Description:
This class can be used to store and retrieve cached values from single file.
It can store one or more keys in a single cache file.
The class can also look up for a given key and retrieve the store value.
It can lock the file during access to prevent corruption, but there is also a sub-class that can be used to access the cache file without locking it.
It can automatically clean-up the least recently used entries to free space.
Package:
Summary:
Extend class functionality with code define in XML
Groups:
Author:
Description:
This class functionality is extended class functionality with code define in XML.
It loads plug-in code definitions from a XML file that contains additional code definitions that are imported into a MySQL database.
Later the class can load the plug-in code from the MySQL database and execute it.
Package:
Summary:
Extend class functionality with code define in XML
Groups:
Author:
Description:
This class functionality is extended class functionality with code define in XML.
It loads plug-in code definitions from a XML file that contains additional code definitions that are imported into a MySQL database.
Later the class can load the plug-in code from the MySQL database and execute it.
Package:
Summary:
Analyse HTTP requests to detect security attacks
Groups:
Author:
Description:
This package can be used to analyse HTTP requests to detect security attacks.
The main class analyzes the HTTP GET and POST values to determine if contains words that can be used to perform SQL injection attacks, mainly to MySQL applications.
It returns the information that based on a score of the word analysis it may be a security attack, so the applications avoid handling the request.
Another class can generate log files in XML format with more details about the eventual attack.
Package:
Summary:
Analyse HTTP requests to detect security attacks
Groups:
Author:
Description:
This package can be used to analyse HTTP requests to detect security attacks.
The main class analyzes the HTTP GET and POST values to determine if contains words that can be used to perform SQL injection attacks, mainly to MySQL applications.
It returns the information that based on a score of the word analysis it may be a security attack, so the applications avoid handling the request.
Another class can generate log files in XML format with more details about the eventual attack.
Package:
Summary:
Iterate over the uploaded files list
Groups:
Author:
Description:
This class can be used to iterate over the uploaded files list.
It can retrieve details of the $_FILES array and rebuilds the array to include the each uploaded file as entry of the array of details for each file.
The class inherits from the ArrayObject array so the resulting files array can be traversed with regular array access functions.
Package:
Summary:
Iterate over the uploaded files list
Groups:
Author:
Description:
This class can be used to iterate over the uploaded files list.
It can retrieve details of the $_FILES array and rebuilds the array to include the each uploaded file as entry of the array of details for each file.
The class inherits from the ArrayObject array so the resulting files array can be traversed with regular array access functions.
Remember when I posted earlier about the Twitter account, and I said that hopefully you’d find out later today what has been keeping us all so busy? Beta testers, this is your moment: the WordPress 3.0 Beta 1 has arrived!
This is an early beta. This means there are a few things we’re still finishing. We wanted to get people testing it this weekend, so we’re releasing it now rather than waiting another week until everything is finalized and polished. There’s a ton of stuff going on in 3.0, so this time we’re giving you a list of things to check out, so that we can make sure people are testing all the things that need it.
You Should Know:
- The custom menus system (Appearance > Menus) is not quite finished. In Beta 2, the layout will be different and a bunch of the functionality will be improved, but we didn’t want to hold things up for this one screen. You can play with making custom menus, and report bugs if you find them, but this is not how the final screen will look/work, so don’t get attached to it.
- The merge! Yes, WordPress and WordPress MU have merged. This does not mean that you can suddenly start adding a bunch of new blogs from within your regular WordPress Dashboard. If you’re interested in testing the Super Admin stuff associated with multiple sites, you’ll need some simple directions to get started.
- We’re still fiddling with a few small things in the UI, as we were focused on getting the more function-oriented code finished first. For example, we’re getting a new icon for the Super Admin section.
Things to test:
- Play with the new default theme, Twenty Ten, including the custom background and header options.
- Custom Post Type functionality has been beefed up. It’s really easy to add new types, so do that and see how it looks!
- WordPress MU users should test the multiple sites functionality to make sure nothing broke during the merge.
Already have a test install that you want to switch over to the beta? Try the beta tester plugin.
Testers, don’t forget to use the wp-testers mailing list to discuss bugs you encounter.
We hope you like it! And if you don’t, well, check back when beta 2 is ready. 
Download the WordPress 3.0 Beta 1 now!
This post is about the @WordPress Twitter account, so if you don’t use Twitter, or don’t care about Twitter, then feel free to take the time you might have spent reading this post to go play outside (or an equivalent) instead.
Okay, so, Twitter! When all those apps started popping up using the Twitter API, things like automatically following anyone who followed you and sending an automatic Direct Message seemed like good ideas. We’re all friends, right? Wrong. That auto-follow bit us hard, and the huge amount of spam the account gets means that it’s been nearly impossible to monitor legitimate messages from WordPress users and developers who need to be pointed to a help resource. We’re sorry! Just as we needed to get the Ideas Forum under control* so that it could become a more useful resource for the community, we needed to get rid of the spam clogging our Twitter arteries. Except there was no easy way to do it.
We had wound up following over 50,000 people. If someone went to the @WordPress profile page on Twitter to see the stream of updates from people we followed, almost none of it had anything to do with WordPress or the community. Diet pills, Twitter scams, and multi-posted spam messages were the norm. Yuck! Who else wishes there was Akismet for Twitter? Unfortunately, there’s no easy way to clear this stuff out quickly (mass unfollows trigger their TOS alert, so it’s not surprising). I even contacted Twitter directly to see what the options might be, and it was suggested we use a script to clear the account. To be clear: Twitter flagged our account so that when the script was run they wouldn’t mark us as spammers for violating the TOS with a mass unfollow. We communicated with them beforehand, and the use of scripts to do this is not encouraged. Twitter was doing us a nice favor to help us get our house in order. Thanks, Twitter! Last night I ran the script and removed everyone. Extreme, but in good cause, right?
We’re now starting to re-follow real people from the WordPress community. There will be no more auto-follow. If you are a WordPress developer, designer, blogger, fan site, whatever — and think your tweets should appear in the @WordPress updates stream, then send an @ reply to us and we can add you to the new list (assuming you’re not hawking diet pills, free iPads or ways to get a million followers). This way, people who are new to WordPress and go to check us out on Twitter will (hopefully) get a sense of the vibrant community that we have. People who send @ messages to us won’t (hopefully) wonder indefinitely why they were ignored, because without all the spam, maybe we can use Twitter as it was intended to be used, as another channel of communication.
And for anyone who uses Qwitter and thinks @WordPress stopped loving them because of the last tweet they posted before the script ran… sorry! It wasn’t like that, we swear! It would be nice if the script could have done a bulk DM before the removal, but nope (otherwise we’d have included a message about this). So trust us, we still like you! And if you haven’t already been re-followed, please don’t take it personally… just send an @reply to @WordPress (tell us how you use WordPress!) and we’ll try to get you re-added soon. Later today (hopefully) you’ll find out what’s been keeping us so busy!
*Have you noticed? We cleared out thousands of old threads, added categorization, and will try to keep it to under a hundred open idea threads at a time so that they can be managed in a timely fashion. Check it out and rate some of the new ideas today!