Checking the database within WP, the posts show as being there. However, when I check the post listing, it says “No posts found.”
Which posts table did you look at? There should be multiple ones.
It appears to be after I moved my .htaccess file as wordpress was giving me a warning that it might be “visible.”
What plugin told you to move it?
Did you move it back?
It was not a plugin. It was a yellow warning that appeared at the top of my dashboard, and I have now moved it back.
Now the posts still don’t show even though at the top of the posts page it shows them as published, the actual listing shows “no posts found.”
If I remove the moved .htaccess, then there is a database error and WP won’t open. So I now have 2 .htaccess in 2 places and I still have “no posts found” while the db shows that the entries exist.
This makes no sense to me whatsoever.
Also the system created 3 directories in my root directory today. Have no idea why.
WordPress has NO feature that tells you your htaccess might be visible.
What folders are being crated? This is starting to sound like a hack.
Interesting as I manage another wordpress site on a different hoost and It started getting that message some time ago. It disappeared for a while and then reappeared on an update. It states
“Your backup folder MIGHT be visible to the public” and then says to move it from the wp-dpmanager folder to the backup-dp folder.
anyway, the folders created in the root directory are:
domain.wordpress directory
domainwordpressdirectory
domawordpressdirectory
That message is coming from a plugin – specifically wp-dpmanager.
When I drill down
domain.wordpress directory
blog1
wp-content
wp-resources-back
file1.4.3
domainwordpressdirectory
blog 2
wp-content
wp-resources-back
file1.4.3
blog 3
wp-content
wp-resources-back
file1.4.3
domawordpressdirectory
blog 4
wp-content
wp-resources-back
file1.4.3
The indents did not show up
domain.wordpress directory
..blog1
… wp-content
……. wp-resources-back
………. file1.4.3
domainwordpressdirectory
..blog 2
… wp-content
……. wp-resources-back
………. file1.4.3
..blog 3
… wp-content
……. wp-resources-back
………. file1.4.3
domawordpressdirectory
..blog 4
… wp-content
……. wp-resources-back
………. file1.4.3
Use code tags (see the quicktags buttons above the text entry box 🙂 )
Wait wait wait wait…. WHAT?
Multisite DOES NOT have multiple folders. Everything is virtual. Are you telling me you actually have physical folders named blog1 and blog2 out there? If so, you are not using Multisite.
They weren’t there for weeks, and then on 10/20 they appeared. Not only that, wp is installed in the root of domain.net and the folders were created in the physical root of domain.com. I have two domains hosted at the same host. Hence the first domain (.com) is the physical root.
Here is a print screen. As you can see, it shows 46,136 posts and yet shows “No posts found”
Those directories just got created out of thin air. I don’t know why and I really don’t understand them being pushed all the way out to the physical root directory.
I set it up as a multi-site and it is showing Network Admin and all of my blogs. SO it is running as a multi-site …. kind of. All of my posts were there, and now they are only accessible for “Blog 1”
I was planning to switch from MT to WP running in multisite mode. This .net setup is a trial run to get everything working. My hope was to somehow shift the whole shebang to my .com domain and replace the MT blogs, or else redirect and relaunch on my .net domain.
Now I have some mysterious error that is driving me nuts.
Help. Please. I don’t even know where to start.
I tried “repairing” the database and now it won’t access wordpress at all. I get an error message:
“The site you have requested is not installed properly. Please contact the system administrator.”
I had hoped to not go back to ground zero on this install as I have about 60 hours work into it.
Is there a way to fix it and get back in, or should I just start from scratch again?
Those directories just got created out of thin air. I don’t know why and I really don’t understand them being pushed all the way out to the physical root directory.
Um…. So two options here, neither are great.
1) Hacked.
2) Rogue plugin
How did you run a repair?
Do you have a backup from before this happened?
