JKEngineer

Thanks.

I understood that. I could not find a the link in Cloud to enter the settings for Cloud. Please point me at it.

Thanks,

Jack

Is there a place in Cloud to duplicate the settings?

Hi Nithin,

Thanks.

I have revisited the page that had the strikethrough on the “bad” links. They are now shown normally, so that is a good thing! I’m not sure why it changed – perhaps because I ran scans again from Local.

With the Tweaks settings all unchecked and, for now, zillow.com and hotpads.com excluded for Local checking, the results are now much better. Far fewer reported bad links and no strikethrougs. Of course, if there is a bad zillow or hotpads link I will no longer know it. That is a problem. Perhaps I will remove them from the exclusion list and keep the Tweaks turned off. That way only I will see the “bad” links and can confirm them manually as necessary. The visitors won’t see anything untoward.

Can the settings I applied to Local be applied to Cloud? I don’t see a place to do it. If not, I will be forced to continue to use Local.

Jack

I did the “nuclear option” of clearing the database and running a new scan. While I am not sure it is done, I am not seeing as many broken links.

Zillow and hotpads links are not being reported. So I guess the exclusion worked. Is it safe to use it?

The strikethrough links are still there. Using Inspect, I see:

<a  target="_blank" rel="noopener" class="broken_link">Nearby Homes&nbsp;</a>

It has class=”broken_link”. which is, no doubt, why it has the strike through. How do I fix this?

The links being reported now don’t seem to have the strike through, which is a good thing! That was really my biggest concern.

Hi Saurabh,

I don’t think I ever visited the Settings page!

I made the changes in the Tweaks under settings and Saved. I marked one of the links reported as Not Broken. It is still crossed out on the site’s page. It’s this one:

“Apartment and Home information from Hotpads.com

Broad Area Search with Multiple types of Dwellings? This link will

on https://www.vcjewishcenter.org/about-us/our-community/moving-to-van-cortlandt-village-real-estate-info/ “

I did the same for one of the zillow links. Same problem.

Also:

I saw that the settings had a box for excluding links with specific text. See screenshot. https://www.dropbox.com/scl/fi/ha17u8eq20dvw7kv5ffhl/Local-Broken-Link-Checker-Van-Cortlandt-Jewish-Center-WordPress_001874.jpg?rlkey=5vlfyz59aatoefln0wyu17kcb&st=t42zbuvi&dl=0 Is this a way to avoid having BLC work on links to sites that it cannot actually get to? Will it apply to both local and cloud?

Your report cites https://www.google.com/calendar/render in >7,000,000 places. Your docs show that you are not checking play.google.com or https://www.google.com/drive. How do I tell it to also not check google.com/calendar, for example?

How do I tell BLC to not check links to sites I have now found you get blocked from? I see on the documentation that you have a list of sites you have learned to ignore (I assume you don’t test them at all). How do I add, for example, hotpads.com or zillow.com to that list?

Thank you for the fast response.

I am not clear on how to set the plugin to ignore certain types of links. For the link I cited to hotpads.com I hit the three dot menu on its right and selected Ignore Link. The webpage with that link still shows the strikethrough. (I did do an F5 refresh and also tested in incognito.)

How do I fix this?

OK, thanks.

Here’s an update. I reloaded the Laragon localhost site after being shut down overnight.

I was able to access the “starter templates” link under the plugin’s entry. (and it is the only plugin on the site). It took me to a display of the templates available and had a link asking for updates to the AI info. I clicked that and found that all of my previously entered data for guidance to the AI was still there. I clicked through to the template display again.

I selected a template and was told it required the Kadence theme. (That should have been upfront info.) I installed the theme and went through the rest of the options and got a fully built site.

The error issue was bypassed this time, but I don’t know why or how. The cause needs to be addressed.

With your enhanced instructions, I tried again. It worked.

thanks.

Jack

On 6/9, I deleted the entry shown as “row” below:

Database: nysspesu_wp619

Table: wpvividstg01_options

Row: wpvivid_staging_data

The top bar color was not affected. I logged out and back in, still orange.

Restore the database. Forced logout.

Logged in.? Went to check restored content in database.? Get this error:

Error in processing request

Error code: 200

Error text: parsererror (rejected)

It seems that the connection to server has been lost. Please check your network connectivity and server status.

Repeat the database restore. Have the WP phpMyAdmin plugin turned off for the restore.

On logging in again, it is turned on.

Still getting error.

Tried in MS Edge.? Did not get error.

Shows the list of tables.? Can filter for optio.? Won't load wpvividstg01_options.? Close the window and do a full backup.

Now I am not getting the list of tables.

Deactivate / activate.? The phpMyAdmin page loads, but is not responsive.

Try in Chrome again.? Get the error above.

I left it alone.

On 6/12/24, I logged into the staging site and its top bar was black, not orange. I logged into the production site, still orange. In the production site, I reactivated the WP phpMyAdmin plugin and had no issues accessing the tables in Chrome (other than the first attempt gave me a 1 hour timeout – which has happened multiple times before).

I seem to be dealing with issues of both WPVivid and the WP phpMyAdmin plugins. I think leaving the top bar orange may be the wisest decision.

OK. I submitted a ticket at Core Trac.

Thanks for the advice.

What I am seeing is a change from all the historical interactions I have had with WP. “Select All” only used to be triggered (other than by clicking it explicitly) if I actually selected all the plugins. It is now triggered if I select any plugins.

I believe the same happens in the update box for themes. That is also a departure from previous behavior and also, in my view, a bug.

This is not a hosting issue. I have had it occur on all the websites I manage, representing several different hosts.

My understanding was that this forum was the correct place to report a bug. Do you feel that it should be in the Core Trac?