[RRowley]

If the authentication option in the config file is set to false, the user is not relevant. Since there is no log in, there is no logout. When authentication is enabled, the user is pertinent. Typically, if a user already exists, the same password should work. The rules for what a new password must conform to does not apply to existing passwords. What I believe the issue would be, is that there has been a change in the algorithm used to hash the password has changed. The authentication logic however takes this into account. If the password fails authentication using the new algorithm, it attempts authentication using the old algorithm. If that succeeds, it updates the password on file using the new hash for all future login attempts. In practice, I found that I would have to login a second time to have the newly encrypted password work. If this process didn’t work for you, I’m at a loss as to why. I’m glad however that you were able to get it working.

[RRowley]

These are the first three lines of the function. The code would go in after them.

 $printIfEmpty = !empty($params['printIfEmpty']) && $params['printIfEmpty'] == true;
    $class1 = empty($params['class1']) ? '' : Util::htmlSafe($params['class1']);
    $class2 = empty($params['class2']) ? '' : Util::htmlSafe($params['class2']);

[RRowley]

I believe you need to start adding debug statements to the function. Try this. In the include/smarty_plugins/function.print_if_not_empty.php file add the following code after the setting of the $class2 variable:

if ($params['label'] == "Ph.") {
    $str = "smarty_function_print_if_not_empty(): Ph is ";
    $str .= empty($params['field']) ? "empty. " : "not empty. ";
    $str .= "printIfEmpty is ";
    $str .= $printIfEmpty ? "true." : "false.";
    var_dump($str);
}

When you print the template, you will get a message at the top of the print info screen that will tell you if it sees the phone field as empty and if it is setting the print if empty option for some reason. A not empty phone field or a true setting on the print if empty variable are the only ways that the logic will print something.

Hope this helps.

[RRowley]

It works in all my testing. Make sure you don’t have a local copy of the function in your invoice plugins directory. I removed them all from the standard version and have worked with this in testing the logic in the various templates and it works fine. I’m in the middle of making some significant changes to SI which includes enhancements to these functions to using multiple labels values and such. So it will be a little while before I get those delivered.

[RRowley]

I’ve gone through and removed all duplicate occurrences of the various smarty function so that the standard version in the library is used. There is no need to include a function in a invoice templates plugin directory unless you want to modify it for some reason.

I’ve updated internal comments in the not null and not empty functions to explain the difference. Basically and item can be not null but empty (blank, 0, etc. are empty values). It appears there is no use of the not empty function but I’ll keep it around for now anyway.

[RRowley]

The isset() test for a field is to see if there is valid content to print. You can use the empty() test on a field to determine if both the label and the field should be printed. For instance here is a test to determine if custom field 1 should be printed:

<!-- Show the Invoice Custom Fields if valid -->
 {if !empty($customFieldLabels.invoice_cf1) && isset($invoice.custom_field1)}
 <tr>
   <td nowrap class="">{$customFieldLabels.invoice_cf1|htmlSafe}:</td>
   <td class="si_right" colspan="3">{$invoice.custom_field1|htmlSafe}</td>
 </tr>
 {/if}

[RRowley]

It has been a while since I coded an extension. So this was a great refresher course. Download the attached zip file and extract it into the extensions directory. Then in SI, select the Settings tab and the Customize Settings menu option. Next select the Extensions button.

This will display a list of extensions among which the new customerList name will appear. In the Actions column select the green Register icon. This will bring up the About to register: customerList screen. All you do here is select the Save button.

Note the new Toggle status icon in the Actions column. Note also that the light bulb in the Status column is grey. Click on the Toggle status icon and the light bulb will be yellow. This means the extension is enabled.

Now when you go to the Customer page, the phone number will be displayed in what was the department column. Note that this logic will prefer the mobile phone for the customer over the phone number if both set. If only one is set, that number will be displayed.

You can use the search field to search for a particular phone number.

Let me know host this works out.

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

Attachments:

1. customerList.zip

[RRowley]

OK. Found the problem. The setting is correct but what shows on the manage screen is not correct. I just uploaded a fix for this. Update files and you should be good to go.

[RRowley]

Yes, that is what the extensions directory is for. It’s been awhile since I’ve created an extension. Basically your folder name is the name of the extension and you create files in directory paths within it that are used instead of the standard file. For class files in the Inc/Claz folder, there is a trick to only add the class code that is specific for your need so you don’t have to copy the entire class and thereby put general maintenance of all the class code on you. Otherwise, you might miss some needed changes that future updates provide.

Maybe if you can explain what you want to do, I can see what it takes to set it up.

[RRowley]

You would have to create an extension with logic to do this.

Currently users with a biller role are restricted to accessing things that are related to that biller. So the biller record and the invoices for that biller. Products are universal, not related to any biller, so they can only be modified by and administrator.

[RRowley]

Provide screen shots of your si_system_defaults and si_preferences tables.

[RRowley]

Glad that worked for you. Sounds like an upgrade issue that you were able to resolve. From this point forward, you can maintain this information via the Inv Prefs screen.

[RRowley]

Use the Search box.

[RRowley]

So you are saying the on the new invoice screen that no matter what you select in the Invoice Preference field, the invoice shows Quote in the preference column? Please get a screen shot of the si_invoices database table showing the setting in the preference_id field, and a screen shot of the content of the si_preferences table.

[RRowley]

The processing time is likely the time to transfer the data from the server. Data for all invoices is transferred in a minimized json file in the public/data.json file. The client (your browser) is set to display data after rendering the 15 rows on the first screen (this is the deferRender option in the Datatables module). Bottom line, the current logic is as efficient as per my understanding, as it can be.

If you have additional thoughts, please let me know.

[Author]

Posts