robguyy

Just who at WordPress wants to cram blocks down our throats? It’s getting more and more difficult to follow vague redesign concepts. You can defend it; I can’t.

in my case, the fix was to get rid of every .htaccess file, which includes the wp-admin and wp-includes folders. Just renaming them to something like “.htaccess.txt” or “htaccess.txt” are unacceptable. Just delete them.

Sadly, what this means is that it doesn’t appear to be possible to use any .htaccess files we have traditionally used to protect folder access from hackers within the WordPress tree structure on your server. The ONLY htaccess file that appears acceptable is at the root of the WordPress install.

Even so, you may have to change the preferred presentation of permalinks in that .htaccss file at the installation root to keep it from choking your server. You can see what works by looking for “core” files via FTP. An example of a name for such file is: core.12345. These “core” files, if left undeleted, will chew up some serious server space. “Core” files are also accompanied by “error_log.” Delete those, too. (Either that, or contact your server people. It just depends on your level of knowledge.)

Note, too that .htaccess files located in places other than the installation root will also throw off your themes – including WordPress themes 2010 and 2011.

One final note: As www.ads-software.com says, before doing any update/upgrade, do these things FIRST: Back up your database and deactivate ALL plug-ins. Only then should you update/upgrade. You don’t have to, but I also backup my home directory using CPanel.

Couldn’t get it to work on two of my sites; thanks, anyway.

Both sites are still working; but although WordPress “sees” me log in, I get 404 errors when i click on any of the admin links. It appears wordpress no longer wants to go to wp-admin anything.

This is on top of WordPress 3.4.1’s antics, which destroyed the display area for the navigation menu in all of my themes – and in all WordPress themes – and I lost my WSIWYG editor. To mitigate the problem on a third site, I just converted it to Drupal 7. The two sites that had survived 3.4.1’s coding changes have now died, for this administrator, with 3.4.2. The admin bar has been lost and also all access to wp-admin.

Guess I’m alone in my opinion that the last 2 versions weren’t ready for prime time.

It’s the readme.txt. If you read it, you’ll see it.

It’s obvious you didn’t read the post. There is no reason to leave security behind to push out a plug in. You’d also see from my post that I did find a link.

Don’t you think WordPress should be more receptive to a report of a security issue, rather than take a postion of, “My shoes don’t stink?”.

Let me help support by giving the link that could have been sent offline. Here is the link that is still a link to malware, and will be malware until Google quits intercepting people trying to go there.

[ Moderated. Thanks for disclosing that responsibly. ]

I think I’m done with trying to talk to deaf people.

OK; it’s late, and my English stinks at this hour:

All other plug-ins, including The Broken RSS Feed Fixer, are OK to use. The feed fixer has now been retired (deactivated).

Good night.

The plug-in was the flv-gallery plug-in; I was going to notify the author, but see the “visit plug-in site” goes to a church. Hmmm.

All other plug-ins, including The Broken RSS Feed Fixer (which will remain INACTIVE now). Bottom line: All WordPress feeds will be the preferred feeds, and FeedBurner now points to https://citrustimes.com/feed – and that feed is now valid.

Thanks for your help; I never suspected a NON rss plug-in like flv-gallery would be a problem … but there you go. Thanks again.

Akismet, Blog Protector, Clean-Contact, Event Calendar, FeedCache, Flexi Pages Widget, FLV Gallery, Generate Post Thumbnails, Google Analytics, Google News, Optimize DB, Page Links To, PHP Execution, Platinum SEO Pack, Regenerate Thumbnails, SimplePie Core, SimplePie Plugin for WordPress, Viva Zoom, WordPress Admin Bar, WP RSS Images, Zap_Recent_Commented

Didn’t work for me. Re-uploading wp-admin and wp-includes was a bust. I can use the html tab, but as soon as I shift to visual editor, that html code is stripped out except for code related to graphics.

So, guess I’ll stick with the html post entry method.

I temporarily solved the menu.php problem by renaming the 2.8 “menu.php” to “wp_suspect.menu”, then copying the 2.7.1 “menu.php”into that wp-admin folder.

Problem solved. No more error, and WP Admin Bar worked as usual. When WP-admin update came out, I restored the 2.8 menu.php, and all is well.

The only problem I had was that the upgrade failed to completely install using “upgrade automatically.” It had a problem copying one of the files. Sorry, but I forgot the file name. My solution was to install manually. All went well using manual install.