• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Plesk Win 7.5.6 Error

T

Traged1

Guest
When accessing a domain owner's "Setup" button, we get the following error:
ERROR: subst (handle=, tag=site_builder, autoload=): no such tag

Can anyone help?
 
you may conact SWSOFT support team and they will send you a fix
 
Yes the following fixed this issue thank you:

Add to < plesk> \admin\plib\templates\hosting\phosting_setup_const
.tpl

before tag "<!-- FRONTPAGE SUPPORT -->"

<!-- BEGIN DYNAMIC BLOCK: site_builder -->
<fieldset>
<legend>{SITEBUILDER_LEGEND}</legend><table width="100%" cellspacing="0" cellpadding="0" border="0"><tr><td>

<table class="formFields" cellspacing="0" width="100%">

<tr>
<td class="name">{SB_PUBLISH_TEXT}</td>
<td>{SB_PUBLISH_CHECKED}</td>
</tr>

</table>

</td></tr></table></fieldset>
<!-- END DYNAMIC BLOCK: site_builder -->
 
OK well now it appears after installing the lastest patch from SW-Soft this fix is no longer working :( does anyone have any idea's???
 
Here is sw-soft support responce to our reporting of this bug again for the second time:

Please, try ro repair your Plesk installation in Add or Remove programs wizard (Plesk 7.5.6 -> Change -> Repair)
Probably, this will help.

Our records indicate that your free support period has expired. We would like to offer you the following options if you wish to receive support from SWsoft:

<> Per incident support - $75<> Unlimited 24/7 e-mail support for one year - $299 <> Premium support - Unlimited e-mail support plus 25 phone instances for one year - $549

And of course the repair did not fix the problem.
 
I have re-applied the latest patch and it did not help.

However, it appears that this only affects domains which have been setup on the shared IP of the server, as when I login as a client which has an exclusive IP the error is not there?
 
Back
Top