Search options (Page 1 of 2)

Well, basically you will need a webserver with PHP and MySQL support and database server (MySQL) installed for ARM CPU, oh and also openssl extension and internet connection.

If it's only used by two people, I guess it MIGHT BE fine. (sorry about the capitalizations, not sure about speed etc)

check this link for pre-requisit
and check this link for LAMP installation on RPi
or check this link for Lighttpd+PHP+MySQL server on RPi

IMO, interesting idea. You can also split the database server from the web server to improve performance.

How exactly is FA dealing with reference number? My guess is FA gets the next reference number when creating invoice form. hence we can't post invoice if somebody else already post the invoice using the same reference number.

I have two proposed solution (programmatically)

First:
when processing/saving document,
1. FA check the reference number if it is already used or not.
2. if not, then commit to database. if already used, FA tells user that the reference number is already used and ask if he/she will change the reference number manually or let FA chooses the next reference number based on the database.
3. if user choose to change manually, then return to step 1, else FA set the next reference number automatically.

Or second:
- add checkbox in invoice/order/delivery form whether user want to create ref number manually or automatically. if user chooses automatically, the reference number input is disabled.
- add reference number information beside invoice/order/delivery number when succeeded so user can take a note for it.

i have tried manually create empty file and rename it into empty.sql.zip and empty.sql.gz.
FA (my version is 2.3.19) reads it normally and showed in backup list.

is renaming your file with *.sql.gz or *.sql.zip after gzip or zipping it solve your problem?

Hi saifmalik,
is it possible that you forget to add the dot before and after TB_PREF variable?

'SELECT * FORM ".TB_PREF."sales_order_details'

from the error message, there is no table 0_bom in your database.
you can copy the query to create table 0_bom from en_US-new.sql script at about line 159.

table 0_bom is used in manufactured items.

dvarsani, i ran your sql query in my test database and it ran without problem. may be something wrong with your table structure?

Hi again, i have emailed update translation (id_ID) to contribution email.
Old translation is too old and not properly translated.

Some strings are translated into original because they will make confusion if I translate them into indonesian.
Also some strings in admin area are not translated, because they are too technical to translate.

Please contact me if there are errors in the translation (I'm not an accountant, so may be I made incorrect translations).

Hope this will be helpful.

I think for bank account should be in Debit, and Equity account on the Credit.
You can ask your accountant for more accurate answer.

hmm, if i may know, where is the translation? I have downloaded id_ID language from fa repo, but the file information I get is

"POT-Creation-Date: 2010-07-08 15:59+0200\n"
"PO-Revision-Date: 2010-03-03 15:41+0700\n"

which is very old compared to last post by kusuma on December 14, 2012.

Is it the same translation with kusuma's translation or not?
I have create my own version of translation for 2.3.19, though. But I think it's better to compare the translations to get more accurate translation.

Thank you.

ah, forgive me.. i just read your notification in swedish language translation post. i'll upload asap.

.... done.

i've updated dynamic theme so it can follow configuration to hide inaccessible item if set to 1.

on line 145 file renderer.php change :

echo "<li><a href='#'></a>$img_src {$lnk[0]}</li>\n";

to:

if (!$_SESSION["wa_current_user"]->hide_inaccessible_menu_items()) echo "<li><a href='#'></a>$img_src {$lnk[0]}</li>\n";

Hope this helps.
Not sure if other theme needs it too.