• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Sitebuilder pubblishing error

M

maxioana

Guest
We get an error when we want to publish a website with modules. This error come only when we want to publish a site with a module (blog, forum, e-shop ...). The publishing is working fine when no modules come published.

Error Log:

System 2008/08/12 21:58:09 admin 84.232.xxx.xxx Action status: 2; Target: /Admin/Site/Form; Messages: The website can not be pubblished at specified position.
System 2008/08/12 21:58:08 admin 84.232.xxx.xxx Fail to check target....

Dettagli #21062Data di creazione 2008/08/12 21:58:09
Livello Errore
Sorgente System
Sorgente System
Nome utente admin
Indirizzo IP 84.232.220.26
URL richiesta /Admin/Site/CheckTargetForEdit
URL referrer http://sitebuilder.xxxxxxxxxxxxxxx.com/Admin/Site/Form
User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.0.04506; InfoPath.2)
Messaggio Action status: 2; Target: /Admin/Site/Form; Messages: Il sito non può essere pubblicato nella posizione specificata.

Our system check is:

OK : supported version of PHP found (5.1.X or newer - 5.2.1)
OK : extension sitebuilder3 in state on found
OK : extension pdo in state on found
OK : extension pdo_mysql in state on found
OK : extension sqlite in state on found
OK : extension dom in state on found
OK : extension libxml in state on found
OK : extension xml in state on found
OK : extension xsl in state on found
OK : extension spl in state on found
OK : extension pcre in state on found
OK : extension session in state on found
OK : extension simplexml in state on found
OK : extension ftp in state on found
OK : extension openssl in state on found
OK : extension mbstring in state on found
OK : extension soap in state on found
OK : extension gd in state on found
OK : extension ctype in state on found
OK : extension zlib in state on found
OK : extension iconv in state on found
OK : extension curl in state on found
OK : extension posix in state on found
OK : extension mysql in state on found
OK : supported SQLite version 2.x found
OK : SQLite UTF-8 encoding found
OK : GD library PNG support found
OK : GD library GIF support found
OK : GD library JPG support found
OK : GD library WBMP support found
OK : supported GD library version 2.0.1 (or newer) found
OK : setting magic_quotes_gpc in state off found
OK : setting magic_quotes_runtime in state off found
OK : setting open_basedir in state off found
OK : setting safe_mode in state off found
OK : setting zend.ze1_compatibility_mode in state off found
OK : setting mbstring.internal_encoding in state UTF-8 found
OK : config file was successfully parsed
OK : connection to MySQL database was established
OK : database and code versions are the same


Sitebuilder and publishing location are on the same machine.

We apreciate your support.

Thank you
 
For checking site publication requirements use following articles http://kb.odin.com/en/1812..As I can see from the output you checked Sitebuilder requirements but not site ones. Could you please translate the following message: "Messages: Il sito non può essere pubblicato nella posizione specificata."? Or if it is possible switch interface language into English and try publication one more time. After that provide log details here. Also, try to check apache error log files. Probably you could find something useful there.
 
Thank you. I will check and keep you up to date about results.
 
Back
Top