[case 45100] Reseller IP Delegation Unchecked on Re-Visit

As root when you set IP delegation for a reseller and you check off the IP's you wish to have them use. Upon re-visiting the same delegation page the IP's are unchecked. This means if you need to add a new IP you then need to re-check all their IP's. If you do not then the reseller will lose any IP's you do not have checked.

For example:

You assign the reseller the following IP's

1.2.3.4
1.2.3.5


Then a week later user needs an additional IP for SSL certificate on a new site they are creating. So you want to add an additional IP 1.2.3.6. You visit the page and noticed 1.2.3.4 and 1.2.3.5 are not checked. You need to then check the following again:

1.2.3.4
1.2.3.5
1.2.3.6

Click save. Then if you re-visit all of those will be unchecked again obviously.


This was introduced in a 11.28 build probably over a month ago and was reported via ticket then. There is no eta in sight on when this is going to be fixed. It would not surprise me if this is not fixed until 11.30 or 11.32 based on resolution of issues similar to these in the past.

So I'm making a thread in hopes others will make tickets and report this same issue to annoy cPanel. Then they might fix it in a reasonable amount of time.

 

Three months and counting on this with a case option and no resolution. Extremely frustrating that people are asking about delegation features and cPanel people on this forum are suggesting using this feature. The problem is this feature does not even persist across page loads so what good is it really? You need to re-check a user delegation every time you want to make changes. At this point may as well just modify the files directly and avoid the interface entirely.

Why this is not fixed I don't understand. A minor bug introduced in a 11.28 release after 11.28 was stable. 3 months after it's been reported it still exists. So probably slated for a 11.30 or 11.32 fix which is what 6 months away from reaching stable? So in total we're talking about a bug existing for almost a year before it's resolved. That is assuming that it's even addressed in 11.30 or 11.32

 

Opened a ticket that's how it got a case number. Then after a while updated it asking for an update on when this will be resolved. Unfortunately this issue remains ignored while other issues some of which brought up in the same ticket have been resolved. It was introduced around 11.28.45 so I'm guessing it actually happened in 11.28.42.

So I mean as I said in the ticket if necessary we'd open a ticket for every license we operate. It's a lot of licenses and I figured it be a stupid thing to do. But if that is how it's determined what bugs are fixed we'll do it and flood the ticket system.