Forum Replies Created
-
AuthorPosts
-
RRowleyParticipant
If you have no problem with the description being displayed where it is now, I can look at implementing a SI Defaults option to have it showing on new invoices rather than hidden. This will be a master_2020 feature though.
RRowleyParticipantFor SI master_2019.2, you need to be on PHP 7.2 at a minimum. PHP 7.4 preferably and 7.4 required for SI master_2020. Any reason you can’t do this?
RRowleyParticipantBefore pursuing a change, have you used the new invoice form as it comes with SI? The default templates show what you ask for with the exception of the description being on the line below the “Quantity”, etc. You just have to select the “Show Details” button.
This form avoids overflow when you have multiple tax ids, or a long description.
If the issue is that you want to access the screen with detail boxes display by default, I think that is more easily accomplished than rewriting the screens. Although the text box for the description would still follow on the line after the item details.
First try and work with what you get by default. If this causes you headaches, let me know and I’ll see what can be done.
RRowleyParticipantZip your old files from the custom directory and attach them to a response to this message. I’ll look to see what you have.
- This reply was modified 3 years ago by RRowley.
RRowleyParticipantIf you are running SI 2011, you should try to update to master_2019.2. I should work with your level of PHP. The update is pretty straight forward.
- Backup your database
- Copy your SI in to another backup directory.
- Delete all the sub-directories in your SI directory.
- Unzip the master_2019.2 zip file content into your empty SI directory
- Copy the
config/custom.config.php
file from your copy of the old SI into theconfig
directory of your existing SI directory. If you don’t have acustom.config.php
, copy theconfig/config.php
after renaming it tocustom.config.php
- Run SI. I should show you that there are a number of updates that need to be applied. Do this.
-
You might be stopped at the update that adds foreign key support if you have orphaned records in your database. If so, look at the instructions in the error message and see if you can resolve it. If not, get back to me.
RRowleyParticipantWhen you load an update, you should load all the files. I start by making a backup copy of what I have, then delete all existing folders, extract the update from the zip file into your empty directory, then copy the
config/custom.config.ini
file from your backed up copy to theconfig
directory of the update. Then run SI. This way you make sure that you have no residual files that might be a problem.RRowleyParticipantGlad to hear it. It has been a tough upgrade road for you but success in the end will be worth it.
RRowleyParticipantNo sure what you mean by “set the bill and the quote in SI master 2020. So you can elaborate on that.
For reports, the currency code comes from the localCurrencyCode in the custom.config.ini file.
Working with templates is a learn by doing exercise. Refer to the Invoice Templates & Styles topic on the left.
There are two locations where the language is set. In the custom.config.ini, and in the Inv Prefs records. These control which language file is read. For instance, a setting of fr_FR uses language from the
lang/fr_FR/lang.php
file. My needs are simple. So I set all these values the same. Maybe you need to do this also.If I misunderstood the language issue, you might just need to translate the phrase in the lang file you want to use.
RRowleyParticipantLook in your tmp/log/php.log file to see if there is more of an explanation. If you need me to look at it, copy the log file to a zip file and attach that zip file to a response to this message.
Also note what OS you are on and what webserver software you are using.
RRowleyParticipantExport the structure of you database, zip it and attach to a response to this topic. I need to determine if their might be other inconsistencies with what the patch process is expecting.
RRowleyParticipantI’ve loaded updated library files in the latest version of master_2020. Use this and see if you still have an issue, let me know.
March 20, 2021 at 9:06 am in reply to: Config::updateCustomConfig() – Unable to open ‘./config/custom.config.php.new #1441RRowleyParticipantSI updates your custom.config.php file if it is missing tags that have been added to config.php. To do this, it renames your custom.config.php file to custom.config.php.old and then creates a new custom.config.php and loads the data in it. If the application does not have write access to the config directory, it cannot do this.
You need to make sure the application has write access to this directory. Also to the public and tmp directories.
RRowleyParticipantHERE IS A REVISION OF MY PREVIOUS POST. I ATTEMPTED TO EDIT IT BUT WAS TOO LATE. SO IGNORE IT AND READ THIS
I assume the error displayed in your browser is:
SqlPatchManager::runSqlPatch() - PdoDb - query(): Execute error. See error_log.
In the php.log, it is attempting to create the si_products_attributes table but this table already exists.
This update would only happen if the greatest value of the sql_patch_ref column in the si_sql_patchmanager table has a value less than 255 and if the si_products_attributes table already exists.
This inconsistency suggest your database is in an unknown state.
To remedy this, you should DROP all tables from the database and then Import the database running for SI 2011 at the time you upgraded to PHP 7.4.
After doing this, check out the content of the si_sql_patchmanager table and verify that the greatest sql_patch_ref value is less than 255 and that there is no si_products_attributes table. Or, that the greatest sql_patch_ref value is greater than or equal to 255 and the si_products_attributes table exists.
If one of these assertions is true, you can access the master_2019.2 code that you have loaded on your system and hopefully this will run correctly. Let me know if this is the case.
However, if neither of these assertions is true, do not run anything, report that here and we’ll work on it further.
- This reply was modified 3 years, 1 month ago by RRowley.
RRowleyParticipantI assume the error displayed in your browser is:
SqlPatchManager::runSqlPatch() - PdoDb - query(): Execute error. See error_log.
In the php.log, it is attempting to create the si_products_attributes table but this table already exists.
This update would only happen if the last row in the si_sql_patchmanager table has a sql_patch_ref value less than 255 but the si_products_attributes table already exists.
This inconsistency suggest your database is in an unknown state.
To remedy this, you should restore both database and SI version to what you had running correctly for SI 2011 at the time you upgraded to PHP 7.4. After doing this, check out the content of the si_sql_patchmanager table and verify that the greatest sql_patch_ref value is less than 255. Also verify that there is no si_products_attributes table.
If both these assertions are true, then access the master_2019.2 code that you have loaded on your system.
Hopefully this will run correctly. Let me know either way.
RRowleyParticipantThe error you are getting doesn’t appear to come from the master_2019.2 load. I believe that you loaded the master version which isn’t supported. Use this link to get the master_2019.2 version: Master 2019.2 Zip File.
You should restore your database and clear out all file from the previous download. Be sure to keep your config/config.php and config/custom.config.php files from before the previous load.
-
AuthorPosts
Recent Comments