6.1.1 Pip/Classic Installation yields ugly/corrupt output

Plone Support
1

I installed Plone 6.1.1 on Kubuntu 24.04 using the pip installation method described at Install Plone with pip — Plone Documentation v6 . I selected the Classic view and walked through the installation per documentation, then got the ugly/corrupt output -- basically just text, with minimal markup and some page corruption with lines over-writing each other.

Interesting side-note: The initial installation page rendered well, with the familiar Plone interface fully intact.

I ran the installation in a terminal with the installation output foregrounded. I wasn't able to capture all the output but I have 500+ lines with only three warnings regarding portlet setups. I don't see any failures.

What do I need to do to get a properly rendered site?

2

You need to provide the full stacktrace of you your ugly/corrupt output as text.

You could also try Cookieplone.

3

@jreese Does your site look a bit like reported here?
Then you are probably viewing it at 127.0.0.1 instead of localhost. Try viewing it at http://localhost:8080/Plone (assuming the default port and site id here).

4

Thank you very much for your response. Yes, that is exactly the page I have encountered. Wish I had a better word for it than 'ugly'.

I was able to reproduce the problem with localhost and the 'localhost' / 'Plone' address using the current Google Chrome. (This was the version now two weeks old -- currently I have version 135.0.7049.84, but it updates in the background frequently).

I honestly can't remember if I flushed the cache or not -- an oversight -- because I was able to overcome the problem by switching to Firefox. One reason I didn't bother to dump the Chrome cache was because I got the same 'ugly' page in Firefox once or twice at first, so I was dissuaded that a cached page might be the problem. After a couple of 'uglies', however, the page rendered properly, and I have been using Firefox with Plone ever since. It consistently renders properly. I haven't gone back to Chrome with Plone so I don't have a comparison.

I concluded that the problem is the rendering engine (Chrome), not Plone, but that the speed of response may have had a role. There may have been a Zope factor but I'm sure the primary issue was the browser.

FWIW I'm using an old-ish Dell Inspiron running Kubuntu 24.04. The video graphics driver is the proprietary Nvidia 550 (tested) driver.