Bugs often refers to insects and other non-aquatic arthropods, but may also refer to: read more at WikiPedia

  • There are numerous GIT workflow floating around like Centralized Workflow, Gitflow, Forking flow and Feature Branch Workflow

    Over the last 10 years, I have followed this really simple workflow, similar to the forking flow.
    • it allow Parallel Development, features branches can be merged to any release branches or ideally Master
    • Collaboration Feature branches also make it easier for two or more developers to collaborate on the same feature

    We consider Master the stable version of the product, this branch should be deployed automatically using continuous delivery

  • I will show you in an Apache Maven configuration file how to copy files to server each time the package phase is executed.

    Solution with Ant SCP task

    This snippet of code is a ready to use code that make use of Apache Ant task scp, Just put this snippet of code in your Maven module where the assembly is executed or anywhere else to push all tar.gz files to a server just run a maven mvn package, you can add as many ant task and push to many server the same file during the reactor build.

                <echo message="Push to server/home/"/>
                <scp trust="yes"
                    <fileset dir="${basedir}/target">
                        <include name="**/*.tar.gz"/>

    Solution with maven-deploy-plugin

    The maven-deploy-plugin allows you to configure the deploy phase to deploy to a server using scp. There is a page in the documentation that describes how it can be done.

    Deploy maven artifact using Maven Wagon SCP

    Another alternative would be to use Maven Wagon SCP like described in this post for example

  • A lot of people have tried numerous times to download files from my download section without
    success, the error message was always the same

    Unrecoverable error "PCLZIP_ERR_BAD_FORMAT (-10)"

    Also, Some tried to unpack the zip file locally using stuffit/Winrar/7Zip and get an error suggesting
    that the archive is damaged.

    Only Internet Explorer users were having issues, this is because of Internet explorer not able to handle
    compression of all file types. I solved the issue by changing my mod_deflate.conf which now look like the following:

    <Location />
    AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css application/x-javascript

    # Make sure proxies don't deliver the wrong content
    Header append Vary User-Agent env=!dont-vary

    I found that I had to use application/x-javascript instead of application/javascript to actually get javascript files on my
    server to be served compressed.

    mod deflate documentation: http://httpd.apache.org/docs/2.0/mod/mod_deflate.html

  • bsod.windows.xp.01 bsod.windows.xp.02

    The Blue Screen of Death (also known as a stop error, BSoD, bluescreen, or Blue Screen of Doom) is a colloquialism used for the error screen displayed by some operating systems, most notably Microsoft Windows, after encountering a critical system error which can cause the system to shut down to prevent damage. According to Microsoft, bluescreens on NT-based Windows systems are usually caused by poorly-written device drivers or malfunctioning hardware. [from WIKIPedia]

  • You can now post comments everywhere and react to my articles (feel free to do it ;-) ), but please respect following guidelines:

    • Please keep the topic of messages relevant to the subject of the article.
    • Please keep your comments and language G-rated; because it can be read by everyone!
    • Personal verbal attacks will be deleted.
    • Please don't use comments to plug your web site. Such material will be removed

    Moreover, You can also rate articles individually from 1 (poor content) to 5 (best content) 

  • Comments are no more working on my homepage

    This is not due to my plugin security images but more to openSEF, a very good SEF (Search Engine Friendly)/ SEO (Search Engine Optimisation) component for Joomla/Mambo:

    • SEO are techniques and changes that are made to the content and code of a web site in order to increase its rankings in the results pages of search engines and directories. These changes may involve rewriting body copy, altering Title or Meta tags, removal of Frames or Flash content, and the seeking of incoming links.

    which currently is not able to rewrite correctly URL of the component akocomment (and akobook as well). This is very frustrating for me and for You as well (As I have received many emails on this). I will have t write an extensions this week end to solve this issue.

    I've solved the issue with openSEF by promptly deactivating it when the user submit a for from akocomment or akobook. All You have to do is siimply edit the file /component/com_sef/sef.php

    (Line 26)
    $sefEnabled = (file_exists( $sefConfigFile ) && filesize( $sefConfigFile ) > 0);
    if ($sefEnabled && $_SERVER['REQUEST_METHOD'] == 'POST' && !empty( $_POST['option'] ))
      $sefEnabled = !($_POST['option'] == 'login' || $_POST['option'] == 'login' || $_POST['option'] == 'com_phpshop');

    $sefEnabled = (file_exists( $sefConfigFile ) && filesize( $sefConfigFile ) > 0);
    if ($sefEnabled && $_SERVER['REQUEST_METHOD'] == 'POST' && !empty( $_POST['option'] ))
      $sefEnabled = !($_POST['option'] == 'login' || $_POST['option'] == 'login' || $_POST['option'] == 'com_phpshop') || $_POST['option'] == 'com_akocomment' || $_POST['option'] == 'com_akobook');

    This is of course a hack and not a correct solution, akocomment URL won't be SEO friendly ! I Will have to inverst more time to write a custom extension for OpenSEF....

  • The Contact section of my site is working again.

    Concernig Joomla! support Please always look first  into

    The server seems to handle the visitor load a little bit better
    as the number of daily visitors (top at 9000) has increased
    of 33% in the last 2 weeks (5900 daily)...
  • joomla_cms

     10 minutes ago, I got a strange error message:

    DB function failed with error number 1016
    Can't open file: 'mos_session.MYI'. (errno: 145) SQL=SELECT session_id FROM mos_session WHERE session_id=MD5('e20eafcf277b7bc0dd125357b4a1b223')
    SQL =
    SELECT session_id FROM mos_session WHERE session_id=MD5('e20eafcf277b7bc0dd125357b4a1b223'

    I was not able to access the frontend or admin panel of my homepage. I tried to look in PHPMyAdmin the table mos_session but was getting the same error message. The only solution was to recreate the table with the following code:

    DROP TABLE IF EXISTS `mos_session`;
    CREATE TABLE `mos_session` (
    `username` varchar(50) default '',
    `time` varchar(14) default '',
    `session_id` varchar(200) NOT NULL default '0',
    `guest` tinyint(4) default '1',
    `userid` int(11) default '0',
    `usertype` varchar(50) default '',
    `gid` tinyint(3) unsigned NOT NULL default '0',
    PRIMARY KEY (`session_id`),
    KEY `whosonline` (`guest`,`usertype`)
    ) TYPE=MyISAM;

    Why my table has crashed is still unknow but I am looking further in logs files...
  • As Git Bisect is not clear a lot of people, here is a nice PDF to look at Enjoy Fighting regressions with git bisect, LinuxCon EU 2013.pdf

    it is about "Linux" combinational explosion... Bug software have the following properties (not desired):

    • has many different "configurations"
    • may fail under one configuration but not another

    N configurations, T tests and C new commits means that a release needs:

    C * N * T tests performed

    where N and T, at least, are growing with the size of the software.

    Git Bisect help find a first bad commit and use a binary search algorithm for efficiency if possible.

  • To solve any problems with securityimages and the admin sessions (bug in Joomla 1.0.13), it avoid you being kicked out of admin every other link.
    You'll have to upload these files with FTP/SCp and overwrite existing Joomla! 1.0.13 files!
    BUG: Patches for Joomla 1.0.13 that includes the admin session fixes? Thanks to users in my forum

    Download JoomlaPatches for Joomla 1.0.13 for securityimages 4.x only

  •   In order to solve  to following issues in Joomla 1.0.9

    Warning: Invalid argument supplied for foreach() in /var/www/vhosts/waltercedric.com/httpdocs/includes/frontend.php on line 85

    Edit the file includes/frontend.php , this is the correct code: 

    * Cache some modules information
    * @return array
    function &initModules() {
    global $database, $my, $Itemid;

    if (!isset( $GLOBALS['_MOS_MODULES'] )) {
    $query = "SELECT id, title, module, position, content, showtitle, params"
    . "\n FROM __modules AS m"
    . "\n INNER JOIN __modules_menu AS mm ON mm.moduleid = m.id"
    . "\n WHERE m.published = 1"
    . "\n AND m.access <= '". $my->gid ."'"
    . "\n AND m.client_id != 1"
    . "\n AND ( mm.menuid = '".$Itemid."' OR mm.menuid = 0 )"
    . "\n ORDER BY ordering";

    $database->setQuery( $query );
    $modules = $database->loadObjectList();
    foreach ($modules as $module) {
    $GLOBALS['_MOS_MODULES'][$module->position][] = $module;
    return $GLOBALS['_MOS_MODULES'];
    In yellow what has changed in that  method (extract)
    . "\n AND m.access <= '".$my->gid ."'"
    . "\n AND ( mm.menuid = '".$Itemid."'OR mm.menuid = 0 )"

    All credits goes to user Mathinka(JoomlaPortal.de)
  • All my latest blue screens of Windows 7 Ultimate 64 bits, 48 inches of blue wallpapers :-)

    The Blue Screen of Death (officially known as Stop error, also known as BSoD, bluescreen, or Blue Screen of Doom) is a colloquialism used for the error screen displayed by some operating systems, most notably Microsoft Windows, after encountering a critical system error that can cause the system to shut down to prevent irreversible damage to its integrity. It serves to present information for diagnostic purposes that was collected as the operating system issued a bug check. [WikiPedia]

    23 Juli 2010  MEMORY_MANAGEMENT blue screen of death

    00.windows7.x64.23.07.2010 01.windows7.x64.23.07.2010 02.windows7.x64.23.07.2010

    20 June 2010 KERNEL_DATA_IN_PAGE_ERROR blue screen of death


    16 June 2010 UNKNOW blue screen of death

    00.windows7.x64.16.06.2010 01.windows7.x64.16.06.2010 02.windows7.x64.16.06.2010 03.windows7.x64.16.06.2010


    8 June 2010 BAD_POOL_CALLER blue screen of death

    00.windows7.x64.8.06.2010 01.windows7.x64.8.06.2010 03.windows7.x64.8.06.2010

    Do i get more and more blue screens?

    YES, the first 5 months none, (installed Windows 7 in november 2009), now i get some…2 per months, maybe it’s time to reinstall the whole operating system :-)

    Would I still recommend Windows 7  64 bits?

    Yes still,  if you want to start Eclipse with 2GB of RAM, you have no other choice! except switching to Linux or Mac :-)