Search options (Page 142 of 247)

In FA 2.3 only some tables are InnoDB by default. You can try to first use the option of one-file-per-table so that the tables are moved away from the heap.

What version of MySQL are you using?
It is also possible you may have hit the limit of max_input_vars.

The MySQL will go away only when it does not have sufficient resources to continue to run.

Which tables in FA are you referring to?
What indexes are present for them and whether you have some additional index for optimisation from here.

1. Manually take backup of FA db.
2. Before deleting fiscal year from table, note it's id.
3. Check the entity relationship diagrams for all references to the fiscal year id.
4. The fiscal_year table's id field is related to fiscal_year field in audit_trail table.
5. In all other tables, the date is compared to check whether it is within the fiscal_year's date range.
6. In the sys_prefs table, there is a record for name= 'f_year'.

You might want to copy over the records you want to retain to a new table and delete the current table and then rename the newly created table to the original table's name.

The function delete_this_fiscalyear($selected_id) in admin/db/fiscalyears_db.inc does the fiscal_year deletion.

@ gaurangs: Which form are you referring to? Why not just have 2 separate items as kits with different quantity each in a bundle?

FA 2.4 config.default.php lines 49-50:

    // Build for development purposes
    $build_version     = date("d.m.Y", filemtime("$path_to_root/CHANGELOG.txt"));

Check the value of $path_to_root at that point.

Modify the function that processes the login credentials. Get the second factor from an email or SMS and enter it into a session variable and then verify with the second factor server and populate a second session variable which then becomes a token of the outcome and remains persistent thereafter for the login session.

Turn on Audit Trail in config file. It will not be specific to your filter.

You might want to use the MySQL tuning Wizard and think about using the InnoDB File per table option (it is enabled by default in MySQL v5.6+).

A few index tweaks for the current stable version are available.

Post Release fixes for FA v2.3.25.
Read caveats on using extensions with the new improved entropy.

Have a look at the Reporting Wiki Page which illustrates how to add a Signature to the Invoice and how to add extra lines to the invoice.

Disable Strict Mode in MySQL 5.7 and beyond:

https://support.kayako.com/article/472-how-do-i-disable-mysql-strict-mode-on-the-server
https://mattstauffer.co/blog/how-to-disable-mysql-strict-mode-on-laravel-forge-ubuntu

In the my.cnf file, use the following:

[mysqld]
sql_mode=ONLY_FULL_GROUP_BY,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION

Then restart MySQL - in Debian / Ubuntu it is:

/etc/init.d/mysql restart

First decide where you will have your pdfs to be attached and what naming convention you would use so that the "id" of the invoice is part of the file name. When creating links, the invoice number will be available to the script which can be used to construct the desired link for the file. Check out the code where the invoice is attached and add a similar line for your file.

Please note that this kind of change should be attempted by PHP programmers and is not meant for the faint of heart. Sufficient debugging will be needed as well besides checks for file presence, content and permissions need to be taken care of.

Create a reporting folder in your company/# folder and place your modified repXXX.php files there. They will override the ones in the one in the webroot. This way your will not get overwritten on any update though you will have to manually update your mods for any enhancements changes in the core.

Make the different "Company Names" as part of the "Branch Address".