wpsecuritylock
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Malware inserted into index.phpHave you checked your server for any mystery files? By that I mean a file that does not come with WordPress core, plugins or your theme.
There could be a trigger file hidden in a folder somewhere that you missed.
Sometimes the hack files are named something you may miss, like wp-pages.php, which is not part of WordPress.
Log-in with Filezilla and check the last modified dates after you re-upload your files and search for any modified previously.
And clean up your server by getting rid of any obsolete WordPress files. You should only have what’s current on your server.
Hope that helps.
Forum: Plugins
In reply to: [Akismet Anti-spam: Spam Protection] akismet/readme.txtbamajr,
I can see where it can be a bit confusing about the compatibility of plugins.
The Askimet readme.txt shows it’s been tested up to 3.1
The plugin page shows it’s compatible up to 3.1.4.Maybe the developers update the Compatible up to version to let us know what they know for sure it works on, without going through the process of updating just the readme.txt file and doing a new version number just for that change, which would alert all of us there’s an update.
Think about how much work that would be to keep changing the readme.txt file for every plugin of what version it’s been tested on and then doing a new version for that simple change. It’s best to wait until they’ve improve or fixed something in an update.
The plugin repository is a great place to find out information about our plugins. We can view requirements, compatible up to, last updated, Changelog, and also see votes from other users.
For me, I hop to the Last Updated section, if it’s really old I consider finding a replacement. Then I jump down to the Compatibility Votes for my current version and see works vs. broken.
If I find that a plugin is voted as broken, I click on the “Forum Posts” link on the page and find out why it was reported as broken. Sometimes, it’s an end-user issue and not the plugin itself.
You can also help out by participating in voting. The more votes, the more each of us know if a plugin works.
Hope that helps.
Forum: Plugins
In reply to: [WPaudio MP3 Player] No MP3 Play Button, Just a Link!Thanks Ursula! You rock!
Forum: Plugins
In reply to: [W3 Total Cache] Changed to IIS7 and can't activate W3TCGlad you got it fixed. Be careful with chmod 777. You don’t want to leave anything open.
Forum: Plugins
In reply to: [WPaudio MP3 Player] No MP3 Play Button, Just a Link!Looks like the plugin needs some TLC and an update.
Forum: Plugins
In reply to: [Audio Player] Notice: has_cap called with an argument that is deprecatedNo, I did not have any other plugin active.
Forum: Plugins
In reply to: [Limit Login Attempts] [Plugin: Limit Login Attempts] Can you unblock an IP?Thanks for letting me know.
Forum: Plugins
In reply to: [AntiVirus] Are you sure you want to do this? ErrorWould be nice for an update on this plugin.
The plugin was part of the original new installation of WP 3.1.3. So no I did not delete it and upload a fresh copy of Akismet only.
Thanks for looking into this Trey. Hopefully a new version will be out soon so.
Thanks for letting us know and taking care of this for us. I look forward to the updated version.
FYI: This is with Debug True.
Forum: Plugins
In reply to: [WPaudio MP3 Player] No MP3 Play Button, Just a Link!I removed the . (dot) per your instructions and the audio player still did not work.
After some plugin deactivation’s, I found that the FancyBox for WordPress plugin (version 2.7.5) was causing the WPAudio player not to load on posts/pages.
It works now on WP 3.1.2.
Forum: Plugins
In reply to: [AdRotate Banner Manager] [Plugin: AdRotate] Plugin Having An Issue With 3.1I just installed adrotate 3.4 on a fresh install of WordPress 3.1.
The only plugin that is activated on this site besides adrotate is WishList Member.
Upon activation, I received the following error:
The plugin generated 732 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.
After deactivate then reactivation the error went away.
Any ideas what could be causing this?
I just got the same error too. Any news on how to fix this?