This weekend saw repairs, both physical and virtual, being made around here. During two significant storms this winter, high wind removed most of the top course of my new vinyl siding from my newly sided garage. When I purchased the siding, I opted for a type of top-course treatment that didn’t require nails. I wasn’t convinced it was a good idea, but the salesman assured me that this “undersill trim” clamping strip works really well. When I was installing the top course, it felt snug, but I was tempted to add some construction adhesive. I didn’t. It looked great, but of the eight pieces of siding along the top course, three came down and one more tore loose. None were damaged. All were replaced this weekend. Construction adhesive was added.
The virtual repairs offered less of a success story. I’ve been dealing with the WordPress Happiness Engineers (that is what they are called, not a snarky nickname I’m giving them).
Earlier in the week, I had reported two problems.
1) Galleries assembled in the Guttenberg editor don’t show captions when viewers hover over the images in a tiled-mosaic arrangement. In addition, the “Descriptions,” which do show if the viewer clicks to invoke a slide-show, appear so far below the image that people don’t see them (unless they know to scroll down).
2) A majority of the blog sites I visit while using Firefox, do not present me with a “Like” button. When I finish reading the post, I see the word “loading” but the page has completed loading, and the button never appears. I have to reload the page in order to see the like button. In addition, after reloading and liking the page, if I write a comment, I can’t post it. Reloading the page doesn’t help. I have to copy the comment I wrote – exit the page – reload the page from the email – paste my comment back in before I can post it. I’ve cleared cookies, my cache and I even went so far as to uninstall and reinstall Firefox.
I posted these issues via email.
I received a “Success” screen.
I never received any follow-up emails…until Saturday. On Saturday, when in addition to not letting me Like or comment on Cheryl Pennington’s post, the page wouldn’t let me Tweet her post. So, when I manually Tweeted the URL of Cheryl’s post, I tossed a jab at WordPress.
The Happiness Engineers (HEs) responded.
As expected, following the mantra of all social media administrators, the HEs tried to direct me to move the conversation out of Twitter. They prefer email, because it allows for longer messages, AND because it takes the conversation out of public view. I continued to respond via Twitter. I explained that I had already tried email and was ignored. I have a Premium account; I’m entitled to a response. Finally, they asked me for my blog’s URL and they emailed me.
I must say, the people I’ve been dealing with are nice, professional and they seem determined to help with the Like/Comment/Tweet problem. We have not made progress, but I feel like they are working on the issue. I have not received a response about the Guttenberg Gallery issue.
I’ve been using these Monday posts to highlight my journey through 40-plus years of technology, as a systems developer/designer/manager. Three things bother me about this situation from the perspective of that experience:
1) Re: Guttenberg – you do not replace a system with a new version until you can replicate all the desired functionality of the previous version. Galleries in the Classic Editor work really well. The Guttenberg versions are not yet ready for production (our term for Prime-Time).
2) Re: Like/Comment/Tweet – You need to listen to the people who are complaining. I have exchanged multiple emails, answering questions about how the problem manifests itself. All of these questions were included in the information I sent in my initial email.
3) Re: Like/Comment/Tweet – Test everything, everywhere! The issue I am fighting is that I experience this problem in Firefox (and Safari) but not in the Chrome browser. This observation is frustrating – it’s as if they’re saying “well, just use Chrome.” I prefer Firefox. That’s not the point of frustration. The point of frustration is that many developers only test web-based applications in Chrome. If it works there, they release it.
The problem could be with the WordPress developers, or, perhaps even more likely, the developers who created the theme I/you use. I have other problems with the sites I visit when I try to view them in Firefox that are likely related to those themes. For some of you, I can’t see your pictures, and for some, I can’t make a comment (even when comments are working in other sites). For you guys, I load your site into Chrome.
We should all test our blogs in every browser we can. On laptops, on tablets, on phones. If we don’t have access to these devices, we should ask for input from our readers.