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

Resolved Typo3 - Error! No pages are found on the rootlevel!

JogoVogo

Basic Pleskian
Hello together,

after migration, without any issues, (over plesk) some typo3 pages from plesk 12.5 CentOS6 -> 17.0.17 CentOS7.

But all have the same problem, a typo site with this output: Error!No pages are found on the rootlevel!

I checked the logs and hosting settings (php, cgi, etc), looks ok.

Any ideas?

regads,
ron
 
Hi JogoVogo,

pls. be aware, that this forum is a PLESK - related forum. If you desire help with a content and it's configuration/modification, pls. consider to open a thread at:

=> Home > Forum > General Discussion > Open Topics

You might argue now "But it worked before the migration, so it must be a plesk - related issue" and as an answer, I just would like to point out, that Plesk itself doesn't change or modify contents at migrations. Your root cause is either, that you modified the "site header" of your root page ( => "hide" = yes/no ), or you use an apache+nginx combination, and forgot, that ".htaccess" - files have to be converted into nginx rewrites ( "Additional NGINX directives" at "HOME > Subscriptions > YOUR-DOMAIN.COM > Apache & nginx settings" ), in order to work. :)
 
Back
Top