• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved DNN on old version in application vault

hostking

Regular Pleskian
How to update DNN which is currently : DotNetNuke (7.0.6-1)

How does one update these. We tried click Checking for Updates but it sais no updates exist.

Looking at DNN website it shows version 9?

So very outdated.

Any ideas?
 
Hi hostking,

pls. note that the package versions inside the application catalog may differ to the official releases directly from the vendor.

In your case, the packager should be informed about the latest release, so that they are able to provide another ( actual ) version over the aps catalog.
Code:
    <author a:author-type="vendor">
      <name>www.dotnetnuke.com</name>
      <uri>http://www.dotnetnuke.com</uri>
    </author>
    <author a:author-type="packager">
      <name>www.sofcloudit.com</name>
 
Hi hostking,

pls. note that the package versions inside the application catalog may differ to the official releases directly from the vendor.

In your case, the packager should be informed about the latest release, so that they are able to provide another ( actual ) version over the aps catalog.
Code:
    <author a:author-type="vendor">
      <name>www.dotnetnuke.com</name>
      <uri>http://www.dotnetnuke.com</uri>
    </author>
    <author a:author-type="packager">
      <name>www.sofcloudit.com</name>

Can you clarify this answer a little bit? Are you saying there is an XML file we have to manually edit somewhere in order for the application Vault to see the newer version? I've only just started using the Application vault for our Plesk Onyx on Windows.
 
Back
Top