These past two days I've ported 90% of my PHP library from use of old-school mysql to mysqli. I still have a bit to update.

Wrote a completely new mysqli framework with default connection [link] capability [removal of first mandatory mysqli parameter and allow for a global default one used as last parameter] and I will no longer use mysql_ inside my code.

My question to you is: What do you use: MySQL_ functions of mysqli classes/mysqli_ functions?
PLEASE ANSWER IN THE COMMENT FORM!

PS: I plan to release some scripts that will also need to interact with the database. I want to know if they will need to work with both or if you are 'new-school'... unlike me.

I'm working on a site to sell many of my scripts and I'm writing the affiliate system. And I started day dreaming. It was like Paypal added two new fields inside the HTML payment forms that were named:

partner_share=Number|Percentage & partner_business=paypal_email

And this way Paypal could automatically share profits for my sales and, in case of financial disputes, they could handle the chargebacks too withdrawing amounts from both accounts. I understand this would be a PITA for them but it would be sooooo cool and make life sooooo easy.

PS: If this is possible in Paypal right now do slap me with your knowledge.

PPS: Adaptive payments come close to my dream yet miss it by lack of chargeback handling and multi-target withdrawl on behalf of Paypal.

PPPS: Some more reading on the subject from Tim Nash. Has some pretty drawings :)

Got a comment that the Google Image Search script I published ages ago does not work anymore and I didn't even check it. But, as I wanted to improve it a bit, I rewrote it with a few tricks. It comes with a whole bunch of defines that allow you to set the parameterseasily. You don't need to know them anymore.
Read the rest of this entry »

Just had a client telling me his hosting service has updated PHP and somehow lost elWpAPI functionality on the way. I don't know what they have done but maybe disabled the XMLRPC extension.

This is a first, but , as I seek to please (sigh) :) I quickly made the code compatible with IXR. Get the library here directly. So, right now, you should be able to use this without the PHP XMLRPC Extension. I tested it and it works but you make sure to save the oldie but goldie version before you try on the new one. I might have missed stuff on the way ... it happens when I speed code.

Enjoy.

There are a few changes in the code. If the response is a fault (error) the returned result will always be null. Use $wp->wasError() or $wp->wasSuccess() to determine success status. This way it will be a lot easier to determine success state of an operation. Use if(!($response = $wp->doStuff())) return false;

You can also totally avoid PHP XMLRPC if IXR exists by changing this to TRUE: define('FORCE_IXR_XMLRPC', false);

If you got problems ... the comment form is below. And go get a fresh copy!

This is really insane. The song is ... like WTF (who would think of sheet like this) ... the melody / voices are awesome.

View this on YouTube:HD.

PS: I'm not posting anything serious until I update the blog. Bad news is it'll be few more days, good news is I'll post some funny stuff here and the new blog will be awesome and more of my scripts will be available here.

I postponed the whole thing a few days. Had to fix some things first. It'll happen by next weekend.

I'm upgrading the blog. And I have no idea how long it will take.

As WP 2.8 came out all my plugins have been rewritten, many others have been created and they are all waiting to serve and protect :) So on Sunday ... the blog will be down for maintenance. If you need anything use the obviously present support@* email address and I'll provide quickly as always.

Have a good weekend ... less busy than mine!

Well ... it's done! Get downloading. And backup first as I never keep old versions :)

There are a few things to pay attention to. rFC & rSQL have been ejected from xmlr_rpc and were transformed in standalone plugins. Truth is these two plugins can do almost anything to Wordpress remotely. That's why I needed to pay attention to them separately.

Some new files are required to work. The xmlrpc.php must be in same folder with wpapi.php. I removed the XMLRPC communication part and made a standalone class to be used with any XMLRPC needs.

elWpAPI works as before but the new class elWpAPImu extends it with new WordpressMU functions that need rFC to work.  You can extend on it easily with any WordpressMU functions you want ... or you can ask me.

I didn't really get to test it throughly as I just wanted it out. It works [as I tested each function building it] but there is always something out there :) Let me know and, as always, I'll fix quickly.

As for the documentation and examples ... it's 2AM here :) In the next week I will start a new blog just for elWpAPI with many examples and a lot more detailed explanations including details on these new functions. But I'm pretty sure most of you will be able to use them right away.

All wpMU functions start with wpmu_*.

Have a good night ... I'll crash now!

I had a great idea from btray77 about making the class compatible with WordpressMU. And so I did ... even if any1 else could have used rFC to achieve this themselves. But this new class elWpAPImu which extends the elWpAPI is a lot cooler. It still needs rFC enabled.

These are the new functions that I added from WordpressMU and you can do anything. Well ... anything I noticed interesting in Wordpress MU but if you need other functions wrapped up I'll gladly do it for you.

createBlog, createBlogURL, createBlogDomain, createEmptyBlog, createEmptyBlogURL, createEmptyBlogDomain, deleteBlog, dropBlog, createUser, deleteUser, addUserToBlog, addSubscriberToBlog, addContributorToBlog, addAuthorToBlog, addEditorToBlog, addAdministratorToBlog, removeUserFromBlog, isUserMemeberOfBlog, getBlogPermalink, getBlogID, getBlogIDFromURL, getBlogsOfUser, getBlogOption, addBlogOption, deleteBlogOption, updateBlogOption, setBlogPublic, enableRegistrations, usersCanRegister, getBlogAddressByID, getBlogAddressByName, getBlogAddressByDomain, isMainBlog, getBlogDetails, getUserCount, getBlogCount, getBlogList

Yet ... there's a catch.

This post is only the heads up as I'm currently documenting the code as I do with all new code [and slowly with old one]. So stay alert tomorrow as I'm releasing the updated version and I know you want it ... if you want to be a good farmer.

There's more improvements to elWpAPI. I added session caching. This way, if your code is not well optimized and you create a category 10 times, the script will just do it once, cache the response and feed it back afterwards. This will be a great improvement in speed.

PS: Sorry btray77 for not publishing it today. I write code a lot faster than I write text or specs ;) but it'll be well worth the wait.

In the past two months I've been like all over but next week I'm back in 'office' resuming business as usual. I've let this blog stay public [with registration requirement for access to certain areas of posts] as before and I'll leave it like that. I'll create a new private blog on a subdomain where people will need to get a membership to read/download stuff. Nothing will be visible to the outside world from that blog except, possibly, some post titles. Most of the stuff I was going to sell for 10-25$ will be freely available to those who become members but ... it won't fly cheap.

More on this next week ... right now I'm preparing the Wordpress membership/affiliate plugins ... and they work ;)