Robert Lee Murphy

My website is restored now, and here is a summary of the actions taken.

1. Some of you suggested it might be a cache problem with my browser, but I clear the cache everyday. I have decided to work on my site using Explorer rather than Edge, however. It takes CCleaner several minutes to cleanup the junk Edge leaves behing.
2. I attempted to restore the site using one of the backup files I had created using BackupWP. I followed their instructions, but after churning for twenty minutes, my FTP client notified me the file was too large. BackupWP does provide two additional possible ways to restore, but I decided to try something else.
3. I deactivated my plugins, and reactivated them, one at a time; but that revealed nothing.
4. I decided to rebuild the missing pieces of my site from scratch, and in doing so, it became apparent that the missing pieces were all powered by Jetpack.
5. I deleted Jetpack (not just deactivated it) and reinstalled Jetpack. Then, information about the missing pieces appeared, but they were not working on my site.
6. I had to go through the various sections of Jetpack and reactivate them one at a time.
7. The guilty party turned out to be Jetpack. It probably caused the problem when a recent update was installed.

Thank you for your suggestions. I will close this line now.

I apologize for losing my temper. I appreciate you all being willing to help. Yesterday I had a family matter that precluded me working of the repair. I will try your suggestions today. Thank you.

I was logged into my file manager account and ready to make the insertion you suggest when I decided to check my website once more. Low and behold, it had fixed itself. Everything is back to normal. I suppose just the threat of me messing around with the code made WordPress take corrective action. Thanks for your help, anyway. I will keep the information for future reference–which I hope is never required.

A side note for others who are following this tag. Last night, when I had given up for the day, I logged out of my website account, but I left all my plugins deactivated. Wrong! Overnight scammers attacked my contact form and junk got through. So, remember to reactivate your plugins before you take a break in resolving a problem.

I have just realized that the toolbar is missing in both the Post and Page functions. How do I activate the toolbar?

James, thanks for the suggestions; however, nothing works. While fooling around I discovered that when I open any old Post with “Edit” or “Quick Edit,” no text appears in the Body Copy Box. But, if I open the old Post with “View,” the page appears as originally posted with all text visible on the site. I then discovered that is I type text into the Body Copy Box, even though I cannot see what I am typing, when I “Preview” the Post, the text appears on the page as if it were published.

Pepe, I brought my wife home from the hospital today, so I will be able to work on the Media Credit problem more regularly.

I have just checked all of the sites to which I send a feed via JetPack’s Publicize feature. The sites showing the shortcode are: Facebook, Google +, and LinkedIn. Two sites are not showing the shortcode: Twitter and Goodreads. Maybe this information will be useful.

Regards, Robert

Yes, I am using JetPack’s Publicize feature. Am I the only user of Media Credit who is having trouble when also using JetPack? Surely there are dozens, if not hundreds, of users doing the same thing.

I appreciate your checking on this for me. Robert

I forgot to mention that I do not have a “refresh” option in Facebook.

The new post that appeared on Facebook and other social media sites this morning still shows the shortcode.

Last night I installed the latest version of Media Credit. This morning I installed the newest version of WordPress (4.0) and an update to the Twenty Ten theme.

I may have to abandon Media Credit if I can’t get this resolved.

Robert

I am advancing the post I originally had scheduled for Monday to tomorrow, Friday. I’ll check it, as can you, on my Facebook Page in the morning. Every time I preview a post, the shortcodes do not show. Thanks, Robert

Not sure how to update the FB share. Shall I try deleting all the postings in FB? Any suggestions?

I’m using the Twenty Ten theme.

Just about time to head to the hospital. Not sure when I’ll be able to check back.

Thank you, Robert

My apologies for taking so long to respond, but my wife is having back surgery and I spent the entire day at the hospital. I expect to be there all day tomorrow as well.

Media Credit showed that it was an activated Plugin, but I deactivated and reactivated it just to be sure. It shows it is activated.

I deleted the filter that I had added as well.

I just rechecked the shared posting on Facebook and the unparsed shortcode still appears.

Thank you, Robert

The Media Credit was attached to the second of two media inputs, halfway into the article. Facebook picked up the second input rather than the first when it was shared on my Facebook Page: Robert Lee Murphy. You can go there to see the result. I have added the shortcode you provided, but it did not remove the code from the existing post. Perhaps it will prevent it from happening next Monday when I have a regular post scheduled. My WordPress site is: https://robertleemurphy.net.

OK, Pepe. I figured it out. For others who are computer challenged, here’s the path I took. From the cPanel I located File Manager, then a dialogue box ask me to select Web Root, then I chose Public-html, the wp-content, finally plugins. I selected all of the files for Media Credit and deleted them. Then I returned to my Workpress Dashboard, chose Plugins, and lo and behold Media Credit appeared in a form that allowed me to download it. This stuff ain’t easy for some of us. Thanks for your patience and your guidance.

Thanks, Pepe. I’m not that familiar with the location for the directory you say I need to delete. Do I find it on my WordPress site, or do I have to use the cPanel?

The problem is resolved. I experimented with a different SEO plugin and I think that frightened the original one to start working.