There's a setting under site-alias that looked promising in the API, called SEO redirect, see here: http://download1.parallels.com/Plesk/PP11/11.5/Doc/fr-FR/online/plesk-api-rpc/index.htm?fileName=28785.htm - doesn't work though, it does not recognise anything but web, mail and tomcat as parameters... Error message: "Parser error: Request is invalid. Error in line 9: Element 'seo-redirect': This element is not expected. Expected is one of ( web, mail, tomcat )."
It is really annoying to have to change this for each client going through our system, I'd rather you removed this feature, or at least gave us an option to disable it higher up in the hierarchy. Service Plans would be an excellent place to do that!
Back to the point, either make this an option in the Service Plans, or make the API work as intended.
Marten
There's a setting under site-alias that looked promising in the API, called SEO redirect, see here: http://download1.parallels.com/Plesk/PP11/11.5/Doc/fr-FR/online/plesk-api-rpc/index.htm?fileName=28785.htm - doesn't work though, it does not recognise anything but web, mail and tomcat as parameters... Error message: "Parser error: Request is invalid. Error in line 9: Element 'seo-redirect': This element is not expected. Expected is one of ( web, mail, tomcat )."
It is really annoying to have to change this for each client going through our system, I'd rather you removed this feature, or at least gave us an option to disable it higher up in the hierarchy. Service Plans would be an excellent place to do that!
Back to the point, either make this an option in the Service Plans, or make the API work as intended.