Moderator
James Huff
(@macmanx)
Volunteer Moderator
Try re-saving your permalink structure at Settings/Permalinks in your admin panel. If WordPress cannot automatically edit the .htaccess file, it will provide manual instructions after saving.
Thread Starter
SauloB
(@saulob)
James, thank you very much for the reply.
But unfortunately this don’t do anything, the .htaccess is fine, no change at all. I did that and same thing. Right now I put the site to use the default model /?p=code , it’s working, no problem at all.
It appears something is gone from the database, I wish I could know what it is, what field on the database it’s the %postname% code and what deleted it 🙁
Moderator
James Huff
(@macmanx)
Volunteer Moderator
Just to make sure it’s not a plugin conflict, try deactivating all plugins, then re-save your permalink structure. If that resolves the issue, reactivate each one individually until you find the cause.
Also, have you tried switching to Twenty Ten to rule-out a theme-specific issue?
Thread Starter
SauloB
(@saulob)
Great, doing that now.
Disabled all plugins, re-saved permalink structure to /%category%/%postname%/ , nothing at all.
All the post links lead just to the /%category%/ , the %postname% is gone.
http://www.avault.com/news/giveaways/
Changed the theme to WordPress Classic 1.5 (we don’t have the Twenty Ten anymore)
re-saved permalinks again.
Our .htaccess file:
———-
Options -Indexes
Options +FollowSymLinks
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
———-
I already went to everything back, plugins, theme and the permalink /?p=code
Thanks James. But I did that the first time it happened. Tried everything. Really everything, read a lot of forum posts, nobody has this error. Something deleted the %postname% codes from the database, it’s the only thing I can think of.
Our site is secured. But I can only think of one attack or a bad (bug) code inside a plugin that could delete it 🙁
Moderator
James Huff
(@macmanx)
Volunteer Moderator
Is the post_name column blank for all of the posts in your database’s wp_posts table?
Thread Starter
SauloB
(@saulob)
I think so. I’m going to download the database and check it.
If it is, what do you think it happened? Any thoughts? Never heard of any problem like that?
I emailed the guy responsible for the server, asked if he has the MySQL log, to check the queries, maybe the query that deleted the column should appear. Gonna wait for his reply
Moderator
James Huff
(@macmanx)
Volunteer Moderator
If it is, what do you think it happened? Any thoughts? Never heard of any problem like that?
I’d suspect either a plugin conflict or a malicious attack.
Thread Starter
SauloB
(@saulob)
Yeah, same thing. I was thinking about a malicious attack.
Right now we are using 43 plugins, all of it know plugins, do you know any plugin that has caused something like this? (it’s the second time)
Our plugins:
- Admin Show Sticky
Akismet
All in One SEO Pack
Allow Multiple Accounts
Dagon Design Sitemap Generator
Degradable HTML5 audio and video
Easy Gravatars
FB Share
FD Feedburner Plugin
Get Recent Comments
Google XML Sitemaps
Highslide for WordPress *reloaded*
Invisible Defender
Most Commented Widget
Multi-page Toolkit
NextGEN Gallery
Ozh’ Better Feed
PadPressed
Popularity Contest
PuSHPress
Redirection
Robots Meta
Role Manager
Search Meter
Search Suggest
SEO Friendly Images
SEO Slugs
Show Top Commentators
Smart 404
Subscribe To Comments
TPC! Memory Usage
TweetMeme Retweet Button
Viper’s Video Quicktags
WordPress.com Stats
WordPress Database Backup
WP-DBManager
WP Content Filter
WP No Category Base
WP Page Numbers
WP Security Scan
Yet Another Related Posts Plugin
Yoast Breadcrumbs
All updated to the last version. Some of them we use for more than 1/2 years. No problem at all. A lot of known plugins.
Right now I’m searching for good security plugins 🙁
Thanks.
Moderator
James Huff
(@macmanx)
Volunteer Moderator
Right now we are using 43 plugins, all of it know plugins, do you know any plugin that has caused something like this?
It’s hard to tell. I can’t commit all thousand-ish plugins to memory, and sometimes the conflict can be caused by the interaction of two plugins. The only way to tell would be to fix the problem now, then deactivate all plugins for a while (maybe leave Akismet active for anti-spam purposes). Then, when you’re satisfied the problem is no longer occurring, slowly being to reactivate each plugin individually over the next month.
Right now I’m searching for good security plugins
I wouldn’t recommend trusting your security to any third-party plugin. Try some (if not all) of the recommended security measures instead.
Thread Starter
SauloB
(@saulob)
James, I opened the actual table and saw that the actual field ‘post_name’ is gone.
The field is gone. Really. Something deleted this field.
Today table:
post_password varchar(20) NOT NULL default ”,
to_ping text NOT NULL,
Before the crash:
post_password varchar(20) NOT NULL default ”,
post_name varchar(200) NOT NULL default ”,
to_ping text NOT NULL,
That’s incredible. What happened? 😮
Thread Starter
SauloB
(@saulob)
I was able to restore the old database, everything is working fine now. But I don’t know what happened.
Moderator
James Huff
(@macmanx)
Volunteer Moderator
I’m going to guess that it was probably either a plugin conflict or a malicious attack. Change all of your passwords, implement some (if not all) of the recommended security measures, and backup your files and database frequently.
Thread Starter
SauloB
(@saulob)
James thanks, most of these security tips we already have, the only left was changing the table prefix from wp_ , thaks for the tips.
Btw, I just downloaded all the scripts from all the plugins installed and checked for the word ‘post_name’ inside all the files to see if any of them could delete the field, none had any command like that.
Really don’t know now. Even it it was plugin conflict, there’s no way any of it delete the field from the wp_post table. That’s what I can conclude.