Plesk Module Hotfix?

[TheHostingHeroes]

Dear WHMCS,

When will a new Plesk module be released that works with Plesk WHMCS 18.0.80?

Ref: https://support.plesk.com/hc/en-us/articles/42276009318423-Unable-to-connect-to-Plesk-18-0-80-from-WHMCS-This-element-is-not-expected 

 

[azzepis]

I can't see anything about this in latest maintanance release, it's like a joke :(

I have to manually suspend/unsuspend every service, nonsense

[websavers]

WHMCS staff provided this fix:

Edit: /modules/servers/plesk/templates/api/1.0.0.0/webspace_set_status.tpl

Replace the root node (and its closing value) so that instead of <domain> and </domain> they read <webspace> and </webspace>

Should solve the problem.

Edited 2 hours ago by websavers

[azzepis]

Just now, websavers said:

Edit: /modules/servers/plesk/templates/api/1.0.0.0/webspace_set_status.tpl

Replace the root node (and its closing value) so that instead of <domain> and </domain> they read <webspace> and </webspace>

Should solve the problem.

I will try, thank you for your help 

[azzepis]

@websavers It works, ahaha, perfect. You are my hero for today!

Two whole weeks. That’s how long it took to wait for the absolute geniuses at WHMCS to fix a critical bug that completely broke automatic Plesk product activation and suspension. You know, just the primary reason anyone actually pays for billing automation in the first place.

During those 14 days? Complete radio silence. Zero response from official support, zero updates from dev team. Then, the grand moment arrives: a shiny new update drops! You install it with high hopes, only to realize they fixed literally everything except the one game-breaking bug starving your automation. Brilliant priority management.

And the rocket science behind the fix that baffled their entire engineering department? A random user on the forums solved it by pointing out that all it took was replacing one single word in the XML