caspersgrin

Figured it out. Solved my own problem.

In what way is it not responsive. It scrolls automatically and the previous next arrows both work. So I’m not sure what your issue is.

Rob Tanner,
Webmaster,
Unitarian Universalist Fellowship of McMinnville

Okay, I finally figured out how to control the size and style of the captions, but I’m still mystified on how to change the order in which the images are displayed. Can someone please help.

Thanks,
Rob Tanner

I discovered that my WP site is automatically updating plugins which, of course, is certainly convenient but I thought about it and decided that might be too risky. Better to update plugins on my staging site first and then manually update after checking it out. Am I being wise or overly paranoid?

I would generally agree with shamser_suzon’s evaluation except that I have the most recent version of the WP User Frontend plugin installed on my WP 5.0.3 site and it fails to work at all. I contacted the publisher directly with as detailed a description of the failure as possible. The next day I got back a message saying that the developers had identified the problem as a Gutenberg compatibility issue (which seems strange as WPUF version 3.0.2 is supposedly tested up to WP 5.0.3). They said that a fix would be forthcoming. And since having a frontend is critical for my bloggers, I asked about an estimated time frame. That email was met with deafening silence. So now I’m looking at the plugin User Submitted Posts. It’s not nearly as full featured as WPUF, but it’s a far superior plugin in that it works as advertised.
~ Rob

Thanks.

Okay, a bit more looking and I figured out the dashboard and it all appears to work as it should.

I wonder why the reference to the template went into style.css header comment. The real problem was that none of the material I read through told me that I needed to activate the child theme template reference is what points WordPress back to the parent. And you’re right, the Handbook makes things much clearer. Live and learn. And thanks!!

~ Rob

It turns out that just switching from Safari to Firefox resolved the issue.