Search options (Page 87 of 246)

When you buy for yourself (non stocked items like hosting) directly take it into expenses.
If these are stocked items then issue to your expenses account or have an own use customer with no tax.

Check in the company/#/pdf_files if the pdfs are generated and saved there. Then check the browser preferences for display of PDFs / popups for the domain.

(100 * 5) / 105 = 4.76%

@joe: any Standard Operating Procedure for this in FA?

A really "kludgy" workaround is to duplicate the company stanza in config_db.inc file and put in a different user / password with restricted credentials! Alternatively, hack the save() function for the cart and/or tweak the insert statements for adding in a where clause to see if the session current_user is either admin or matches the record owner.

Otherwise, post your bounty in the Job Offers board with a clear description of what you want.

FA allows all locations to sell all products. If you want to restrict items sold at each shop, setup a separate POS for each shop outside of FA and import transactions into FA or make a separate extension for the same. Warehouse locations may be a filter that might be useful.

Refer any report where you find a centered field and provide screenshot. We can then trace what works for alignment in Arabic.

If you center the amounts in the body of the invoice, they will not align correctly for the decimal places. But if you still want it, then amke line 61 of reporting/rep107.php:

    $aligns = array('left',    'left',    'right', 'center', 'right', 'right', 'right');

to be:

    $aligns = array('left',    'left',    'right', 'center', 'right', 'right', 'center');

The top summary table has it's elements already center aligned in the English version - see attachment. The values in it are populated in the $aux_info array in reporting/includes/doctext.inc file.

The file reporting/includes/header2.inc that the invoice report uses aligns the values in it's lines 167-175 ('C'):

        foreach($aux_info as $info_header => $info_content)
        {

            $this->row = $iline2 - $this->lineHeight - 1;
            $this->TextWrap($col, $this->row, $width, $info_header, 'C');
            $this->row = $iline3 - $this->lineHeight - 1;
            $this->TextWrap($col, $this->row, $width, $info_content, 'C');
            $col += $width;
        }

This is a very important extension for FA and should have been built into the core as export/import are the important integration hooks for other applications to exchange data.

@itronics: please update the pkg repo accordingly.

The user input control functions that provide the dropdown select box php code should not get confused and the search delimiters should not be ambiguous. URL encoding too will convert space to "+".

We can also add the back tick character to the forbidden list it as well - "`". A semicolon too may be added to the list.

Here is an elegant way to check a string for presence of any character in an array:

$arrayOfBadCharacters =array(' ', "'", '"', '+', '&', chr(9), chr(10), chr(13), '`', ';');
$chars = preg_quote(implode('', $arrayOfBadCharacters));
if(preg_match('/['.$chars.']/', $_POST['NewStockID']) {
    // bad character(s) found
}  

These bad characters may be stripped off and the code used instead of throwing an error.

The addition af a nice POS into FA would make it very usable for the retail segment. Nevertheless, there are many dedicated POS systems with great advancements in it's development that to replicate the effort here would dilute the offering as voluntary maintainers with core skills and interests are hard to find and would be spread thin for it to be sustainable. Hence the need to natively integrate with an FA connector to popular Open Source POS applications.

A rudimentary POS in FA is the Direct Invoice entry screen. With a proper native FA RestAPI in place, integration with any POS by building a connector would become relatively easy.

The sales document types were missing for processing them. They have now been added.
Possible errors that may still remain are the fixed asset parameter in FA 2.4 for adding an invoice though a synch with the core cart class has been done.
The core may not yet have to be modified to degrade gracefully if the results of these changes demonstrate.

The Direct Invoice entry would suit such Cash entries with the Credit Card info in the memo with a pdf attached as a document to it. Possibly modify it for another menu link by hardcoding a Direct Credit Card Invoice entry.

Better still, use a POS and import transactions into FA.