Skip to main content

ZC-11576 - Bug in MultiPHP Manager

Comments

18 comments

  • cPRex Jurassic Moderator
    Hey there! Thanks for bringing this to my attention. I confirmed this behavior and filed case CPANEL-36246 with our developers so they can look into that issue. If you're signed in to our ticket system you can follow along with updates on that case here:
    0
  • kdean
    So I was just reading the support thread on this since it's still broken and it appears that cPanel decided to just not fix it. Seems filtering a list shouldn't be that difficult. When you have a lot of domains, search/filter is rather important. I do find that if one searches with the starting letters of the domain it's more reliable, rather than searching for a word within a domain name.
    1
  • cPRex Jurassic Moderator
    @kdean - I'll look into this a bit later today once all the developers are in and I'll let you know what I find!
    0
  • cPRex Jurassic Moderator
    I checked into this again just now and I'm no longer able to reproduce the problem with the old steps I used. Here is the method of testing I used:
    • Create a server with at least one cPanel account, and ensure that domain is using PHP-FPM
    • Go to WHM >> MultiPHP Manager and select the "User Domain Settings" tab
    • Ensure that PHP-FPM is enabled on the right side of the page.
    • In the "Search for domain or user" box, search for the username of the test user
    Previously, the PHP-FPM options didn't display, but I am seeing those now. Is there a different testing method I need to use to reproduce the issue? Could you also let me know what version of cPanel you're working with?
    0
  • kdean
    I'm running 98.0.9. I have over 300 domains and sub-domains on the server so it presents a lot of opportunities to see incorrect data. Currently the vast majority of the results should show PHP-FPM as enabled, however as I type letter by letter into the search as expected the result list will keep updating but throughout each update I see numerous domains that should show enabled, showing as disabled instead. The further odd thing is it isn't even consistent. I can clear and retype the same search letters in and the enabled/disabled indicators will follow a different pattern where domains now indicate the opposite of what they just did before. Even if the matched set of results doesn't change, typing additional matched letters can cause the indicators to toggle. There's just no reliability to the indicators in the searched results. Maybe the results are getting influenced by no longer shown non-matched domains if the bug stems from the quantity of initial possible domains. So, a clean server with a few domains may not have the problem if that plays into it. I suggest adding a few domains and some sub-domains to see if anything presents itself oddly. If I page through all 17 pages of the full list, they all look correct. Someone really needs to trace through each step of the code for this to see where the output is going awry.
    1
  • cPanelAnthony
    Hello! Upon review, I have been unable to replicate this issue in a test environment. Would you be able to open a support ticket using the link in my signature? Once done, please provide me with the ticket ID so I can keep track of updates and update this thread with the findings. Thank you.
    0
  • Benjamin D.

    The issue still exists under WHM 116.0.14.  How is this still not fixed in March 2024?

    0
  • cPRex Jurassic Moderator

    I can't say why the issue hasn't been fixed, but I can confirm work on this is happening in the new case number, ZC-11576, since it has been assigned to a team.

    0
  • Benjamin D.

    Thanks

    0
  • Benjamin D.

    Any update on this? It should not take more than 5 minutes to fix for a single programmer.

    0
  • cPRex Jurassic Moderator

    I don't have any updates yet.

    0
  • Benjamin D.

    It's still not fixed in WHM 120.0.9

    0
  • Benjamin D.

    Still not fixed in WHM 120.0.15.  Are there any updates on this issue? Why is it not fixed yet? What is taking so long?

    0
  • cPRex Jurassic Moderator

    Update: the case has been assigned to a dev team now!

    0
  • Benjamin D.

    What do you mean by now? It was assigned more than 5 months ago? ZC-11576

    0
  • cPRex Jurassic Moderator

    There's been some restructuring internally, and this was a low-priority case so it was never addressed.  It's with a new time now and will be getting handled.

    0
  • Benjamin D.

    0
  • cPRex Jurassic Moderator

    Update - our team has identified the underlying issue, so they'll hopefully be working on a public fix soon!

    0

Please sign in to leave a comment.