Route page missing on 4.0.0

[Maximebaker]

[chriskapp]

@Maximebaker with the 4.0 release we have moved from "Routes" to "Operations", instead of Routes you create now an Operation. An operation is basically assigned to an HTTP path and method and is invoked if the specific request arrives at Fusio. You can find also more information at our release post s. https://www.fusio-project.org/blog/post/fusio-4.0-released

[Maximebaker]

Where is the doc to edit my "routes" operations?

[Maximebaker]

Here you can see that the operation tab is also missing and that if I try to go to /public/apps/operation, that thing happen:

[chriskapp]

Since you also have no "Operation" entry in your navigation the problem is probably that your account is not assigned to the "operation" scopes, for this go to the user panel and add the "operation" scope to your user, then it should work. You can find more information about the migration at https://github.com/apioo/fusio/blob/master/UPGRADE.md

[Maximebaker]

Since you also have no "Operation" entry in your navigation the problem is probably that your account is not assigned to the "operation" scopes, for this go to the user panel and add the "operation" scope to your user, then it should work. You can find more information about the migration at https://github.com/apioo/fusio/blob/master/UPGRADE.md

As you can see, there is no operation scope in any of the category.

I should have said that I upgraded fusio from 2.0.0 to 4.0.0 from the marketplace update button.

[Maximebaker]

Am I the only one with that problem?

[chriskapp]

Ok, so updating from 2.0 to 4.0 through the backend only updates the backend Angular app, to update the actual PHP backend you also need to migrate the database to the new structure, at this step the scope should be also created, you can find more instructions at our UPGRADE.md. Otherwise you can of course also start with a fresh installation which should work.

[bangash-92]

@chriskapp php bin/fusio migrate

WARNING! You are about to execute a migration in database "api_fusio_upg" that could result in schema changes and data loss. Are you sure you wish to continue? (yes/no) [yes]:

yes

[notice] Migrating up to Fusio\Impl\Migrations\Version20230922194158 [error] Migration Fusio\Impl\Migrations\Version20230508210151 failed during Post-Checks. Error: "An exception occurred while executing a query: SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child r ow: a foreign key constraint fails (api_fusio_upg.fusio_scope_operation, CONSTRAINT scope_operation_scope_id FOREIGN KEY (scope_id) REFERENCES fusio_scope (id))"

In ExceptionConverter.php line 56:

An exception occurred while executing a query: SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails (api_fusio_upg.fusio_scope_operation, CONSTRAINT sco pe_operation_scope_id FOREIGN KEY (scope_id) REFERENCES fusio_scope (id))

In Exception.php line 28:

SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails (api_fusio_upg.fusio_scope_operation, CONSTRAINT scope_operation_scope_id FOREIGN KEY (scope_id)
REFERENCES fusio_scope (id))

In Statement.php line 130:

SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails (api_fusio_upg.fusio_scope_operation, CONSTRAINT scope_operation_scope_id FOREIGN KEY (scope_id)
REFERENCES fusio_scope (id))