gfbhwo

Can you join the dots for me here?

I reported seeing blank usernames in the report. Do you mean that they were blank because the username was too long to display? I do not have any usernames longer than ones that were already able to display.

So what exactly is this update? What has it “fixed”?

You can add the following before the stated code to make it apply only to FAQ product:

.faq_content

Are you going to put that in an update?

Thank you! I reported this problem to both Jetpack (as a submit button on a Jetpack form was not showing up properly) and Spider FAQ. The Jetpack folks pointed to the Spider FAQ as the culprit but I haven’t the time to plough through the CSS. THis is prety poor CSS programming however, particularly for something like WordPress where there are likely to be so many CSS files.

That’s pretty much a non-starter; IT security 101.

I will spend a little time trying to find this on my own. If it isn’t a quick solution I will either find a different contact form or a different FAQ plugin.

BTW, I fully realise these are both free plugins, I have no criticism for either one. You get what you pay for ??

Thanks.

Thanks for following up, the page with the contact form is:

https://newportsoccer.org/contact-us

Hire’s what I heard back from Jetpack support as to why they pinpointed Spider FAQ:

“we simply disabled additional stylesheets from plugins, and narrowed the issue down to Spider FAQ. The submit button showed up when Spider FAQ’s stylesheet was disabled.”

Ditto on the PHP version; I really think that the plugin should not update if it isn’t going to work with the PHP version. Alerting you after the fact is none too helpful. I have no control over the PHP version from my hosting company.

I have deactivated the plugin and will probably delete it. A shame as it was a nice plugin, but I can’t afford to have things suddenly stop working like that. I’ve reverted to HTML-coding the buttons which is a pain. I’ll have to find an alternate plugin.

The CSS portion goes in the box below where it says: “Add your custom CSS below…”.

Also the above is missing one line in the CSS:

.clearboth {clear: both;}

I found that the use of the “h3” tags was a bit too much; it made the RHS of the entry too big. Instead of:

<li><h3>[staff-name]<br>[staff-position]</h3></li>
I used:

<li><strong>[staff-name]</strong><br>[staff-position]</li>
Other than that, very useful thank you Colin

I found a workaround. For each image you want to use as a header, you have to select it as a custom header under “Appearance”. Then it shows in the header widget when editing pages. I don’t recall having to do that under 3.6.1