RRowley

Forum Replies Created

Viewing 15 posts - 211 through 225 (of 300 total)
  • Author
    Posts
  • in reply to: Customer management on 2019.2.27 #960
    RRowley
    Participant

    In your config/custom.config.php file make sure you have the following settings:

    debug.level                         = All
    debug.error_reporting               = E_ALL & !E_DEPRECATED
    
    zend.logger_level                   = DEBUG

    The debug settings are probably already set this way. But if not, will cause runtime errors to be reported in the tmp/log/php.log file.

    The zend.logger_level setting will have a lot of debug information to written to the tmp/log/si.log file.

    If your problem still exists, zip these files together and attach to a message added to this thread.

    in reply to: price needs to be normalized when creating itemized invoice #959
    RRowley
    Participant
    RRowley
    Participant

    You should load master_2019.2. Your PHP version is better served by this version and brings you up to the best, most currently supported version.

    in reply to: Unable to apply patch 318. Found foreign key table #947
    RRowley
    Participant

    The error is explicit. There are values in the cron_log table where the cron_id is set to 2 and to 3, but there are no entries in the cron table with an id of 2 or 3. Two options are provided. Change the cron_id in the those cron_log records to a value that does exist in the cron table or delete those records.

    The update command:
    UPDATE si_cron_log SET cron_id = 6 WHERE cron_id IN (2,3);
    will set the cron_id to 6 for these records. Or the delete command:
    DELETE FROM si_cron_log WHERE cron_id IN (2,3);
    will delete these orphaned records.

    I recommend the delete command. These records probably were associated with cron table entries that you deleted in the past and the history in the cron_log table was not cleaned up.

    To either update or delete the records copy the command, go to the phpMyAdmin console and do:

    1) Access the cron_log table
    2) Select the SQL tab
    3) Select the Clear button to clear the default content in the text box
    4) Paste your copied command into the Run SQL query text box
    5) Finally select the Go button to execute the command.

    At this point, the orphaned records should not be orphaned/exist any more.

    I recommend that you delete the content of the tmp/log/php.log file before accessing SI again in case there is another error, so it will be at the top of the file.

    • This reply was modified 3 years, 8 months ago by RRowley.
    RRowley
    Participant

    Great find. Just updated master_2019.2 version (v2019.2.28) on github to use the SiLocal::dbStd(...) fix on both Itemized and Total style invoice unit prices. Also found and fixed an issue of Total style invoice handling of more than one tax item per line item used. The 2nd and on tax items we being ignored.

    • This reply was modified 3 years, 8 months ago by RRowley.
    in reply to: Float Right ? #933
    RRowley
    Participant

    Change any occurrence of
    <td colspan="6"><br/></td>
    to
    <td colspan="6">&nbsp;</td>

    In the case of

    <td colspan="6">
        <br/>
        <br/>
    </td>

    to

    <td colspan="6">&nbsp;</td>
    <td colspan="6">&nbsp;</td>

    My test shows both the printer render and the PDF render honor this change whereas the PDF render ignores the <br/> value in a table item definition.

    in reply to: Unable to create public/data.json file #932
    RRowley
    Participant

    Is there an error in your tmp/log/php.log file? Also, check your database for the invoice_items with the greatest value (click on “id” sort once for low to high and then again for high to low). What does this show in the “invoice_id” field? The value in the “id” field contains the invoices table. There has been an issue in the past, where the “invoice_id” gets set to a zero value and so doesn’t show with the invoice., If this is the case, you can manually change the value in the database to fist the unattached invoice item. I would then suggest you perform a clean install of the current version of SI. By clean install, I mean the following:
    1) Rename your current SI directory.
    2) Download the master_2019.2 SI zip file from github.
    3) Unzip the content of the downloaded zip file. Make sure you brows to the root directory for your web applications and then name the folder that will be unzipped to, to the name of your original SI directory renamed in step 1.
    4) Copy the config/custom.config.php file from your renamed SI directory (step 1) to the config directory of the newly restored file path.

    At this point, you should be able to access your SI app. See if the problem you experienced has been fixed. Note that I assume that you reattached (so to speak) the invoice_items record(s) orphaned in the database to their associated invoices record(s). The verification that this issue has been resolved is that you will see invoice items defined for new and existing invoices properly associated with the invoice.

    Let me know how this turns out.

    in reply to: Customer management on 2019.2.27 #931
    RRowley
    Participant

    Have you looked at the tmp/log/php.log file for an error? I assume the list of invoices on the primary screen shows correctly. If not, make sure that a public directory exists in the SI directory structure.

    in reply to: Fatal Error when exporting as PDF or DOC or XLS #922
    RRowley
    Participant

    Fixed this in current update, 2019.2.27 uploaded to github today.

    in reply to: Fatal Error when exporting as PDF or DOC or XLS #917
    RRowley
    Participant

    Select download on Github Fearless329 Simpleinvoices Master 2019.2 as shown in attach picture.

    • This reply was modified 3 years, 9 months ago by RRowley.
    in reply to: Fatal Error when exporting as PDF or DOC or XLS #915
    RRowley
    Participant

    I’m unable to replicate this error. The lowest PHP level I can test at is 7.2x. If you can upgrade to 7.2x and use the master_2019.2 version, hopefully the error will go away. If not, I might be able to better test for your issue.

    in reply to: Float Right ? #913
    RRowley
    Participant

    Try this.

    RRowley
    Participant

    I took another look at this and believe that a solution was found. The update has been pushed to github for fearless359/master_2019 version 2019.1.2. If you try this, let me know how it works.

    in reply to: performance with large datasets #908
    RRowley
    Participant

    FYI, there is a new local.currency_code field in the custom.config.php file. It is added automatically but is likely not set right for you. Check for it under the [production] header and for clarity, move it to the other local settings for locale and precision.

    Once this is set up, let me know the following:
    1) local value settings in the custom.config.php file.
    2) What are the settings for currency sign, currency code and locale fields in the INV PREFS (SETTINGS) for Invoice type records.

    RRowley
    Participant

    I changed my settings to en_GB in custom.config.php and in the INV PREF (SETTINGS) for the Invoice to en_GB also. This still works find. When I look at the php error log you sent in a zip file earlier, I see that the comma is being carried through to the database insert. When I look at this same command on my system (it is my production linux based system but running php 7.3) the comma that is displayed on my screen disappears from the $_POST array value for this field. So I thought maybe something in your PHP settings. However the PHPINFO information you provided, I couldn’t see any setting that would do this. Note that my development system is windows running xampp currently PHP 7.4 and it works fine there also.

    Bottom line is I don’t know what is going on. My best suggestion at this point is to install the latest master_2019.2 version (updated on June 3) as a fresh install. That is, don’t load it over anything existing install. You should be able to rename your current directory, create a new directory named what your old one was and then unzip the downloaded version of master_2019.2 content into it. Then copy your config/custom.config.php file from the old install to the new install. If you have any special files such as extensions or in the custom directory then copy those over. Also, if you have your own invoice template, you need to copy that directory to the templates/invoices directory, and copy any special logo images in the templates/invoices/logos directory to the new directory.

    Sorry I don’t have a more definitive answer. The removal of the comma is being handled behind the scenes so just recommending a scatter-gun approach to see if it changes thing.

Viewing 15 posts - 211 through 225 (of 300 total)