[wp-testers] RE: wp-testers Digest, Vol 43, Issue 7

[Kirk M]

Reading all the reply's to this problem and the fact that none of them 
have worked thus far I'm pretty much convinced that this is really a 
server side problem. I've been playing around with my local WordPress 
Sandbox trying to recreate the problem by attempting to "break" things 
through the WordPress interface, FTP, phpMyAdmin and server side root 
".htaccess" file. I can mess things up right good enough but not in the 
way you describe. You say the guy you're helping "broke it in the first 
place"? Stupid question here but does he have any idea what he was doing 
when he " broke it"?

Otherwise, let the host rebuild the entire server then (after you 
download a full DB backup of course) and see what goes after that. Now 
I'm hooked on this problem as well. I'll post here if I find out 
anything worthwhile.


Shelly wrote:
> >>What happens when you try to do that?<<
>
> Well, nothing.  The only time I receive an error is when I type - 
> either to edit a post or to create one.  That little pink 
> "Undientified error" thing comes up in the sidebar as soon as I type 
> the first letter in the body.  When I save, it just returns me to the 
> "edit post" index - all changes are lost.  (If I'm editing the 
> stylesheet, it'll return me to the index of the theme editor - all 
> changes lost.)  Same when I edit any user - it just returns me to the 
> user index - all changes lost.  no errors, nothing - it's like it just 
> redirects me back to the index of whatever section I'm working on.
>
> >>It could be that your MySQL privileges are incorrect or there's some 
> other problem with your database.<<
>
> That's also been checked.  As I said before, I tried creating three 
> entirely new databases, with new users, and installing older versions 
> of WordPress on them.  The users have all privileges to the databases 
> they are associated with.  *All* installations fail like this.   From 
> 2.0.10 up to the current 2.6.2.  The problem initially started with 
> 2.5.1 - and *how* is yet to be determined.  It was working just fine 
> for months - and I know the "and suddenly" thing sucks - because 
> usually when you say that it's your fault anyway LOL  But in this case 
> we are all scratching our heads on it.  I was working with the files 
> and content just fine one day (and it was working perfectly), left it 
> alone for a week, and came back to this.  The host has done nothing to 
> the server - no changes were made to it during the time I was away.  
> The guy I'm helping out ...well I'll just say he's not touching it 
> with a 10-foot pole (the reason I've been helping him is because he 
> broke it in the first place, and he refuses to touch *anything* until 
> I'm finished and give him instructions so he doesn't mess it up again).
>
> >>mod_security doesn't do permalinks, that's mod_rewrite.<<
>
> Ah!  thanks for that :)  (I've only had 1 cup of coffee today...LOL)
>
> >>Have you tried rebooting the server? Or short of rebooting, have you 
> tried stopping apache, then *verifying* that it was stopped?<<
>
> yes, the host did that for me yesterday.  When it didn't work, he 
> actually rebuilt Apache to see if that would fix it.  but I'll pass 
> this info you gave along to him o see if it helps him out - thanks for 
> that :)
>
> LOL I just heard back from the host - I'm so glad he's nice, some 
> people would want to be strangling me by now - and says he's on the 
> verge of rebuilding the entire server to get this to work.  But he's 
> followed up on the other suggestions given to me earlier: mod_security 
> is doing what it should, and everything has the permissions set as 
> they should be.
>
> Thanks again for sticking ith me on this.  it's a really bizarre issue.
>
> ~Shelly
>
>
>
> _______________________________________________
> wp-testers mailing list
> wp-testers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-testers
>