Kef Schecter
Forum Replies Created
-
Forum: Plugins
In reply to: [XML Sitemap Generator for Google] Blank line generated before XML headerProblem solved. Something in our functions.php file was emitting a blank line.
Forum: Plugins
In reply to: [XML Sitemap Generator for Google] Google XML Sitemap vs. Yoast XML ?Bliss7, I wouldn’t say “no one does it better than Arne Brachold” when this support forum is flooded with issues and very few answers. Maybe that wasn’t the case when you posted that message, but it certainly is now.
Forum: Plugins
In reply to: [XML Sitemap Generator for Google] one of my sitemap has some bugsPlease do not just say “issue is resolved” without posting your solution, in case somebody else is experiencing the same or a similar problem.
Forum: Plugins
In reply to: [XML Sitemap Generator for Google] Where is sitemap located?I imagine the sitemap.xml file is being generated on-the-fly by the WordPress plugin. I don’t think there’s anything wrong with that.
pesiunwalla: you will know if Google can see it if the file is listed in your site’s robots.txt file and the given URL for the sitemap works in your web browser.
Forum: Fixing WordPress
In reply to: link-template.php.suspected?It seems this .suspected thing is connected with some kind of hacking, because being hacked was the reason I’d upgraded WordPress to 4.2.2 in the first place. The link-template.php file itself is not being compromised, though; it’s the same file that WordPress itself installed.
Forum: Fixing WordPress
In reply to: Fatal Error on wp-settings and links-template?I think you should probably just do a full system reinstall. That’s what I’m going to do with our sites. It’s a severe pain, but it’s the only way to be sure you don’t have a rootkit or any other nasty stuff. Hopefully the issue with the file being renamed will go away in the process.
Forum: Fixing WordPress
In reply to: Fatal Error on wp-settings and links-template?I’m having this issue as well. Our site got hacked recently (which was why we upgraded to 4.2.2) and I wonder if this is in some way related. I know the link-template.php file was not compromised at the time it was renamed, though; its timestamp indicated it had been replaced during the upgrade and not touched since then.
I asked our host (Bluehost) if they were running any malware scans or if CentOS came with such a scan, but they said they weren’t aware of any such thing. I did find afterwards there was another security hole (an FTP account) the hackers left behind, so it’s possible a hacker logged in and did something to trigger this behavior.
Or it could be entirely unrelated. In any case, it’d be a good idea to make sure your WordPress installation hasn’t been hacked. Be sure there are no strange files or strange bits of code in your theme files; that’s apparently a popular place to put in exploits.
Forum: Fixing WordPress
In reply to: link-template.php.suspected?https://ww.wp.xz.cn/support/topic/fatal-error-on-wp-settings-and-links-template — apparently this is a duplicate of this issue. I suppose further discussion should take place there.
Forum: Fixing WordPress
In reply to: link-template.php.suspectedForum: Fixing WordPress
In reply to: link-template.php.suspected?I am getting this problem too. I do not think wp-settings.php is being altered. What’s happening is something — probably outside of WordPress — is detecting link-template.php and renaming it to link-template.php.suspected. It’s likely some kind of false positive from a scanner looking for compromised files and such.
I have not yet found what is causing this to happen, but in the meantime I suggest contacting your webhost. They will probably know what’s doing the renaming.