richbhanover

Thank you all for your extremely kind responses. I have done some modeling of my own, running a Python program several times, to look at the distribution of random.choices() from a set of 24 items. You’re correct: the distribution I presented doesn’t seem to be out of line for actual random selection.

I guess my concern is one of user experience: Images don’t appear random to the viewer. As I noted:

* The same images frequently appear two times in a row.
* A few images frequently appear several times “in a cluster” that doesn’t seem to be randomly.

Some of you know that I have opened a ticket on Trac https://core.trac.wordpress.org/ticket/51739#ticket.

Consequently, I’m closing this as my thoughts are adequately represented there. Thank you again.

Thanks for the speedy response. I am seeing different images, but the pattern is definitely not random. Two observations:

1) The same image will show up a couple times in a row, or a small set of images will cycle through several times, before switching to other images;

2) The distribution is definitely not random. I refreshed 100 times, with this distribution. Note that certain images appear 5 to 8 times while other were only displayed once.

8 bent branch
7 house with christmas lights
6 trail to franklin hill
6 tennis court fence
6 second mirrored sunset
6 mirrored sunset
6 Holts ledge (little field in center)
5 sunset with big pine in center
5 sunset on snowy field
5 moon mirrored on lake
5 lone red tree
4 ice flowers
4 holts ledge horizon
4 christmas trees on common
5 sun shining on frozen pond
3 orange sky
3 hoarfrost
2 lake beach summer
2 house from hill
2 foggy top to post hill
2 compass hill view
1 pond from pinnacle
1 forest glade
1 foliage on papoose trail

As a long-time computer professional, this feels like a bug. How would I report this? Thanks.

I appreciate your need to simplify the UI for the majority of your customers.

But here is feedback on the trouble I had when trying to find my current PHP version. (It turns out that this was one of the primary reasons I started using Health Check – just to see the PHP version.)

1. The old Site Status tab seems to have been replaced by the new Info pane. So far so good. But that pane’s accordion-like structure makes it hard to find any particular item. I had to hunt around, opening and closing several of the items, to find where you decided the PHP version should be displayed.

2. The “Copy Site Info to Clipboard” does indeed provide all the details underlying the accordion view. But it’s hard to use: after I click the button, I then have to find a place to paste the info so I can see it all at once.

3. The “View extended PHP information” button is hard to find, since you have to scroll way down to the bottom of the page. And clicking it loses my context: I wasn’t in any of the Site Health panes (Status, Info, Troubleshooting, Tools)

4. Also, the names “Status” and “Info” don’t really convey the difference between the contents of those two panes. From their names alone, I couldn’t guess what they’re going to show without actually clicking.

To address all these, perhaps you could:

a) Rename the “Info” pane to “Details” and

b) Put three tabs into the Details pane:
– an “Info” tab, containing the current accordion list
– a “Full Info” tab, displaying as text the info I get when clicking the “Copy” button
– an “Extended PHP Info” tab, with the contents shown by “View extended PHP information”

Thanks.

Great news. (My motto is, “We promise not to fix it if we don’t know it’s broke.”) 🙂

Perfect! Thanks, and good luck!

Sorry – there wasn’t much info regarding the message. Here is a screenshot that I got after I installed and activated the plugin.

That is, I clicked Install, then Activate, and the browser automatically went to the UPG settings page – there was some stuff at the top, then this…

Unexpected Output

I also looked in the error.log file and didn’t see anything related to the plugin. Sorry

Good thought about Securi – I’ll check it and report back. (I just got interrupted, and won’t be back for a bit…) Thanks again.