5,476

(4 replies, posted in FA Modifications)

http://adf.ly and http://uploaded.to URIs are blocked by ISPs in India (at least by BSNL).

Make sure that there are no transactions as yet when such currency changes occur.
Perhaps easier by editing a backup and restoring it with proper auto_increment value for the auto_number primary key field.

If these changes are submitted to the project, then it might be included as an addon (aka textcart) or into the core so that with version changes in FA, all would be faithfully carried forward.

5,478

(45 replies, posted in Modules Add-on's)

Fixed commit URL in Wiki:
http://www.frontaccounting.com/fawiki/index.php?n=Devel.SimpleAPIModule

5,479

(45 replies, posted in Modules Add-on's)

Congrats Andres - keep up the good work. Just placed a link to this post and relevant commit in the Wiki till I have time to go thru' it.

As you appear to be using the Mac for your work, please remove the Mac specific files like .DS_Store, etc from the repo.

5,480

(29 replies, posted in Wish List)

Get someone to make a module extending FA for it if it isn't there as yet. Try using Dimensions and Tags to see if they fit the bill.

5,481

(5 replies, posted in Wish List)

Use vTigerCRM and integrate the customer's Account Code into it and then provide a restricted login role - a dirty hack though.

After the last commit in the Mercurial Dev repo on May 16th, 2013, development has now moved solely to Git

Primary Dev Repo:

Mercurial till 2013-05-16: https://frontaccounting.hg.sourceforge.net/hgweb/frontaccounting/frontaccounting/

Git Repo after 2013-06-16: http://devel.frontaccounting.com/git/

5,483

(28 replies, posted in Accounts Receivable)

Any reason why this has not made it to the HG repo?

The file is:
includes/ui/ui_view.inc and the line to be changed is line no. 793:

     if (!($document == ST_SUPPAYMENT || $document == ST_CUSTPAYMENT || $document == ST_CHEQUE))

to

     if (!($document == ST_SUPPAYMENT || $document == ST_CUSTPAYMENT || $document == ST_CHEQUE || $document == ST_SALESINVOICE))

5,484

(13 replies, posted in Setup)

The Date format fix will be to delete the js files in the company/#/ folder and have it regenerated on next usage.

5,485

(11 replies, posted in Banking and General Ledger)

Thanks Joe.

Updated the Wiki at:
https://frontaccounting.com/fawiki/index.php?n=Help.ItemSalesSummaryReport
and
https://frontaccounting.com/fawiki/index.php?n=Help.ReportsAndAnalysis

5,486

(11 replies, posted in Banking and General Ledger)

Thanks Joe. You've named the report &Sales Summary Report, Detailed

It might have been better to be "Item &Sales Summary Report" to distinguish it from the Customer one.

5,487

(45 replies, posted in Modules Add-on's)

Depends on the way your apache conf is setup - with or without mod_rewrite and rewrite rules. Your URL is okay if you have the default apache conf setup.

The OpenVZ template I have is setup to avoid the index.php from showing up in the URL.

5,488

(12 replies, posted in Modules Add-on's)

The renderer.php lines 112-114:

                foreach ($sel_application->modules as $module)
                {
                    echo "<p ".$first." class='menu_head'>".$module->name."</p>\n";

displays only those modules that are enabled and passed onto it. It appears that the Dashboard module remains inactive as far as ths is concerned even if it has been activated for the company under use.

Therefore during installation, it must be explicitly be made active in the web root's installed_extensions.php and accordingly passed on to the one under the company/#/installed_extensions.php as well.

The non standard approach to having the installed_extensions.php's array subscript "active" as being true/false or 0/1 in the webroot 's installed_extensions.php and in the company/#/installed_extensions.php may cause problems - better to standardise on either the boolean variant or the integer flag method.

The dashboard module's name in line 13 of hooks.php - is it's case sensitivity important:


    var $module_name = 'dashboard';

Lines 18-27 of the dashboard module's dashboard.php:

        //$this->add_module(_("Dashboard"));
        $this->widgets = array();
        $this->add_extensions();

        $this->apps = array("orders"=>_("Sales"),
                        "AP"=>_("Purchases"),
                        "stock"=>_("Items and Inventory"),
                        "manuf"=>_("Manufacturing"),
                        "GL"=>_("Banking and General Ledger"),
                        "Dashboard"=>_("Dashboard"));

also has case sensitive issue for module name and the commented out add_module line.

Also a list of translatable entries should be placed in an empty.po or some sample language file like en_US.po/mo

5,489

(1 replies, posted in Modules Add-on's)

Such segregation would be useful but may have to wait for FA 2.4 since db changes are not allowed in FA 2.3 anymore. You can turn off auto numbering and manually use the physical voucher number each time till such a feature comes up - or pay someone to develop an extension for you and donate it to the community.

5,490

(11 replies, posted in Banking and General Ledger)

@Joe: please consider including the (Item) Sales Summary Report extension as part of the core as it should really be there.

5,491

(12 replies, posted in Modules Add-on's)

where in the dashboard theme do we enable the dashboard menu tab or where do we enable it by default in the dashboard module install - the hooks.php is quite plain indeed and somewhere defaults are kicking in. The commented out add_module in it does not seem to work even if the comments are removed. Possibly it must be done prior to installation......or activation for a company atleast.....

Have a look at the non ajax links on some of the FA pages and see the html code and the original php code that built it and verify if the said variables are in scope in the place you want it (or global the variable or use a function instead) and create your links accordingly.

@Joe/Janusz: This might be a nice feature to include into FA - emailing and re-mailing invoice/quote, etc.

5,493

(12 replies, posted in Modules Add-on's)

To maintain consistency and backward compatibility, we can have all widgets restricted to the Dashboard Tab with the reminders showing up on the main Dashboard tab by default. This will also make for good help screenshots and menu guides as well.

Since during FA operation, the end user will be switching between tabs, no need to waste time in having widgets on non-Dashboard tabs.

5,494

(9 replies, posted in Wish List)

Getting your patches integrated into the core of FA along with config flags if necessary will ensure that you will have those changes faithfully carried over to future installs without having to maintain a separate repo and making incremental changes on diff-by-diff basis each time the master changes.

5,495

(12 replies, posted in Modules Add-on's)

The Dashboard menu tab appears only if the $hide_inaccessible_menu_items = 0; since it is disabled in the install (how to enable it in the install?) and even then it appears blank.

The patch needed is to enable all widgets to be available as menu items in the Dashboard menu tab and make it enabled and have the Dashboard functionality removed from other tabs. Possibly the widget display sql can have the WHERE clause tweaked to not care about the menu tab it is to be displayed in and make a decision to display it only if the Dashboard menu tab is selected.

5,496

(9 replies, posted in Wish List)

Try this at first as someone asked for it in the forums a few months ago:

- Order Delivery
* add clear quantity button, so the default quantity to dispatch to 0. (usefull when you need to dispatch only a bit from a big order).

or better still just make addons / extensions of each set of features or the whole bunch as Elax Apps in a separate menu tab.

@AlistairR: Thanks for the input. I was mistaken into assuming that it was for a cron job on demand like reminder and expected some accounting action from the system to be performed in FA. I now see that is a human manually entered to do task list - a sort of memo reminder.

5,498

(12 replies, posted in Modules Add-on's)

If the config.php has:

    $hide_inaccessible_menu_items = 1;

then the Dashboard will not be visible as a menu tab. View it by setting above to 0 (default in FA).

Use phpmyadmin and check the tables manually. Alternatively, in FA, take a mysql dump (backup) and edit it and upload and restore.

Very easy!
Place network printers in each location and turn on CUPS-BSD Printing and set it in each user's profile.
Keep one or more userids for each location if needed so that the profile of the printers and stationery can be stored.

Keep Dimensions as the Branches.

Just one company install is sufficient.

One user login can see all the branches.

Filter by Dimension (branches) for branch transactions.

Specific set of transactions across locations can be bunched together using Tags. Example will be one supplier supplying goods to more than one location to be bunched together for evaluating average cost of his supply alone and then making payment across all supplies.