Search options (Page 1 of 2)

Finally I can create a report without any quote marks
Btw, I was creating a pdf report for stock movements, because I don't see a pdf report available for it.

Albert

With my current settings:
- $sql_trail set to 0
- "tout = tout | 600000;" in utils.js
- no change in inserts.js
I restored my backup file of size 3.948MB (unzipped) or 355KB (gzipped) in about 3 minutes and 20 seconds.

This is of course beyond the 60s limit in inserts.js like you just explained. Everything was normal, no timeout, no triangle icon, the proper "Restore backup completed." message was shown.

I haven't traced the whole js code, but from this experience I think the timeout limit is in utils.js. I haven't checked what effect I will get if I edit the timeout value in inserts.js.

Albert

Hi Janusz,

Thanks for your reply. I tried to import via phpmyadmin, and the data was imported successfully. I traced the code, and found that the restore execution stopped when processing sql_trails table. Since the execution found an error, then the code tried to rollback any changes done (dropping and creating tables), but somehow the rollback process was failed. So, what's left was table from stock_category until wo_requirements (they were untouched by restore process).

My guess is that since the sql_trails table related to $sql_trail variable, $sql_trail set to 1 could be the cause of this problem. So I set $sql_trail to 0, and the problem is gone. So when we restore the backup, we have to set $sql_trail to 0.

Now I found another problem. The restore process is successfully done, but the warning icon still shows, and the icon shows even when the restore process isn't finished. I suspect the setting of tout variable in utils.js is related to this problem. Can you help to explain how the tout variable works?

Albert

How to do the same thing for purchase invoice?

Thanks Joe.

Albert

Can you explain how does the sys_types table work in general?
What is field type_id used for?

Albert

After some search, I found the answer. I will put it here, so it can be useful for anybody else here.

I got it from here: http://www.gnu.org/s/hello/manual/gette … Entry.html
Here is the important part:
===========================
‘ll_CC’, where ‘ll’ is an ISO 639 two-letter language code (lowercase) and ‘CC’ is an ISO 3166 two-letter country code (uppercase). The country code specification is not redundant: Some languages have dialects in different countries. For example, ‘de_AT’ is used for Austria, and ‘pt_BR’ for Brazil. The country code serves to distinguish the dialects.
===========================

Joe, if you don't have any idea yet about what might cause my problem, at least please tell me what to check. Which file should do what.
Btw, is FrontAccount language system using cache? How can we refresh the cache if needed?

Albert

Hi Joe,

Thanks for the quick response

Actually, I didn't copy po and mo files manually to the language folder. In the installation process, I didn't install Indonesian language. So when the installation process finished, I just had en_US and new_language_template folders inside lang folder.

I installed Indonesian translation later when I have merged the existing translation with empty.po. Using Install/Update Language menu, the frontaccount code created id_ID folder inside lang folder.

After the language installation process was finished, I have checked the po and mo files inside id_ID folder, and I confirmed that they were the latest translation version (the merged one).

So, back to my original problem: why do I still get the old translation strings on my application screens?

Do you have any idea Joe?

And about sharing the translation: of course!
I plan to share it after I finish the project.

Thanks,
Albert