August 11, 2020 at 02:00 UTC - Views: 21 #65064
Perhaps it is a matter of too much memory attributed to the page_file, that READ MORE does not open to the rest of the story. I am not sure. I thought you might wish to explore it. I had thought it was interstitial advertising below the READ MORE link but I had them removed to no avail. I am on IOS and Safari. the page looks fully loaded but does not respond to the READ MORE task. Here is a link:
Please tell me what you think.August 11, 2020 at 04:54 UTC - Views: 19 #65067
It works for me on edge, but you have other popups that could be interfering with the link.
Just to be sure the social bar on the left does not interfere, scroll away from it before trying the read more.
Also test deactivating non weaver pluginsAugust 11, 2020 at 10:48 UTC - Views: 17 #65069
Thanks, I will explore this further on the test site. I did not know EDGE had a mobile version.August 11, 2020 at 16:46 UTC - Views: 14 #65072
I am testing the “mobile” version by simply reducing the browser size on desktop until the theme switches to mobile layout.
And it is the Chromium based version, so it is the same as ChromeAugust 11, 2020 at 19:26 UTC - Views: 7 #65076
Ok.. How about this. Can we load (Activate) the READ MORE button before the page is done loading? That might be the real problem. ON the mobile site because of the stacked ads, I don’t think it ever finishes loading. At this point just. theory, but I want to know what you think and is it possible. thanksAugust 11, 2020 at 20:38 UTC - Views: 5 #65077
I don’t see it on your page anymore so I can confirm anything.
Do I understand that what you call read more is actually the plus shortcode for Show/Hide text?
If you have anything doing optimization, remove or deactivate that.
And as I said before, if you think the script is not loaded, the issue is not to change any loading order, but find out what is preventing proper execution of the script, as there could be many more potential issues if that is the case.
The way to do that would be to deactivate ALL non weaver plugins, and see if the issue goes away. If it does, reactivate one by one to find the culprit.
- You must be logged in to reply to this topic.