Hi all,
So I am not an expert WordPress user but I get by just fine running our library’s adult blog and know my way around all the basic stuff that I need. Someone upstairs in the children’s room asked me for help figuring something out this morning with the youth blog and we both absolutely cannot figure out what is going on. Here’s the problem:
The person who used to usually run the blog has left. A new person is going to run it and they BOTH LOG IN WITH THE SAME USERNAME AND PASSWORD. Exact same. We can’t come up with any reason why it would think they’re different people.
The new person has tried to post two times and it \*shows that her posts have been published,\* they are marked as public, they are categorized the same way the previous person categorized them; basically there are no discernible differences between these posts and the previous person’s posts. BUT they don’t show up ON the blog itself, in the stream of posts. The only way you can find the new person’s posts is to click on the URL from the editor (or bookmark it, whatever- point is you can just view the single post separately).
We also noticed that when we look under All Posts and go to Published, none of the previous person’s posts SINCE 2020 are there… So they’re on the blog, in the stream of posts, and she’s posted recently, but they are not showing up under published posts.
….WHY?!!?!? What is going on? We can’t come up with a single difference between the two users other than currently using different machines, but I can edit the adult blog all the same on my work computer, home computer, and the app. Really would appreciate any help!
[ad_2]
Make a unique account for testing and publish a test post. See if it shows up.
When you say “don’t show up”, I assume you mean the Blog Home page, where posts are typically indexed. I would confirm that page is properly setup, as there’s an oddball chance that someone was manually managing it instead of letting WordPress do its thing.
If the posts are published and public and you can reach the post directly in a browser (without logging in), the problem is likely with the home page.