Updating and moving to a new server

Support
53

Response 1

It appears you’re experiencing issues with database updates not being fully applied after upgrading to InvoicePlane version 1.6.2. This is a known issue that was reported during the beta phase of version 1.6.2, where the database migration process could fail, leaving the application in an inconsistent state. The development team addressed this problem in the final release of 1.6.2 by correcting the migration scripts. ​GitHub

Recommended Steps to Resolve the Issue:

  1. Verify Your Current Version:
  • Ensure that you are running the final release of InvoicePlane 1.6.2. If you had previously installed a beta version, it’s advisable to upgrade to the final release to benefit from the fixes implemented.​
  1. Backup Your Data:
  1. Reapply the Update:
  • Download the final release of InvoicePlane 1.6.2 from the official source.
  • Replace the existing files in your InvoicePlane installation with the new ones, ensuring not to overwrite the following:
    • /application/config/database.php
    • Customized templates in /application/views/
    • Custom styles in assets/core/css/custom.css and assets/core/css/custom-pdf.css
    • Uploaded files in the uploads/ directory
  • Access http://yourdomain.com/setup in your browser and follow the on-screen instructions to complete the update process. ​wiki.invoiceplane.com+2InvoicePlane Community Forums+2wiki.invoiceplane.com+2wiki.invoiceplane.com
  1. Check for Successful Migration:
  • After completing the setup, verify that all database migrations have been applied correctly. You can check the ip_versions table in your database to see which migration scripts have been executed.​
  1. Enable Debugging (If Issues Persist):
  • If you continue to experience problems, enable debugging in InvoicePlane to identify any errors:
    • Open /index.php in a text editor.
    • Set the environment to development by changing:

php

CopyEdit

define('ENVIRONMENT', 'development');

* This will display detailed error messages that can help in troubleshooting.
  1. Consult the Community:
  • If you’re still facing issues after following the above steps, consider reaching out to the InvoicePlane community forums for assistance. Provide details about the errors you’re encountering and any steps you’ve already taken. ​

By following these steps, you should be able to resolve the database update issues in InvoicePlane 1.6.2. If you need further assistance, feel free to ask.

Response 2

If you’re on InvoicePlane version 1.6.2 and noticing that not all database updates have been applied, here are some steps and considerations to help you resolve the issue:

:white_check_mark: 1. Verify the Upgrade Process

Ensure that you followed the official upgrade procedure:

  1. Backup: Always start by backing up your database and files.
  2. Download: Obtain the latest version from the official InvoicePlane website.
  3. Replace Files: Copy all files to your InvoicePlane installation directory, but do not overwrite:
  • ipconfig.php
  • Customized templates in /application/views/
  • Custom styles: assets/core/css/custom.css and assets/core/css/custom-pdf.css
  • Uploaded files in the uploads/ folder
  1. Run Setup: Navigate to http://yourdomain.com/setup and follow the on-screen instructions. The application should automatically apply necessary updates .

:hammer_and_wrench: 2. Check for Applied Updates

InvoicePlane tracks applied database updates in the ip_versions table. To verify which updates have been applied:

  • Access your database using a tool like phpMyAdmin or via command line.
  • Execute the following query:

sql

CopyEdit

SELECT version_file FROM ip_versions ORDER BY version_date_applied;
  • Compare the listed version_file entries with the SQL files present in the application/modules/setup/sql/ directory. Any missing files indicate updates that haven’t been applied.

:bug: 3. Address Known Issues in v1.6.2

There have been reports of issues related to database migrations in version 1.6.2. Specifically, an error concerning database migration was discussed in GitHub Issue #1147. The issue pertained to problems with SQL migrations, and a fix was implemented in pull request #1159. Ensure that your installation includes this fix.

:arrows_counterclockwise: 4. Manually Apply Missing Updates

If certain updates haven’t been applied:

  1. Identify Missing SQL Files: Based on the comparison from step 2, note which SQL files are missing.
  2. Apply SQL Scripts: For each missing SQL file:
  • Open the file to review its contents.
  • Execute the SQL commands manually using your database management tool.
  • After applying, insert a corresponding record into the ip_versions table to indicate the update has been applied.Example:

sql

CopyEdit

INSERT INTO ip_versions (version_date_applied, version_file, version_sql_errors)
VALUES (UNIX_TIMESTAMP(), 'missing_file.sql', 0);

Replace 'missing_file.sql' with the actual filename.

Caution: Always back up your database before performing manual updates.

:test_tube: 5. Test in a Staging Environment

Before applying changes to your live environment:

  • Set up a staging environment that mirrors your production setup.
  • Apply the updates and thoroughly test the application to ensure stability.
  • Once confirmed, replicate the changes in your live environment.

If you need assistance identifying specific missing updates or applying them, feel free to provide more details, and I can guide you through the process.