jeffersonpowers

@webnus also, can you please tell me the exact settings you have in place for the demo page you linked to in your earlier comment?

@webnus —

I’ve tested it several times with the Twenty Twenty-One theme and no other plugins active, and still got the same issue. Normally my site is running the Pinnacle theme (free version) and the following plugins:

Kadence Blocks
Page-List (installed after this issue started)
UpDraft Plus
Virtue/Ascend/Pinnacle Toolkit
Wordfence Security
WP-Optimize

I routinely run these plugins on dozens of websites and have never run into any problems with any of them. Again, I did test with all other plugins turned off and still got the issue I’m describing.

Can you at least confirm that you are seeing the issue when you look at my site?

@webnus UPDATE — this issue appears to only be happening in Chrome (on Windows or Android) and in the Samsung Internet mobile browser on Android. It does not happen in Firefox or Microsoft Edge (I don’t have the ability to test in any other browsers).

So it looks to be a Chrome/Android issue. Can you test and confirm?

@webnus —

I’ve tried it twice now with all other plugins turned off, and the theme switched to Twenty TwentyOne, and there is no change. I am getting the same result, so no, it is definitely not a theme or plugin conflict.

Did you look at the link I provided (https://denverastro.jeffersonpowers.com/test-page/) on a mobile device or in developer tools? I want to make sure you understand what the issue is – when you tap the right arrow it moves normally, but when you tap it a second time it rapidly advances to the last event. From there, when you tap the left arrow, it moves to the next-to-last event, but then when you tap either arrow it goes back to the last event, and remains stuck there.

Can you please provide a link to your test or demo page, so I can see the Type 2 style carousel working normally on mobile? Thank you.

Hi. When you say you’re not seeing the issue, do you mean that you don’t see it on my website, or just that you’re not able to recreate the issue?

Please remember, this is only happening in the mobile view, so you will need to look at it on a mobile browser, or in a mobile emulator such as Chrome’s developer tools.

@wfadam as of 12/22 at 12:00 pm pacific, reinstalling Twenty Twenty One does not fix this issue. The changes to the files are even more minor than they were before, but Wordfence is still flagging them as modified. Here’s what “view differences” is showing:

Original version: * @since 1.0.0
Modified version: * @since Twenty Twenty-One 1.0

The exact line number varies but it’s always near the top.

This is very minor and clearly not going to cause problems, except that WF will keep flagging these files and sending alerts about them, but I imagine people are going to keep posting about it until the issue gets fixed.

No, I determined that the client was not actually using this plugin for anything, so I deactivated and deleted it.

Would these be error logs that are specific to the Constant Contact plugin? If so, how do I check and review them? If not, can you be more specific about what error logs I should be looking for?

I’m talking about the home page title background image when you have “Choose A Home Page Slider” set to “Page Title.”

I did some additional research and it appears that there’s no way to add alt tags to background images, and no reason to do so either.

This came up because Yoast SEO is telling me to add alt tags to all my page images, and the only image on the home page is the background image behind the page title. I’ll follow up with Yoast support.

Thanks for your quick reply!

They’re all on the same hosting company, one that I’ve been having some related issues with. I will take it up with them. Thanks!

@hristo-sg Thank you for responding. I was not aware that Siteground hosting was Managed WordPress by default — I maintain backups and updates for my clients, so I don’t normally recommend that they sign up for managed accounts.

What I object to is Siteground making these changes without informing us of what you’re doing, and giving us a choice to opt out if we want to handle updates ourselves, or if we want to see the full Site Health report without part of it being blocked.

@mymothersdaughter they are blocking several Site Health notifications from appearing – one about your PHP version, one about auto updates being disabled, and one about a missing PHP extension.

If you want to see if your site is affected, check your wp-config file, there will be a line of code added to the end with a note that reads “added by SiteGround WordPress management system.”

None of them are critical notifications, but I don’t think it’s Siteground’s call to censor the Site Health feature like they’re doing.

• This reply was modified 5 years, 6 months ago by jeffersonpowers.

@diondesigns I’m seeing this happen across several Siteground accounts, none of which should be on any managed WordPress plan. You make good points about PHP and imagick, but wouldn’t those be issues for the WordPress Site Health development team to address?

I don’t think it’s the hosting company’s place to decide what should be blocked from the Site Health scan, and I don’t think they should be modifying our website files without asking first and/or telling us why they’re doing it.

@duongcuong96 — I don’t understand what you are asking.

I should not need WinRAR to open a .zip file in Windows. This is the core problem — BackWPUp .zip files are not opening in Windows.

7Zip works as a perfectly good (and free) alternative to WinRAR, and I’m getting errors when I try to open BackWPUp .zip files. I don’t get this problem with any other .zip files, only the ones generated by BackWPUp via the WordPress dashboard. More importantly though, I should not need it to open a .zip file.

UPDATE: this is happening with backups that I download via the BackWPUp controls from within WordPress. If I download the same backup file from remote storage (DropBox), it opens normally and all the files appear to be there.

So, not the crisis that it first seemed to be, but still a problem.