I followed the instructions and migrated from V4 to V5 (but after the following issues, I’m sticking w/V4 for now…)
The instructions aren’t complete. You can’t login via Google and have to reset your password so you can login via email.
They tell you to login to your v4 site to start the migration, and while the link has the proper options in the URL, they don’t list them on the page.
When the migration is over you’ll have at least TWO companies. The empty one from setting up v5 and the migrated one. Delete the empty one.
On to my real issues…
The invoice screen (for a single invoice) is horrible. v4’s screen was intuitive and easy to read. Now everything is in white blocks that aren’t aligned on a white background. No color cues at all. The PDF no longer shows below, but you have to click a button to make it popup.
The list of invoices isn’t bad at all. A lot of changes, including the custom columns I’ve been waiting for, but again the color cues are missing. It’s just white on white mostly.
Recurring Invoices - same problems - but I do love being able to change the Next Send Date.
Do you mean the edit invoice screen? The v5 layout is based on the v4 layout. In v5 we added a view preview but this didn’t exist in v4.
You can add color to the header by setting a color on Settings > User Details or change to the dark mode on Settings > Device Settings.
In v4 we used a client-side JavaScript based PDF solution which was fast to render but hard to customize, in v5 we’ve changed to a server-side HTML/CSS solution.
I tried the User Details but when I save I get this error: 412: Invalid Password and there’s only an option to set the accent color anyways. No header color. The dark theme has the same problem, but just with a dark theme.
In v4 the PDF was created in the browser so we could show it as it was being created, in v5 the PDF is created by the sever so we can only show it once it’s complete.
That’s a good suggestion, do you want to create an issue on the GitHub repo to track the request?
Note: the app is built with Dart/Flutter, this enables us to build mobile, web and desktop apps with one codebase. CSS wouldn’t work but we should be able to find a simple solution.