<html>

<head></head>

<body>
    <div class="item">
        <div class="item-header">



        </div>

        <div class="item-body">

            <p></p>
            <p>So the other day, I posted about how <a href="greasemonkey-and-jquery-revisited.html"><strong>adding</strong> jQuery to a <strong>greasemonkey</strong> <strong>scripts</strong></a>&nbsp;has become pretty easy. It wasn’t always like &nbsp;that. The same approach can also be used to add YUI, Prototype etc to any GreaseMonkey script. Now suppose you want to add such a library to existing GreaseMonkey code? Well it’s a bit of a nuisance but can be done.</p>
            <p>First go to ‘Manage user scripts’ via the Grease menu &nbsp;and then right click on the script of your choice to find it’s containing folder.</p>
            <p>Second step is to download the library (eg, jQuery, YUI etc) of your choice and place it in the same folder as your script.</p>
            <p>Now edit the script and add the appropriate @require header eg:&nbsp;// @require &nbsp; &nbsp; &nbsp; &nbsp;http://ajax.googleapis.com/ajax/libs/jquery.6.2/jquery.min.<strong>js</strong></p>
            <p>close your browser and go up to the parent folder of your script, there you will find a file named config.xml , open it with your favorite xml or text editor.</p>
            <p>Find the element that describes your script, add a require child node &nbsp;like this:&nbsp;&lt;Require filename=”jquerymin.js”/&gt; replacing jquery.min.<strong>js</strong> with the name of the file that you just downloaded.</p>
            <p>Now go have that cup of tea. Tea is better than coffee you know. Tea’s got caffeine too.</p>
            <p></p>

        </div>
    </div>


</body>

</html>

Adding a JS library to existing greasemonkey scripts

<html>

<head></head>

<body>
    <div class="item">
        <div class="item-header">



        </div>

        <div class="item-body">

            <p></p>
            <p>Thousands have geeks have been combining the power of Greasemonkey and Jquery thanks to a small to a small tip published by <a href="http://joanpiedra.com/jquery/greasemonkey/">Joan Piedra</a>&nbsp;which explains how to load jQuery by adding script tags to the web page using Greasemonkey code. This approach was needed because jQuery and Greasemonkey didn’t play nice with each other.</p>
            <p>&nbsp;</p>
            <p>Some geeks still start a new greasemonkey script by cutting and pasting this bit of code from one of their old scripts into the new one. guess what, you no longer need to do that because the @require directive which didn’t work with greasemonkey 0.8/ jQuery 1.4 works well with current versions. That’s right folks Joan’s tip, which was a life saver not very long ago has sadly become redundant. You can just strip out about 20 lines of code and replace it with one line of code.</p>
            <p>// @require &nbsp; &nbsp; &nbsp; &nbsp;http://ajax.googleapis.com/ajax/libs/jquery.6.2/jquery.min.js</p>
            <p></p>

        </div>
    </div>


</body>

</html>

Greasemonkey and Jquery Revisited

<html>

<head></head>

<body>
    <div class="item">
        <div class="item-header">



        </div>

        <div class="item-body">

            So it looks like the whole world is moving from the PHP mysqli api to PDO (mysqli? what the hell is mysqli? guess you are asking cause you picked up PHP only during the last two years). There are millions of lines of PHP code out there that still uses the mysqli api and caveat that used to trip up countless programmers coding with mysqli is now tripping up people using PDO
            <p style="padding-left: 30px;"></p>
            <p style="padding-left: 30px;"><span style="color: #993300;">&nbsp;PHP Fatal error: &nbsp;Uncaught exception ‘PDOException’ with message ‘SQLSTATE[HY000]: General error: 2014 Cannot execute queries while other unbuffered queries are active. &nbsp;Consider using PDOStatement::fetchAll(). &nbsp;Alternatively, if your code is only ever going to run against mysql, you may enable query buffering by setting the PDO::MYSQL_ATTR_USE_BUFFERED_QUERY attribute.</span></p>
            &nbsp;

            Errors like this pop up because mysql stored procedures return multiple result sets! Even if your stored procedure is not supposed to return anything at all a single resultset will be created. If you do not fetch it your next query will fail! For queries that you expect to return data the first resultset is the one that you want. You can fetch and discard the rest with a for loop that calls&nbsp;PDOStatement<a href="http://www.php.net/manual/en/pdostatement.fetchall.php">::</a>fetchAll() . The alternative is to call&nbsp;PDOStatement::closeCursor

            &nbsp;

            If I remember correctly you cant use stored procedures at all with the ‘original’ PHP mysql API, the one that is older than many of the kids coding with PHP. &nbsp;The simple reason that MySQL &nbsp;simply didn’t support stored procedures in the good old days when PHP 4 was still king. It didn’t support a few types of sub queries as well.

        </div>
    </div>


</body>

</html>

MySQL stored procedures with PDO or mysqli

<html>

<head></head>

<body>
    <div class="item">
        <div class="item-header">



        </div>

        <div class="item-body">

            <p></p>
            <p>This blog is pretty old now, it's origins date back to <a href="36.html">2004</a>&nbsp;In the early days it was hosted on blogger and then on this site itself through <a href="36.html">MovableType</a>&nbsp;and then finally it moved from <a href="1484.html">MT to Wordpress</a>. Though I had blogged about WP even as far back as 2006, the actual move wasn't made until <a href="920.html">2008</a></p>
            <p>In the early days the posts were identified by their numbers (/archives/%post_id%.html is the format as you can see from the links above). Then I wanted to switch links where the post was identified by title &nbsp;(<code><a href="https://www.raditha.com/blog/wp-admin/options-permalink.php?sub=post#edit">/archives/%postname%.html</a>)</code> &nbsp; . I tried a few plugins for that before settling in the <a href="1698.html">Advanced Permalinks</a> plugin. I initially had a few teething problems with it but managed to make it work the way I wanted it to; that is older posts should still have the post id while the new ones should have the title in the post like this:&nbsp;<a href="solving-the-permalink-migration-mystery..html">http://www.raditha.com/blog/archives/solving-the-permalink-migration-mystery..html</a></p>
            <p>Then all of a sudden it stopped working. The posts seemed to revert to the old numeric format, this happened around post number <a href="https://www.raditha.com/blog/archives/3003.html">3003</a>&nbsp;which was nearly an year ago, but I had lost a bit of interest in blogging at the time so it wasn't until today that I had figured it out. The reason? I had set the end ID too low in the Advanced Permalinks settings page!</p>
            <p>Now I need to figure out why the feed and the next, prev links on the listings don't work anymore.</p>
            <p></p>

        </div>
    </div>


</body>

</html>

Monthly Archives for 2011 08

Adding a JS library to existing greasemonkey scripts

Greasemonkey and Jquery Revisited

MySQL stored procedures with PDO or mysqli

A few wordpress issues here and there