roadsidephil

Thanks, Adam… That seems to have done it. I uninstalled/reinstalled the plugin and then it was able to fetch my Tag account. Thanks for the help.

Turns out it’s some sort of memory conflict with WP Time Capsule. I didn’t investigate further since I’m not planning on keeping that plugin anyway.

Yep, I’m doing that. Thanks.

Yes, that’s correct. Runs fine without Elementor.

No, even once it was connected outside Elementor it still wouldn’t work inside. Asked to be connected, the API popup asked if I’d like to use the connection settings it already had. And then it still sends me off to the Customizer again.

Someone on the Elementor Facebook group said that it could be because of OAuth changes that have been made by Facebook and Insta in the last few days.

Ok, it does seem to be an issue with Elementor. I tried it with all the plugins deactivated except Elementor and had the same issue.

Also tried it with all the plugins activated but on a regular Gutenberg page and it seems to work fine.

So there’s something about when Elementor tries to connect that it pulls me over to the Customizer page for Widget areas.

Might be something the JetPack folks might want to talk with them about since it’s such a popular page builder. But I’ll check in with their support and see if there’s a solution.

Thanks for your help.

Thank you.. We’re getting closer but not quite there yet.

These are the steps I’ve done:
– Tried it in Edge (secondary browser) with a cleared cache and got “Invalid/missing request nonce.” when trying to connect my Insta account.

– Went back to Chrome (main browser), cleared cache and it looked like it was working. Took me to the Insta connection pop up.

– I’m doing this in Elementor. It popped up the Insta window to connect via the API. Then I got a notice about “Do you want to leave this page? Your changes won’t be saved.” Clicked No at first and the widget says “Connecting” and hangs there. Checked the page and the widget doesn’t render.

– Same sequence, but clicked OK on the “leave this page” notice. It took me over to the standard WP Customizer on the Active Widget Area section. But doesn’t give me any way of doing anything with that Insta widget. It does say there’s a more recent autosave, but reverting to that doesn’t change anything.

– Going back to the page in Elementor, the widget is still there, but it’s not connected to my Insta account. Clicking Connect again gives me a message like “you previously linked WordPress to Instagram. Would you like to continue with your previous settings?” Clicking Continue sends me on the same adventure as previously.

Ideas?

Thanks for your help Angelo. I suspected it might be related to that.

I use the Libsyn feed because it’s more stable and safe than the WordPress feed of course. And my podcast already shows up in searches and in the podcast app, Alexa, etc.

So wouldn’t that big long Google link just link to the show in the podcast app? There’s no way to link to it from a site that isn’t hosting the RSS feed?

Thank you, I’ll do that.

I was having trouble finding the garbage code manually. But I usually look for it if there’s a discrepancy.

Ok, never mind… I re-ran the Sucuri check with a cleared cache and it seems to be clean now. Wordfence had found a glitch in the nav that was fixed and it looked like Sucuri was still finding garbage, but the re-run test seems to be clean.

It’s a membership site and that’s the front page. So no links going inside it from there.

I think I’ve got it figured out and it seems to be working now. Here’s what I did.

I remembered I had a Google split test going on that site, so I stopped that. That’s when the front page started coming up again. Everything else was still a blank white page.

I got two messages in the permalinks settings: The PHP version on my server needed to be upgraded, and WP wasn’t able to write to my htaccess file.

Got my host to upgrade the PHP which got me from blank white pages back to server level 404’s.

I temporarily changed the permissions on my htaccess to 777, resaved the permalinks, then changed the htaccess permissions back to 644.

That seems to have done the trick. Still not sure why it happened out of nowhere, but it seems ok now.

Thanks very much for your help Christy. ??

Not that I can see. Actually now the front page comes up fine. And the rest are coming up just as blank pages. Not even any code in the source. Still all visible in the back end for editing.

Here’s an example of an internal page not coming up: https://www.roadsideattraction.com/members/members-home/

Thanks Christy… Yes, I double checked all the spellings and everything is correct. And everything opens fine on the back end.

Ok, I just figured it out. Didn’t need to use the beta. I was using image codes, but forgot to the click the “image code” radio button. So it was trying to serve code that wasn’t there.

I’ve had the same problem today. I found the malicious code in one of my plugins and removed. Also found it in the vars.php and removed it.

I’m using version 2.8.2

Now two other things are happening. When I post a new entry from the main edit window, the resulting page is just a blank white one. The entry does post though. Same thing if updating an entry. Doesn’t seem to do it from the quick edit page.

Also, I wanted to updgrade to 2.8.6. When I click Upgrade Automatically it just says it’s downloading the files but doesn’t go any farther.