Search options

Well, there are some places where confirmation is good idea, but it make no sense to include it everywhere. I  believe application
should make user's life easier, so asking for confirmation where there is small risk for any damage is just waste of user's time. We have added confirmation dialog iin places where using delete action can complicate user's life, and when the action can be harmful additional constraints does not allow for this. But if you want to add confirmation dialog in any customized page, you can do it easily using submit_js_confirm() helper.

Have you found any place in standard FA where additional confirmation should be added?

Janusz

Hi bhoo,

Could you send me example selenium based tests as you use it for your modules?

Janusz

AFAIK ISO-8859-15 is just Latin1 extended by Euro sign. This does not solve the problem for other latin encodings, but for Western Europe languages is probably the best solution. Using Utf-8 has other drawbacks like enormous PDF reports size, so we have decided to use mixed approach in next FA 2.5 i.e. utf8 encoded database together with arbitrary encoding in user interface. upgrade scripts will recode old databases to utf8.

Janusz

You can eventually block the message by commenting out display_warning() call in sales/includes/ui/sales_order_ui.inc ca line 60.

Nothing changed so far I'm affraid. The payroll system highly depends on local requirements, so we have not decided to start this development in main FA core.

Janusz

If your account has Default24 POS tied, constraints related to this POS are used during invoice issue.
Otherwise e.g. the salesman not allowed to make cash payments could issue cash invoices and receive money.

Janusz