When it comes to labels, by default, this function only loads current module labels into SUGAR.language.

These labels are acessible through the following command:

SUGAR.language.get('<ModuleName>', 'LBL_<LabelName>');

In order to add support to other module labels to be included, you should override _displayJavascript() method in your modules view, and specify which other modules labels should be included.

// modules/<ModuleName>/views/view.edit.php

require_once 'include/MVC/View/views/view.edit.php';

class <ModuleName>ViewEdit extends ViewEdit
{
    protected function _displayJavascript()
    {
        parent::_displayJavascript();

        if (!$this->_getOption('show_javascript')) {
            return;
        }

        $modules = array(
            '<Module1Name>',
            '<Module2Name>',
        );

        foreach ($modules as $module) {
            if (!is_file($GLOBALS['sugar_config']['cache_dir'] . 'jsLanguage/' . $module . '/' . $GLOBALS['current_language'] . '.js')) {
                require_once 'include/language/jsLanguage.php';
                jsLanguage::createModuleStringsCache($module, $GLOBALS['current_language']);
            }
            echo '<script type="text/javascript" src="' . $GLOBALS['sugar_config']['cache_dir'] . 'jsLanguage/' . $module . '/' . $GLOBALS['current_language'] . '.js?s=' . $GLOBALS['js_version_key'] . '&c=' . $GLOBALS['sugar_config']['js_custom_version'] . '&j=' . $GLOBALS['sugar_config']['js_lang_version'] . '"></script>';
        }
    }
}

Like all other stuff made in SugarCRM, this process also depends on what type of module you’re hacking, in other words, the place where you’re going to write the logic depends if you’re hacking a custom module or a core one.

Before you perform view customizations on core modules you should check first if the view is already implemented, in this case, you should check if the following file exists:

modules/<ModuleName>/views/view.edit.php

If so, you should create a new file on:

custom/modules/<ModuleName>/views/view.edit.php

and add further customizations.

Beware that on latest SugarCRM versions, you’re able to create custom views without having to copy all the logic from the core ones, and by that I mean that now you’re able to “truly” extend the custom views from the latter.

In order to achieve this the view name should be prefixed with ‘Custom’:

// custom/modules/<ModuleName>/views/view.edit.php

require_once 'modules/<ModuleName>/views/view.edit.php

class Custom<ModuleName>ViewEdit extends <ModuleName>ViewEdit {
    /** 
     * ...
     */
}

If by instance you’re hacking a core module that doesn’t have the view defined, you should create it like the example above but with a few differences:

// custom/modules/<ModuleName>/views/view.edit.php

require_once 'include/MVC/View/views/view.edit.php';

class Custom<ModuleName>ViewEdit extends ViewEdit {
    /** 
     * ...
     */
}

One thing to keep in mind is that if you’re hacking a custom module, you are able to choose which directory suits you best. As opposite to the examples above, on the example below, the logic is written directly on the module main folder.

// modules/<ModuleName>/views/view.edit.php

require_once 'include/MVC/View/views/view.edit.php';

class <ModuleName>ViewEdit extends ViewEdit
{
    public function display()
    {
        $this->_processDuplicate();
        parent::display();
    }

    /**
     * How bean will act on edit view when it's being duplicated.
     */
    protected function _processDuplicate()
    {
        if ($this->ev->isDuplicate) {
            $this->bean-><FieldName> = '';
        }
    }
}

Thanks to Jeff Bickart of Nepo Systems and Matthew Poer of Profiling Solutions for pointing the “truly” Custom views feature out.

Usually people tend to use strotime() indiscriminately, without being aware of its limitations. Although it is an awesome function, it needs to be used with care, otherwise it may lead to unexpected behaviors.

Below there’s a list of notes, also available in the PHP documentation, that everyone should keep in mind before using this function:

If the number of the year is specified in a two digit format, the values between 00-69 are mapped to 2000-2069 and 70-99 to 1970-1999. See the notes below for possible differences on 32bit systems (possible dates might end on 2038-01-19 03:14:07).

The valid range of a timestamp is typically from Fri, 13 Dec 1901 20:45:54 UTC to Tue, 19 Jan 2038 03:14:07 UTC. (These are the dates that correspond to the minimum and maximum values for a 32-bit signed integer.) Additionally, not all platforms support negative timestamps, therefore your date range may be limited to no earlier than the Unix epoch. This means that e.g. dates prior to Jan 1, 1970 will not work on Windows, some Linux distributions, and a few other operating systems. PHP 5.1.0 and newer versions overcome this limitation though. For 64-bit versions of PHP, the valid range of a timestamp is effectively infinite, as 64 bits can represent approximately 293 billion years in either direction.

Dates in the m/d/y or d-m-y formats are disambiguated by looking at the separator between the various components: if the separator is a slash (/), then the American m/d/y is assumed; whereas if the separator is a dash (-) or a dot (.), then the European d-m-y format is assumed. To avoid potential ambiguity, it’s best to use ISO 8601 (YYYY-MM-DD) dates or DateTime::createFromFormat() when possible.

Using this function for mathematical operations is not advisable. It is better to use DateTime::add() and DateTime::sub() in PHP 5.3 and later, or DateTime::modify() in PHP 5.2.

Returns a timestamp on success, FALSE otherwise. Previous to PHP 5.1.0, this function would return -1 on failure.

After reading a couple of reviews of other people that wanted to perform the same upgrade as me, from 2GB into 4GB, I’ve finally decided to bet on Kingston, and I bought the KVR800D2S6K2/2G modules.

Now you may be wondering why I didn’t bought 8GB instead of 4GB since the netbook supports them, the reason is plain simple: in my humble opinion they are way too expensive!

Here is a list of Kingston memory upgrades for Asus Eee PC 1201N.

While performing the upgrade I decided to take a couple of photos to illustrate the process.

First I took a couple of screenshots of Gnome’s system monitor before the upgrade.

The two brand new Kingston ram modules that I bought. As you can see in the picture their specifications are: KVR800D2S6K2/2G 2GB PC2-6400 CL6 NON-ECC 200-Pin SODIMM.

The backside of the netbook and a closer look at the memory compartment.

Another photo of it’s backside, after removing the screws from memory compartment, we can see the default memory ram modules: two dimms of 1GB each.

In this photo we can see a comparison of both memory ram modules. At the top we have one of the modules that is installed by default in this netbook, an ASint DDRII 1GB-800, and the new one at the bottom.

Another photo of it’s backside after installing the new memory modules.

To finish the sequence, here is Gnome’s system monitor screenshots after the upgrade.

Because I’m currently using a 64bits version of Ubuntu I didn’t found any kind of problem related with the recognition of the new modules, but from what I’ve read, in 32bits versions there may be problems which require a couple of updates.

As you can see performing the upgrade is a really simple process that takes only a couple of minutes. If after this, you are still with afraid of screwing your netbook here is a video that shows you, once again, how simple it is to upgrade your netbook memory.

With this in mind you only need to download this file which was referenced in this thread on post #134 and execute the commands below. Make sure to remove the NDISWrapper driver before doing this if you have already installed and set it up.

After download, unpack driver:

$ tar xvf rtl8192se_linux_2.6.0010.1211.2009.tar.gz
$ cd rtl8192se_linux_2.6.0010.1211.2009
$ sudo make

Then you need to edit two files:

$ sed -i 's/install: modules/install:/g' ./ieee80211/Makefile
$ sed -i 's/install: modules/install:/g' ./HAL/rtl8192/Makefile

Finally install and load:

$ sudo make install
$ sudo echo "r8192se_pci" >> /etc/modules
$ sudo modprobe r8192se_pci

Your wireless should now be working.

Credits go out to CompMas2 of ubuntuforums.org for the quick answer and to david woo of lauchpad.net for making this driver available.

Today I had to use NTLM authentication method, unfortunately it isn’t supported by NuSOAP yet, but I’ve found that if you combine cURL with NuSOAP you can get through without a problem.

So here is the solution I came up with:

First of all I’ve upgraded NuSOAP to it’s latest version which is 0.7.3 (the one provided by SugarCRM didn’t supported cURL yet), then I wrote something similar to the code below.

<?php

$wsdl = 'http://project/file.php?wsdl';

$client = new nusoap_client($wsdl, true);
$client->setCredentials('', '', 'ntlm');
$client->setUseCurl(true);
$client->useHTTPPersistentConnection();
$client->setCurlOption(CURLOPT_USERPWD, 'auth_username:auth_password');

?>

Although it is still an alpha version it already allows you to perform the regular navigation activities that you are used to with an incredible speed.

It’s layout is also a bit different of what we are used to, in my opinion it is great, KISS principle all the way.  I also like the new functionalities like the task manager which allows you to take control over the used memory with each tab/window and the browser itself.

With all this in mind I expect a great browser to arise from Google in the next months. Below are the steps that I needed to perform to install Chromium on Xubuntu 8.10 (Intrepid).

First of all you need to edit the /etc/apt/sources.list file:

$ sudo gedit /etc/apt/sources.list

Add the following two lines at the bottom of the file:

deb http://ppa.launchpad.net/chromium-daily/ppa/ubuntu intrepid main
deb-src http://ppa.launchpad.net/chromium-daily/ppa/ubuntu intrepid main

Now save/close the file and add the GPG key using the following command:

--rev-keys --keyserver keyserver.ubuntu.com 0xfbef0d696de1c72ba5a835fe5a9bf3bb4e5e17b5

Next we will update the source list and install the browser:

$ sudo apt-get update
$ sudo apt-get install chromium-browser

If you want you can also enable flash support by copying (or linking) your previously installed flash library into browser plugins directory:

$ sudo cp /usr/lib/flashplugin-installer/libflashplayer.so /usr/lib/chromium-browser/plugins

And you are done, next time you run it you will only need to specify the plugins usage with following command:

$ chromium-browser --enable-plugins

But there are also another flaws that you should be aware about, for example, column truncation vulnerabilities.

This security flaw it’s related with the lack of input length validations and it seems that it is affecting a lot of known applications.

Stefan Esser wrote a great tutorial about this subject it’s a must read.

Unfortunately there aren’t much informations about this subject, and from what I’ve read there is a lot of people with the same doubts I had.

Because I haven’t found any documentation on this subject I’ve decided to write the my own tutorial, hope it helps you.

Assuming that you already know how to create a Joomla! component setup XML file, I’ll write here how you can translate your administrator menu items using language packages. That way I will not talk about website front-end since I’m only focusing on administration menus.

I will also assume that you have a directory structure similar to the one below:

com_mycomponent
com_mycomponent/mycomponent.xml
com_mycomponent/admin
com_mycomponent/admin/index.html
com_mycomponent/admin/language
com_mycomponent/admin/language/index.html
com_mycomponent/admin/language/en-GB.com_mycomponent.ini
com_mycomponent/admin/language/en-GB.com_mycomponent.menu.ini
com_mycomponent/admin/language/pt-PT.com_mycomponent.ini
com_mycomponent/admin/language/pt-PT.com_mycomponent.menu.ini

1. Open XML setup file.

$ geany com_mycomponent/mycompoment.xml

2. Open administration tag and start to write component administration menu, our component’s menu will be composed by a title (COM_MYCOMPONENT) and two child links (LINK-1 and LINK-2). Note that all & must be escaped to & for the file to be valid XML and be parsed by the installer.

<administration>
<menu>COM_MYCOMPONENT</menu>
<submenu>
<menu link=”option=com_mycomponent&amp;controller=c1“>LINK-1</menu>
<menu link=”option=com_mycomponent&amp;controller=c2“>LINK-2</menu>
</submenu>

Now that we’ve finished the component administration menu, we will load language package files that will translate your component administration menu itens.
For this example we will have two different translations, English and Portuguese.
Although we are writing four files, two pairs for each language, the *.menu.ini are the ones that matter for this tutorial, the other ones are used to translate other texts that you will use in your component.

<languages folder=”admin/language”>
<language tag=”en-GB”>en-GB.com_mycomponent.ini</language>
<language tag=”en-GB”>en-GB.com_mycomponent.menu.ini</language>
<language tag=”pt-PT”>pt-PT.com_mycomponent.ini</language>
<language tag=”pt-PT”>pt-PT.com_mycomponent.menu.ini</language>
</languages>
</administration>

End of component administration supported languages and close administration tag.

3. Edit the English package file and write the translations for the items you’ve just created.

$ geany com_mycomponent/admin/language/en-GB.com_mycomponent.menu.ini

COM_MYCOMPONENT=My Component
COM_MYCOMPONENT.LINK-1=Link number one
COM_MYCOMPONENT.LINK-2=Link number two

4. Repeat the step #3 for the Portuguese package file.

$ geany com_mycomponent/admin/language/pt-PT.com_mycomponent.menu.ini

COM_MYCOMPONENT=O meu Componente
COM_MYCOMPONENT.LINK-1=Ligação número 1
COM_MYCOMPONENT.LINK-2=Ligação número 2

Note : All ini files need to be saved as UTF-8.

With this four steps you are able to translate your component administrator menu items, although it is a simple process, unfortunately there isn’t much documentation on this subject, and the one that exists is a bit poor and doesn’t explain all the steps.

To complete what I’ve wrote in here you can also take a look at this tutorial that talks about this subject, and you may also take a look at this one that covers the steps needed to follow while developing a component.

Imagine you have a field named price and it’s type is VARCHAR (it doesn’t matter why it’s not INT or FLOAT) and you want to use ORDER BY clause so you can list table rows ordered by price value.

It won’t work, since the prices will be listed alphabetically, you may read here how to fix this issue.

If you have a table labeled products, a field labeled price (typed as VARCHAR) and the following values: 1, 2, 3, 7, 8, 53, 47, 32, 99 and 327.

And you perform a query similar to the one below:

SELECT price FROM products ORDER BY price;

The result will be:

1, 2, 3, 32, 327,47, 53, 7, 8, 99

As you can see the product prices are ordered alphabetically to fix this you should add + 0 to the query (see example below):

SELECT price FROM products ORDER BY price + 0;

The result will be:

1, 2, 3, 7, 8, 32, 47, 53, 99, 327

Problem solved, now your rows will be sorted by price correctly.