• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Question Entire page not being displayed in preview mode

pintsizelala

New Pleskian
Server operating system version
Windows
Plesk version and microupdate number
Obsidian 18.0.54
Hi all

I am having an issue with Plesk preview whereby the entire page is not being displayed

I have been developing the site in VS Community and it works perfectly fine in debug but as soon as it is uploaded to the server and viewed through Plesk Preview it only serves about 3/4 of the page and then just stops

I cannot think of why it would be doing this so any help would be greatly appreicated

The preview can be viewed at: [URL redacted]

Cheers

Eric
 
Please check the source code of the page in the browser to see where it breaks. Then check your true source on the server to find out what line comes next and where the syntax error is so that it breaks. Normally the cause for such breaking pages is a missing resource or a malformed file, e.g. a file that was only partially uploaded.
 
Hi Peter

Thanks for this - I have viewed both ad the code uploaded to the server is valid html so that doesn't appear to be the issue

Cheers

Eric
 
Can you show an excerpt of the source where it ends on the server and how it should actually continue if it was delivered in full?
 
The source from the page is:
Code:
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Maecenas ullamcorper ante ac lectus vulputate, ac sagittis nibh faucibus. Suspendisse potenti. Morbi non magna at metus mollis congue sed eget magna. In dictum faucibus auctor. Ut sit amet arcu lacus. Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas. Nunc fringilla bibendum efficitur. Curabitur eget est malesuada, mattis sem a, eleifend mi. Pellentesque gravida elementum est, at efficitur ligula. In tempus egestas dui, ut blandit eros ornare quis. Fusce auctor maximus lacus. Vivamus ut molestie ligula. Cras vel nisi ornare, ultrices leo sed, condimentum dui. Vestibulum mattis molestie lorem, in accumsan velit pelle

It should contuine like:

Code:
</div>
            <div id="footerArea">
                <p>Sponsors and Affiliates</p>
                <div id="sponsorsLogos" class="clearfix">
                    <div class="sponsorLogo"><img src="/images/lmLogo.png" alt=""></div>
                    <div class="sponsorLogo"><img src="/images/ngLogo.png" alt=""></div>
                    <div class="sponsorLogo"><img src="/images/siLogo.png" alt=""></div>
                    <div class="sponsorLogo"><img src="/images/jplLogo.png" alt=""></div>
                    <div class="sponsorLogo"><img src="/images/nasaLogo.png" alt=""></div>
                </div>
            </div>
        </div>
    </form>
    <script src="/scripts/sheetslider.min.js"></script>
</body>
</html>
 
In your source, at least a closing </p> is missing. It normally won't break a page when a section end </div> follows, but it could be that an "invisible" control character is ending processing that string.
 
Sorry there is a closing </P>

I have copied the source code from the debug version into an html validator and it validates correct - it is only once it loads on to the server and you view it through site preview that it stops working properly

Hence why I was wondering is it was a site preview issue or a configuration issue perhaps
 
I would only suspect an issue with the preview if the page content is exceptionally long so that a limit on what the server can deliver is reached. So far we have not been getting similar reports, so this is not very likely.
 
Back
Top