Kazam Creative
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Random $_FILES['F1l3'] CodeAnnaBell,
I fixed my hacked website by performing the following steps:
1. Changed passwords for both WordPress backend and FTP hosting account.
2. Deleted wp-includes, wp-admin and root files (except the wp-config.php)
4. Opened my wp-config.php file to make sure there was no malware code in it
3. Re-installed WordPress files/folders manually
4. Updated all plugins
5. Installed Wordfence plugin and ran a scan
6. Found files that were infected or shouldn’t be there and either had them removed by Wordfence or found the file via FTP and removed the malware from the fileFYI: I found alot of new files were strewn throughout the Uploads folder. Wordfence was great as it picked up on all these and I just deleted them via Wordfence.
The unfortunate reality is hacking is just a part of web life now. I have had a fair few websites hacked lately by the Gantengers Crew from Indonesia, who openly gloat about their hacking accomplishments.
Hope this helps you.
Forum: Fixing WordPress
In reply to: Random $_FILES['F1l3'] CodeYes I’ve dealt with many hacked sites over the years, and the methods such as the ones listed above have usually fixed them, with no recurring issues.
This one is different to what I’ve dealt with before (I’ve never seen this code also). No matter how many times I remove the malicious code, it keeps coming back a few days later.
Forum: Fixing WordPress
In reply to: Random $_FILES['F1l3'] CodeYes I managed to get it up and running again after reinstalling everything, although overnight it seems to have happened again.
I have replaced the index.php and wp-blog-header.php files again to fix it, but here is a screengrab of the problem when it happens:
https://drive.google.com/file/d/0B_DiQO5cOpWkczA0em9hSGVLcDg/viewI think this site might just be being targeted, not sure.
Forum: Fixing WordPress
In reply to: Random $_FILES['F1l3'] CodeThanks Stephen. The website was hacked despite wordpress and plugins being up to date, so I replaced all wordpress install files/folders, upgraded the theme and changed both FTP and wordpress passwords.
It seems to be just this
$_FILES['F1l3']
thing that has come back twice now after deletion.Forum: Fixing WordPress
In reply to: Random $_FILES['F1l3'] CodeI’m only looking for solutions to my initial problem, please try and stay on topic.
Forum: Fixing WordPress
In reply to: Random $_FILES['F1l3'] CodeNo not that site. It doesn’t matter what site it is, as I’ve removed the offending code already.
Besides, an outdated version of wordpress should not cause the issue as stated above.
Oh fantastic that fixed it. I did read the changelog but couldn’t see anything relating to this.
Thank you, problem resolved.
Forum: Plugins
In reply to: [Google Maps Plugin by Intergeo] Nitpicking??????
Forum: Plugins
In reply to: [AM Events] "No Upcoming Events" event though there isIt’s okay, I’m an idiot. I have another plugin besides yours that adds an “Events” option to the WordPress menu also. I was adding events to the other one!
Apologies Atte, your plugin gets 5 stars!
Forum: Plugins
In reply to: [Strong Testimonials] Settings BugThanks Chris, perfect answers. I will continue using your plugin as the scroll effect was only a “want” rather than a “need”.
(a) find a more suitable jQuery content slider plugin, or (b) customize Cycle to work better
I’ve used FlexSlider in a few projects, might be a possible solution? It has both the “fade” and “slide” options that seem to work well.
Looking forward to the updates.
My temporary solution (which has worked for me) until Photocrati release their performance improved version is to revert back to a previous version of NextGen.
I changed my version of NextGen back to v1.9.13 and this solved my slow website issue.
Thank you Photocrati for addressing the issue and I look forward to the fix.
Thank you for your prompt reply photocrati,
I always optimise clients images and resize them to 800x600px prior to importing into NextGEN, so I knew that couldn’t be the issue.
I’ve temporarily resolved the issue by reverting back to an older version of NextGEN (runs like a dream again), and will wait for this problem to be fixed in a later version.
Thanks again.