Admin tabs order not working properly

[tiagosampaio]

When you add 2 or more tabs to admin area, like order view page, by using the method addTabAfter and the second new tab is placed after the first new tab the sort order does not work as expected.

Preconditions

1. Magento 2.2.4
2. PHP 7.1.13
3. MySQL 5.6

Steps to reproduce

Example:

I created a module which make changes for the sales_order_view handle in admin area and in my file Vendor/Module/view/adminhtml/layout/sales_order_view.xml I add two new tabs using the method addTabAfter:

1. skyhub_order_data_source: is placed after the tab order_history.
2. skyhub_invoice_key: is placed after the skyhub_order_data_source.

When accessing the page in admin area the following sequence is rendered:

1. skyhub_order_data_source
2. skyhub_invoice_key
3. order_info
4. invoices and all the rest.

It only works if I set the skyhub_invoice_key tab to be placed after order_history.

Expected result

Actual result

[Aranjan21]

I installed magento2 using this code on virtual box but my url is not opening . I have given correct permission to file as well still its not loading

[tiagosampaio]

@Aranjan21 what Magento version are you using for this test?

[magento-engcom-team]

Hi @tiagosampaio. Thank you for your report.
The issue has been fixed in #16412 by @tiagosampaio in 2.3-develop branch
Related commit(s):

• e04b7ca8077fcbd269ad2e2f3515af12f7beaba9
• 447667fccfdcbba86dbbd0e5d58d33bc9d8fc1e7
• 0dd4268c9c2a4398d54cf9c71cd5272ffe2f9e73
• 9301ccbf4d2c018304bbaad846ca39a8d939373c
• c2b5c7a586672a2633b746758a7adb124a2e1947
• 024384adfb612151477e60af6b2ed2815cc08496
• d35b094fb9152de81a76af474ba62358be854da3
• 63cc8e630df033191fd9447e997f7f38b7504be1
• fe307c701c47c553825c278df3d6e2fa5530b1a4

The fix will be available with the upcoming 2.3.0 release.

[magento-engcom-team]

Hi @tiagosampaio. Thank you for your report.
The issue has been fixed in #16175 by @tiagosampaio in 2.2-develop branch
Related commit(s):

• e0b26a7bb49871a701cb85062227297575243451
• 23d616d1913fcc40b8cf7e21c3f9cbbe933f83f6
• 5f2cf41ae48e907431267fdffe240765514c05d8
• 3252237dc976a74903910904a8608764746e5d23
• d136ac1757ee7fba67726979f80fc25e1aec2b6d
• 633a751e1ea734a6371ec26d6969592f57706ce1
• f5efeeef428382567d0f375e19b580cfcd118e25

The fix will be available with the upcoming 2.2.6 release.