PBA-S WHOIS privacy retrospectively
Adding WHOIS Privacy to Plesk / Odin PBA-S after the event has not been supported for quite some period of time. This is a pain.
The database structure is a rats nest.
Borrowing from ‘half the information’ you need to be useful that I found here, the following SQL managed to make the pain go away without putting everything in the toilet.
mysql> use aspc;
Database changed
mysql> UPDATE dm_regdomain SET id_protect = 1 WHERE id in (SELECT id FROM dm_basedomain WHERE domain in (‘siteone.com’,’sitetwo.co.uk’));
mysql> UPDATE subscr_domain SET id_protect_fee = 9.99 WHERE domain_name in (‘siteone.com’, ‘sitetwo.co.uk’);
mysql> UPDATE subscr_domain SET is_id_protect = 1 WHERE domain_name in (‘siteone.com’,’sitetwo.co.uk’);
Needless to say – this comes with no warranty for use, tables change, you may have a different structure – back your stuff up first. – however this worked for me
Previous Post
Next Post
Why you no copy and Paste -damn you and your tin foil hat sir!
For my SQL challenged colleague Alex – this would look a little like this for a single domain ;)
mysql> UPDATE dm_regdomain SET id_protect = 1 WHERE id in (SELECT id FROM dm_basedomain WHERE domain=’domainname.tld’);
mysql> UPDATE subscr_domain SET id_protect_fee = 9.99 WHERE domain_name=’domainname.tld’;
mysql> UPDATE subscr_domain SET is_id_protect = 1 WHERE domain_name=’domainname.tld’;