Cloudron Forum

Got resolved.
https://github.com/invoiceninja/ui/issues/2151

Hey there,

when heading to the settings page, i get the offer to update to the latest (beta) update.

I need because of a migration thing, the latest STABLE release. Any possibility to only update to the latest stable? Do i miss something?

Thank you so much guys

any updates here? would love to have strapi here as well...

Hey folks,

since a few updates (sadly we don't know which), the ExpenseCategories are not fully loaded when adding a new Expense.
Only one is beeing shown:

If you start typing, one match will be shown, but you have to know which all exist. Sadly not an option.

After some research, we found the following:

The network requests specifically asks for only ONE ExpenseCategory (per Page), as shown here:

URL: /api/v1/expense_categories?status=active&per_page=1&sort=name%7Casc&filter=

We found a GitHub Issue claiming to have the same issue.

So, as you can see in the thread, they suggest the VITE_IS_TEST env is probably set to true, which can be verified by checking the Reports Page.

If only 4 Products are present in the Dropdown, then the VITE_IS_TEST var is set to true (or equally NOT set to false).

So, we went over to the Cloudron Dashboard, into the Terminal of the InvoiceNinja App and checked the .env files.

First, the "Main" .env file (/app/data/env) seems to be the right place. But adding the VITE_IS_TEST=false does not change anything.

In the GitHub Issue they say, we have to look for the .env file where also the VITE_API_URL var is present and should look like this example.

The thing is, i do not find the right place. As all the VITE configuration is specifically for the React App, i cannot figure out how to set env-vars for it.

I also tried to manually set a global var via the cloudron cli (cloudron env set VITE_IS_TEST=false --app <app-id> but with no success.

So, a few questions:

• Do you experience the same behaviour?
• Is the frontend already built / bundled?
• Where can we pass VITE_XX env vars to the UI / frontend?
• What other impacts does the VITE_IS_TEST=true have on other features?

Thank you so much for your help