MihailoJoksimovic

dig@dev:cat (develop)$ git branch
* develop
  feature/EPROC-395
  feature/EPROC-416-rebased
  feature/EPROC-420
  feature/EPROC-423
  feature/EPROC-423-hotfixes
  feature/EPROC-456
  feature/EPROC-460
  feature/EPROC-462

MihailoJoksimovic

 toggleRow: function(rowIdx, record) {
        var me = this,
            view = me.view,
            rowNode = view.getNode(rowIdx),
            row = Ext.fly(rowNode, '_rowExpander'),
            nextBd = row.down(me.rowBodyTrSelector, true),
            isCollapsed = row.hasCls(me.rowCollapsedCls),
            addOrRemoveCls = isCollapsed ? 'removeCls' : 'addCls',
            rowHeight;

MihailoJoksimovic

Dear Client

At the end of last week, Hetzner technicians discovered a "backdoor" in one
of our internal monitoring systems (Nagios).

An investigation was launched immediately and showed that the administration
interface for dedicated root servers (Robot) had also been affected. Current
findings would suggest that fragments of our client database had been copied
externally.

MihailoJoksimovic

Ext.define('DIG.libs.DocumentEngine', {
    /*
     * The parent component that has all the grids inside it.
     */
    parentComponent: null,
    /*
     * The header panel where all the document headers will be grouped.
     */
    headerPanel: null,
    /*

MihailoJoksimovic

#!/bin/bash
#
# mydns        This starts and stops mydns.
#
# chkconfig: - 65 35
# description: A database-driven DNS server
#
# processname: /usr/sbin/mydns
# config: /etc/mydns.conf
# pidfile: /var/run/mydns.pid

MihailoJoksimovic

<materialToArticleConversion>
        <!-- Maps Material Entity properties to Article Entitiy properties -->
        <conversionMap>
            <property>
                <materialEntity>article_short_text</materialEntity>
                <articleEntity>description_short</articleEntity>
            </property>
            <property>
                <materialEntity>article_description</materialEntity>
                <articleEntity>description_long</articleEntity>

MihailoJoksimovic

<fujitsu>
    <hostName>cat</hostName>
    <systemName>portal2</systemName>
    <systemInitials>P2</systemInitials>
    <!-- 1  => newcat -->
    <dbdId>2</dbdId>
    <serverId>6</serverId>
    <isReportingEnabled>1</isReportingEnabled>	<!-- enable this only if you also specify a custom reporting DB (or use the default one if thats appropriate) -->
    <isReportCartProcessingEnabled>0</isReportCartProcessingEnabled>

MihailoJoksimovic

cha@catdevng:/data1/www/catdevng.office.dig/ssl-htdocs/catalog/cha/eprocure (hotfix/2.69.2.1)$ git pull
You asked me to pull without telling me which branch you
want to merge with, and 'branch.hotfix/2.69.2.1.merge' in
your configuration file does not tell me, either. Please
specify which branch you want to use on the command line and
try again (e.g. 'git pull <repository> <refspec>').
See git-pull(1) for details.

If you often merge with the same branch, you may want to
use something like the following in your configuration file:

MihailoJoksimovic

function copyConfig($clientName, $filename)
{
    $defaultConfig = CLIENT_ROOT . DIRECTORY_SEPARATOR . $clientName . RELATIVE_CONFIG_DIR;
    $configFilename = $defaultConfig . DIRECTORY_SEPARATOR . $filename . '-config.xml';

    $newFilename = $defaultConfig . DIRECTORY_SEPARATOR . 'client.xml';
    checkNewFilename($newFilename);
    copy($configFilename, $newFilename);
}

MihailoJoksimovic

getPotentialAnswerDoctypes: function(buyerId, sellerId, document) {
        var doctypesFormatted = new Array();

        if (!document.get('answered') || document.get('another_answer_allowed')) {
            var workflowId = this.getWorkflowForBuyerAndSeller(buyerId, sellerId);