Forte Payment Gateway
Swiss QR Codes
Bug fixes
Please note that whilst Purchase Orders have been exposed in this release, this is alpha quality.
Forte Payment Gateway
Swiss QR Codes
Bug fixes
Please note that whilst Purchase Orders have been exposed in this release, this is alpha quality.
Hi,
I do prefer the look and feel of the React Web App which, imo, feels more user friendly and less corporate software.
I do understand that it is actually in development.
Do you have any roadmap for this web app ?
Do you plan to implement localization, especially languages ? It does not work at this point.
I selfhost IN actually, and it returns 404 error quite a bit. Maybe normal at this stage of dev ???
Thanks for the good work
There isnāt a public roadmap, but we are working on 1:1 feature parity with the flutter app.
If you can let us know where you are seeing these 404ās we can take a look into it.
as for localization, @ben do you have guidance for this?
Thanks for the reply,
Iām getting 404 almost everytime I refresh a page.
Can you confirm there is a pound sign between the website and the path?
No pound sign between the website and the path.
And if Iām on /invoices (or whatever page) and I add a pound sign just before, ie. Example Domain, I will be redirected to dashboard, which will reload correctly.
Sorry, just to confirm, if you use the pound sign, does the app behave correctly?
Can I send you a private Loom. It will be easier for me to explain what is going on when I browse the react app and you to understand what is going on (or not) !!!
Thanks
@david : Hereās a quick video that demonstrates my issue
Thanks for your support
So it looks like your system is rewriting the # sign out of the url, this is preventing React from capturing the routing and it is falling back to the laravel server hence the 404ās
By any chance, would you know what could be causing that rewriting ?
This issue is not happening when using IN in the Flutter app.
Thanks
v5.4.9 is now released.
Purchase order functionality has now been expanded.
Ability to convert a Purchase Order to an Expense
Ability to āReceiveā a purchase order which increments the inventory
Bulgarian translations added
Quantities enabled in Subscriptions to allow the end client to select quantity during checkout.
@david By any chance, would you know what could be causing that rewriting ?
This issue is not happening when using IN in the Flutter app.
So it looks like your system is rewriting the # sign out of the url, this is preventing React from capturing the routing and it is falling back to the laravel server hence the 404ās
Thanks
@alexgauvin I havenāt seen this before, I am assuming you are using apache as the webserver, I wonder if there is something filtering your URLs, perhaps mod_security or something.
@david : Thanks for your support.
Iām selfhosting IN on Siteground. Here is the reply for my support request on Siteground.
There is no mod_security filtering that will cause that behavior. When a mod_secrutiy rule is triggered, a āBad Requestā error page will be displayed instead of a redirect occurring. As for the application, there are no server-level filtering that redirects any URLs based on such criteria.
There are no redirects set on the server by default, at all. The only redirects that would be set are those that you can set from your Site Tools ā Domain ā Redirects and through the siteās .htaccess file.
The only thing Iām able to find is the siteās default .htaccess file which contains rewrite rules required for your applicationās functionality in the siteās public_html folder (document root). As this is not a server-related issue, thereās not much we can do to assist.
Youāll need to have your developers look into it as it looks like the application itself is rewriting the URLs to the default structure.
With that reply, not sure where to look at for my issue.
Thanks
Hi all,
We have tagged a special v5.5-RC build which is a big upgrade in Laravel versions (we are moving from Laravel 8 to 9), we are also resetting the minimum PHP version to 8.1 to support this release.
We are holding back on tagging this as a production release as weād like to get some early testing, our full test suite passes and we havenāt found any issues in the interface at all, however we would really appreciate the community performing some tests and advising of any issues.
The release file can be found using this link:
https://github.com/turbo124/invoiceninja/releases/download/v5.5-RC4/invoiceninja.zip
Installation is identical to other release. Please let us know in the comments if you find any issues.

Hi all,
I have just tagged v5.5.0. Please read below, I have recreated notes about this release and impacts of upgrading. TLDR. If you are NOT ready for PHP 8.1 stay on v5.4.12. When you are ready to upgrade your PHP to 8.1, please dive into v5.5.0
Release notes for v5.5
v5.5 is the new long term backend implementation of Invoice Ninja. In this major release we have incremented the minimum PHP to 8.1 and use the Laravel 9 framework this to allows the platform to remain stable without another major platform upgrade until 2024.
How do I upgrade?
First, upgrade your version of PHP to 8.1 and ensure the same extensions are available:
bcmath extension
ctype extension
fileinfo extension
gd extension
json extension
mbstring extension
openssl extension
PDO extension
tokenizer extension
xml extension
curl extension
zip extension
gmp extension
mysql extension
fpm (for Nginx)
Update your nginx configuration to point to the new PHP 8.1 FPM socket
If you run multiple version of PHP for other applications on your server, youāll want to ensure the CLI version for invoice ninja is PHP 8.1, if the default PHP cli version is not PHP 8.1 youāll want to update your supervisord configuration to point to the php8.1 binary
After starting the PHP8.1 FPM service and restarting nginx, you are ready to copy over the new v5.5 release files. You can either use the in app upgrade option, or manually copy over release files from the github release section.
v5.5.9 has just been tagged and should be available shortly for auto upgrades
v5.5.20
Has just been tagged, Lots of small improvements particularly around client registration and importing payments via CSV
Add check if plan is expired
Add checks for ninja portal urls
Improve handling of purchaseOrder and purchase_order
Updates for vendor routes
Client Paid To Date updates
Fixes for tech template
Fixes for braintree
Update client presenter methods
Updated composer lock
Fixes for default mark down settings
Fixes for tests.
Fixes for auto billing when using credits
Working on credit paymentS
Fixes for store payment request
Ensure documents array is an array
Handle single contact object passed into array
Handle single contact object passed into array
Fixes for handling partial payments with credits
Fixes for stripe error message when authorizing credit card
Fixes for seeding languages
Refactor for client balance
Fixes for select box background color
Fixes for registration fields and ensure client contact email is uniqā¦
Remove redundant code from CompanySettings
CLean up code paths for client balance
Remove DispatchNow()
New release with some significant performance improvements in the client portal and invoice PDF generation.
Supported by Invoice Ninja and Event Schedule