Forwarded to devs Cannot read properties of undefined (reading 'searchFilters')

[macadia]

Username:

TITLE

Cannot read properties of undefined (reading 'searchFilters')

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk 18.0.69, Almalinux 9.5

PROBLEM DESCRIPTION

After upgrading to version 18.0.69 where one of the new features is a revamped database view, I get the error Cannot read properties of undefined (reading ‘searchFilters’) when trying to list the databases of a domain.

STEPS TO REPRODUCE

1. Enter a subscription
2. Click on Databases
3. The error appears on its own

ACTUAL RESULT

EXPECTED RESULT

View the list of domain databases

ANY ADDITIONAL INFORMATION

I opened a topic in the Plesk Obsidian section but nobody has answered me and I need it to be solved as soon as possible.

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Answer the question

 

[Sebahat.hadzhi]

Thank you for the report, @macadia . The reported issue is not reproducible on a test environment. Therefore, I cannot qualify it is as a Plesk bug. It appears that's something specific to the environment, it might have resulted by failure/interruption during the upgrade. In other for the exact root cause to be identified, I would suggest opening a ticket with Plesk support for an investigation of the issue on your server. To sign-in to support and open a ticket go to:
https://support.plesk.com
If you got your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative to get support directly from Plesk:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk

 

[macadia]

Thank you for your response. I see you have deleted the other topic. I have opened a support ticket to my hosting company to contact you.

 

[alvarezcruz]

Definitely looks like a bug. We've had several cases and our devs are looking into it already. I couldn't reproduce it either so it must have some specific trigger.

 

[Sebahat.hadzhi]

It has been recognized as a bug, identified with ID PPPM-14921. The issue is only observed after a Plesk update, so I was unable to reproduce it because I tested it on a fresh installation with Plesk 18.0.69. Apologies for the initial misunderstanding. I will follow-up with more details as soon as possible.

 

[macadia]

Thanks, my hosting company is in touch with the Plesk Support and waiting for your answer.

And yes, it happens after an upgrade from a previous version, 18.0.68#2->18.069 in my case.