• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Cannot Prepare Placeholders

D

david_3rdday

Guest
I have an issue when I publish a site. It gets to about 90% and then I get the following error. The template that I get this error on is a custom template that I created.

Internal SiteBuilder error.
File: /usr/local/sitebuilder/include/SB/Site/Compiler/Modules.php; Line: 827
Message: Cannot prepare placeholders.; Code: 0

I am not sure how to fix it. Any ideas? I am running sitebuilder 4.2 on Fedora Core 7.
 
It is hard to say exactly what can be the reason for this but we can try to figure this out. Please give me answers for the following questions:
1 Do you have any pages on this site which are hidden from navigation?
2. Could you provide structure of the site here, so I could check it on my test server?
3. When did this error appeared? Probably you remember some specific actions after which it took place?

This information should help me clarify this situation and probably generate a solution for you.
4. Did you see any errors in Logs administrator section?
 
Solved

well I finally got this issued fixed. Support gave me an updated sdk, and that seemed to fix it. It was an update to the 4.2 sdk. thank you for looking into this issue.
 
Back
Top