Problem in the New Admin Beta

[adbrum]

Problem Description

We have verified in the code that there is a variable NEW_ADMIN_URL that switches from the Legacy Admin to the Beta Admin. We inserted this variable into udata.cfg as:
NEW_ADMIN_URL = '/beta/admin/'

Only with this configuration can we access the Beta Admin. We would like to know:

• Is this approach correct?
• Does this variable already have a default value or does it need to be explicitly defined?

Identified Differences

We have observed that the version of the New Admin in production on the French portal differs from the version downloaded from GitHub:

GitHub versions:

• udata-front v6.1.5
• udata-back v10.1.3

1. Menus

   • French version: Presents differences in the menu structure.

* Downloaded version: Some menu options are different or do not appear.

* Also in the "Publish on..." menu we have the items:
    * A harvester - is giving a 404 error
    * A Post - is giving a 404 error and does not exist in yours

2. Different URLs

   • Example URL for datasets:
     • In our environment: /beta/admin/#/me/datasets
     • On the French portal: /beta/admin/me/datasets/
   • We observed the difference in using the # character, which occurs in all URLs of the side menu items.

3. "Publish on..."

   • The pages accessed from the "Publish on..." menu are not loaded within the Admin, being opened in a new tab outside the administrative environment.

Question

Do these behavioral differences (menus, URLs, and internal navigation) depend on any other configuration variable besides NEW_ADMIN_URL to display the Beta Admin identically to the French portal environment?

[nicolaskempf57]

Hi,

We have moved the new administration from udata-front to our new front-end cdata. The /beta/admin routes in the udata-front repository aren't used anymore on the French portal.

The NEW_ADMIN_URL is here to link to the administration on the new front-end. For our local environments, the variable points to the dev.local address with the port used by cdata, e.g. http://dev.local:3000/en/beta/admin/.

For our deployed environments, we are using nginx to direct requests to udata-front or cdata based on their paths. In this scenario, the NEW_ADMIN_URL is simply /beta/admin/

[adbrum]

Hello,

We have updated to the latest versions of uData (10.3.2) and udata-front (6.2.3). We are attempting to use the new administration panel, which we understand is now part of the cdata project. However, when trying to run cdata, we are encountering several errors, and the administration panel is not accessible.

We would like to clarify a few points:

Should we continue using udata-front alongside cdata, or does cdata fully replace udata-front?

Is there any official documentation on how to configure and integrate uData with cdata?

In the current version of cdata, is it still necessary to set the NEW_ADMIN_URL variable in the udata.cfg file? If so, what should be the new path, considering that the administration panel is no longer in beta?

Thank you in advance for your attention, and we look forward to your guidance on resolving these issues.

Best regards,