• 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.

publishing only "static" version

E

entexgmbh

Guest
hello
when i try to publish a site, the site is only published as static (html-sites instead of aspx-files). if i check the publishing-settings as administrator, then it shows "dynamic". .NET is checked in plesk setup. i have deleted site in sitebuilder an deleted hosting in plesk und made all new. but it's always the same problem. other sites can be published correct.
any ideas?
regards steve
 
I need some clarification to understand what can be the reason for this behaviour.
Do you get any errors during publication? What is the output if you check publishing location? Do you have any modules enabled on the site?
 
1. no, i get no error during publication
2. in the output (in httpdocs/sitebuilder/) there are only html files, no aspx.
3. we have no modules on this site.
hope, this helps
 
So, as I understand you are confused about "dynamic" note in publishing settings? Is it different if you check it under user itself, not administrator? If it is possible, could you provide here screen shot for this issue to avoid any confusions.
 
Back
Top