New updates is not displayed in the new UI 🙀

AngryWarrior · June 25, 2024, 1:35pm

Hi guys @david / @hillel

Pretty much as the subject says. I had to go to the old UI in the desktop app to see it…

In the new UI you cannot see the new update notification:

But the update notification is displayed in the old UI (Through the Windows store app):

Thanks in advance.

Kind regards

hillel · June 25, 2024, 1:36pm

Hi,

I believe this should be corrected with future releases once you update to the latest release.

AngryWarrior · June 25, 2024, 1:38pm

Thanks for the update. It quite critical thing because you cannot access the update function through the website.

Not sure how clever or safe it is to update Invoice Ninja through the Windows app?

AngryWarrior · June 25, 2024, 1:42pm

Hmm as I expected the Windows app is unsafe for updating Invoice Ninja:

It should be done directly as we always done it on the website itself.

hillel · June 25, 2024, 1:43pm

The apps call an API route to run the update, the app you use to run it shouldn’t make a difference.

What may have an impact is the size of the update, form the error it may help to increase the PHP memory limit.

AngryWarrior · June 25, 2024, 1:47pm

We have already 1024M configured for Invoice Ninja since a long time. I

t has worked fine until this new UI update. Do you really need even more?

AngryWarrior · June 25, 2024, 1:48pm

Forced update seems to stall when you run the update on the website:

It basically stuck on that step.

hillel · June 25, 2024, 1:49pm

I suggest trying 2048 or manually copying over the latest tar.

AngryWarrior · June 25, 2024, 1:51pm

Wow.
Invoice Ninja is really becoming hungry for memory. I remember when you had like 128M requirements…

AngryWarrior · June 25, 2024, 1:54pm

Increased to 2048M:

Running the update after increasing memory generates this:

hillel · June 25, 2024, 1:57pm

The memory requirement depends on the specific release, minor updates shouldn’t need as much memory.

I suggest checking storage/logs for any errors.

AngryWarrior · June 25, 2024, 1:58pm

Hmm…

The update seems to also have messed up our database and have generated duplicate tables?

How do we fix this?

hillel · June 25, 2024, 2:02pm

You can comment out the referral_meta column in the database migration and then re-run it.

AngryWarrior · June 25, 2024, 2:03pm

Where can I do that? In the prompt?

Also how do I do that command? Any example please?

hillel · June 25, 2024, 2:07pm

You want to comment out these three lines of code

github.com

invoiceninja/invoiceninja/blob/v5-develop/database/migrations/2024_06_19_015127_2024_06_19_referral_meta_data.php#L15


      
          use Illuminate\Support\Facades\Schema;
          
          return new class extends Migration
          {
              /**
               * Run the migrations.
               */
              public function up(): void
              {
                          
                  Schema::table('users', function (Blueprint $table) {
                      $table->mediumText('referral_meta')->nullable();
                  });
          
              }
          
              /**
               * Reverse the migrations.
               */
              public function down(): void
              {

AngryWarrior · June 25, 2024, 2:15pm

Thanks!
And the duplicate table it just generated - should we delete it?

hillel · June 25, 2024, 2:17pm

I’m not sure what you mean, this migration was adding column. It tried to create a duplicate but wasn’t able to.

AngryWarrior · June 25, 2024, 2:42pm

Oh. I must i have misunderstood the error message. Then I read it like the update somehow have come to generate an additional table (duplicate), in the database,

So doing your suggestion should solve the issue then?

Thanks a bunch for your answer.

hillel · June 25, 2024, 2:47pm

As long as you can run the migrate command without seeing any errors then the problem is resolved.

AngryWarrior · June 25, 2024, 3:45pm

Ok, thanks.
I’ll give it a try later.