Norbet Mocsnik's Blog: Setting Up DokuWiki with Simple Authentication
684711
Norbet Mocsnik, having just set it up himself, is sharing the steps needed to get DokuWiki set up and working with a simple authentication system.   I promised to investigate the steps needed to set up DokuWiki with the simplest authentication scheme for a friend and I thought others might benefit from it too, so here it is.   There's about fifteen steps in all, including the download/install of the package and creating the basic functionality (like a simple Auth schema - he gives an example). Create the superuser and set up the desired restrictions and you're home free. If you want more information on authentication in DokuWiki, check out this page on the DokuWiki's wiki.
761948
A new submission from Ophir Prusak came in this morning about a new article he has posted on his site - Understanding PHP - How did we get here?
277894
Chris Hartjes has posted a tutorial about the creation of a simple user registration system in an application developed in the CakePHP framework. In response to the popularity of his other article on using CakePHP's Auth component, he's created a bit of code to answer some questions.   People have been having some questions about how the password is hashed and questions about a user registration system. Of course, the snarky response is "go and read the source for Security::Hash() and create some of your own code", but it is easier to just give people some code so they stop asking.   His example code extends the User object for the model, makes a controller with a register() method call and creates the username/password form for the user the enter in their information.
323084
Wez Furlong, a proponent of the OpenID authentication system, has posted a new tutorial of sorts that details a script for communication between your application and the OpenID servers.   I have a patch (php-openid.diff, for PHP 5, might also apply to PHP 4) for the openssl extension that makes it easier to build OpenID and TypeKey authentication support into your PHP apps. I don't have a canned solution for you to deploy, but I can give you some pointers on how to use these bits. I'm assuming that you know a bit about how OpenID works.    It's broken up into three sections - a look at associating with an OpenID server, performing the actual authentication (including the code for the page they're redirected back to), and an example of using the same functionality to interface with TypeKey.
201795
In a pointer from PHPKitchen.com today, there's a new tutorial discussing the use of PEAR's LiveUser library to help you authenticate and add/remove/update permissions for users of your site.
686172
Ryan Malesevich is taking a break from his look at some handy WordPress packages to share a small series on how to move from using MD5 hashes out to SHA-1 hashes for passwords in a MySQL database. He's posted part one today.   What if you're using MD5 in your web application and want to switch over to another encryption method. It's actually not that hard and I plan to cover them in this multi-part tutorial (I know I planned on writing this months ago, but it's better late then never). In this first part I plan on going over updating the database structure and a 'pseudo-code' of what will need to be done.   As mentioned, he gives the outline (pseudo-code) of how the process will work - basically, creating an SHA1 hash of the MD5 and the username in a "newpassword" column added to your database.
466365
Cameron Olthuis wants to share the tools that he finds th emost useful with the entire web, so he's posted them here on his blog.   His list includes libraries from all different technologies, not just PHP. Several are Javascript-related, but it's always good to have a complete toolkit on hand when trying to tackle some of the more difficult things.   Included in his list are things like:  Moo.fx - a Javascript effects library Swat - an open source web application toolkit PEAR - the PHP package repository Mochikit - lightweight Javascript library    Be sure to check out the post and its comments for more great resources!
7274
MediaWiki is the collaborative editing software that runs Wikipedia, the free encyclopedia, and other projects. It's designed to handle a large number of users and pages without imposing too rigid a structure or workflow. MediaWiki 1.3.5 is a security update, which contains a small fix for a potential cross-site scripting vulnerability. All MediaWiki 1.3.x users are strongly encouraged to upgrade to this latest release.    The only substantial change from 1.3.4 is in includes/RawPage.php, so you can copy that one file in to perform a 'hotfix'. (Copy also includes/DefaultSettings.php to update the version number.)  Note that 1.3.4 included a number of bug fixes and stronger checks on file uploads to combat scripting vulnerabilities in Internet Explorer; users of earlier versions are very strongly encouraged to upgrade.  Release notes: http://sourceforge.net/project/shownotes.php?release_id=271848  Download: http://prdownloads.sf.net/wikipedia/mediawiki-1.3.5.tar.gz?download  Wiki admin help mailing list: http://mail.wikipedia.org/mailman/listinfo/mediawiki-l  Bug report system: http://bugzilla.wikipedia.org/  Play "stump the developers" live on IRC: #mediawiki on irc.freenode.net
535273
PHP driven Inventory, HelpDesk, Support, Issue Tracking, and Knowledge Base web application. Focuses on simplicity and ease of customization. Sort of a mini-Directory solution for SMBs using PHP and any Pear::DB supported database. OpenIT 1.3 represents a major step from 1.2.  Thanks to Aaron's (acolflesh) new "Lookups" section all entries in the database can be edited via OpenIT.  This means no more using phpMyAdmin to add Departments.   Dan (dancoulter) worked hard to get Active Directory authentication to work via LDAP.  This is an exciting feature for anyone using Active Directory.  The coding style is in a state of flux as we're trying to bring it in line with PEAR standards.  There have been minor database changes.  At this point the easiest way to upgrade your database is to do a diff of the old & new tools/setup.php scripts to see what has changed.  Please use this release as much as possible and report bugs on the SourceForge Project Bug tracker & forums.  Note:  From version 1.3 forward OpenIT will follow versioning practices similar to the Linux Kernel.  This means all odd minor number releases (1.3, 2.5, etc.) will be "Testing" releases, while even minor number releases (1.4, 2.0, etc.) will be "Stable" releases.  OpenIT 1.3 Released http://openit.sf.net  This version is availabe here: https://sourceforge.net/project/showfiles.php?group_id=111107&package_id=133178
343971
With the recent acquisition Sun has made (you heard about that, right?), there's tons of resources in the open source community that are talking about it, lots of them are more PHP-specific. Cal Evans has put together a list of some of the PHP bloggers/community memembers that have posted some of their thoughts on the purchase.   With all of the buzz floating around yesterday on this topic, I decided to let some of the dust settle before posting. From everything I've seen, the PHP community is largely positive about the news. [...] As I said, the community at large seems to be pleased with this news. Here are the links I've collected so far.   Names in the list include Andi Gutmans, Lukas Smith and Jaremy Zawodny. There's also a list of some comments from the "pundits" as to what this purchase could mean for the web as a whole.
130878
Blog: Web directory is light on content and features.
96958
Paul Jones is rejoicing a bit about the OpenID and Typekey functionality Wez Furlong shared just the other day on his blog.   Wez Furlong gives us good news about implementing the math functions needed to support TypeKey and OpenID more directly within PHP.   Paul also mentions that the Solar framework has also had the Typekey support integrated for a while now (as an adapter) that uses the "big-number math functions" currently available to PHP developers. Wez's solution, however, would just about make those obsolete.
731797
This is really cool!  I finally get my own comment spam!  For some reason I felt left out of the party.  I just wasn't cool enough for the spammers to consider me worthy of their spam.  Anyway.  I implemented my own little turing test.  Now the comments say:  {{{  Turing Test: Are you a human? (required. Just type yes... this is for automated spam prevention)  }}}  While this wouldn't work for all blogs in the wild I'm sure it will work just fine here in my little corner of the blogosphere.  If spammers really want my blog enough then I'll deploy a captcha.  If they solve the captcha I'll deploy a sentient robot  which will traceroute packets back to the host and then terminate with prejudic ...
588152
Russ asks: Where's the OpenSocial container API? I love Russ because he cuts through all the BS and gets right to the core, most basic question, and he doesn't care who he pisses off. That's my kind of developer. You can't lie to the compiler, when the bits hit the road, you gotta know what garbage goes in and what garbage comes out.  (Ahh programmer's humor!) In other words, suppose I wanted to compete with Google, MySpace, Plaxo and LinkedIn, well, where's the spec that shows me how to do that? Well, of course I don't know, they aren't communicating with riffraff like me, but I have some experience with this kind of stuff, so I can hazard a guess. If they publish a spec,all kinds of projects will likely get started to enable the API in (just for the sake of argument): Drupal, WordPress, Twitter, Pownce, Jaiku, Scripting News (why not add widgets to a random blog), CNN, The New York Times, well you get the idea. There might be lots of implementations very quickly. And that would be it for changes. It would be frozen de facto, they'd have to live with what they have, which given how quickly it was thrown together, probably isn't very good. Not the kind of stuff you'd like to support for the next decade or two. Or maybe they would break everyone, something guaranteed to make them a lot of enemies, much the way Microsoft did, and they were good at migration of APIs.  Google is good at doing AJAXy web UIs, they make users happy, but they're not very good at APIs. This one is a loser, for sure. That's the answer to Russ's question. It's probably not malice that keeps them from releasing details to everyone outside their club, it's pragmatism. They have to try to hold on to it to keep it from becoming even more of a mess than it already is. Just my opinion, for what it's worth. I've been wrong many times before.
154420
When Tim Howes and a group of colleagues created the Lightweight Directory Access Protocol almost 15 years ago, he had no idea this quiet little front end to the more robust X.500 directory
335297
After an annoyingly long series of beta releases, say hello to MediaWiki 1.3.0! Everyone running the beta releases is _strongly_ recommended to upgrade to the current code. MediaWiki is the collaborative editing software that runs Wikipedia, the free encyclopedia, and other projects. It&apos;s designed to handle a large number of users and pages without imposing too rigid a structure or workflow.   This release includes a security fix: the 1.3.0 beta releases may be vulnerable to a PHP inclusion attack if include files are exposed and you have allow_url_fopen and register_globals on (this is the default configuration in PHP 4.1.x, but register_globals is off by default in 4.2.x and later).  Note that while MediaWiki through 1.1 required register_globals to be on, 1.2 and 1.3 *do not*. If you have register_globals on, you should turn it off unless you are absolutely sure you require it for some other package. See http://php.net/register_globals for general information.   Release notes: http://sf.net/project/shownotes.php?group_id=34373&release_id=259965  Download: http://prdownloads.sf.net/wikipedia/mediawiki-1.3.0.tar.gz?download  Wiki admin help mailing list: http://mail.wikipedia.org/mailman/listinfo/mediawiki-l  Bug report system: https://sourceforge.net/tracker/?group_id=34373&atid=411192  Play "stump the developers" live on IRC: #mediawiki on irc.freenode.net
533524
A great presentation by Ilia Alshanetsky from the International PHP Conference 2004. The only thing I would like to point out is that MMCache is still being actively developed, as evidenced by the CVS activity at sourceforge.  PS: You might need to use Mozilla to view this. IE sometimes doesn't work properly. I thought IE was a defacto standard :-)