Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
Why didn’t you raise a support topic if it did not work on your site?
https://wordpress.org/support/plugin/xml-sitemap-feed/#new-post
Hi @alicewondermiscreations if you can share a link I can take a look. You might be seeing a static file that does not belong to this plugin. Compare your /sitemap.xml output with /?feed=sitemap to make sure the output is from this plugin. Or another plugin or your theme is messing with feed output (adding blank lines at the top for example) breaking valid XML. Again, I’d need to see it live to tell you more… As Jan Dembowski suggested: if you create a support thread, I can help you there further 🙂
I’ll have to enable it again, I just manually created a sitemap and decided I’m probably just going to write my own using DOMDocument.
One thing that’s possible, I do not like how much write permission WordPress like to have – e.g. I think it is highly irresponsible for WordPress to encourage blogmasters to let the webserver have write permission to .htaccess and that has caused issues before – so if this plugin needed to write somewhere outside of wp-content then that could be the cause, though I did not see any error to that effect as I have seen with other plugins that wanted to write outside that directory.
No, XML Sitemap & Google News feeds does not need any write permissions. It was specially created to NOT write any files. It creates a dynamic feed just like your /feed/ URL (but with XML markup and on different URL) so this plugin should actually fit your needs perfectly.
You can activate the plugin and you can create your own sitemap.xml file if you wish. The feed will still be available on /?feed=sitemap for testing 🙂
It seems to indicate it is not a valid feed.
https://notrackers.com/?feed=sitemap
okay with the plugin actually turned on – it’s generating gibberish.
Indeed, that does not look like it’s doing very well. Do you have any errors in the server error log? Or could you switch debugging on by add these lines temporarily to your wp-config.php ?
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
Then revisiting the sitemap might generate some meaningful messages either in the source (Ctrl+u) or in the /wp-content/debug.log file (you might need to change your dir permissions to allow file creation)
Even with debug this is the only thing showing up in the error logs:
PHP Warning: unlink(/srv/notrackers.com/wordpress/sitemap.xml): Permission denied in /srv/notrackers.com/wordpress/wp-content/plugins/xml-sitemap-feed/includes/class-xmlsitemapfeed.php on line 1679, referer: https://notrackers.com/wp-admin/plugins.php
That’s where enabling the plugin tried to nuke my manually created sitemap.xml and it isn’t related as issue existed before I created it, but I can move it if needed.
No need to move your manual sitemap.xml file, as long if it’s there, search engines will not see the broken plugin feed. In the mean time, we can continue figuring out why the plugin is failing.
So there is no error in the debug log after visiting the /?feed=sitemap location? What about the server/apache error log file? I wonder if it’s PHP 7.1 that is related there…
Your server uses PHP/7.1.14 while the plugin was tested on PHP/7.1.13 and PHP/7.2.1 … seems unlikely that that would be the cause of the issue.
What other plugins are you using?
for php –
php-common-7.1.14-1.el7_4.awel.libre.0.x86_64
php-intl-7.1.14-1.el7_4.awel.libre.0.x86_64
php-pear-1.10.5-1.el7_4.awel.libre.1.noarch
php-tidy-7.1.14-1.el7_4.awel.libre.0.x86_64
php-cli-7.1.14-1.el7_4.awel.libre.0.x86_64
php-pecl-apcu-5.1.9-1.el7_4.awel.libre.x86_64
php-json-7.1.14-1.el7_4.awel.libre.0.x86_64
php-process-7.1.14-1.el7_4.awel.libre.0.x86_64
php-pgsql-7.1.14-1.el7_4.awel.libre.0.x86_64
php-gd-7.1.14-1.el7_4.awel.libre.0.x86_64
php-xml-7.1.14-1.el7_4.awel.libre.0.x86_64
php-pecl-imagick-3.4.3-1.el7_4.awel.libre.0.x86_64
php-mysqlnd-7.1.14-1.el7_4.awel.libre.0.x86_64
php-pdo-7.1.14-1.el7_4.awel.libre.0.x86_64
php-bcmath-7.1.14-1.el7_4.awel.libre.0.x86_64
php-7.1.14-1.el7_4.awel.libre.0.x86_64
php-mbstring-7.1.14-1.el7_4.awel.libre.0.x86_64
php-pecl-libsodium-2.0.10-1.el7_4.awel.libre.x86_64
For WordPress plugins, not a lot.
Theme is gtl-multipurpose
Post Type Switcher (a feature WP really should have)
Open Graph
Disable Emojis
Contact Form 7
Plus two I wrote –
https://github.com/AliceWonderMiscreations/FlossWoff2/blob/master/wordpress/AWMFontBuilder.php
That’s just a class, installed in mu-plugins – that lets me use my own font server instead of google fonts.
https://github.com/AliceWonderMiscreations/PluggableUnplugged
That one does replace some of the wp functions in pluggable.php – such as the horrid way WP generates CSRF tokens.
Oh and I apologize for the 1 star, I was absolutely wrong to rate the plugin before asking about was going wrong.
I’ve made a mental not not negative rate for at least 48 hours in the future to give myself time to rationally think about what I’m doing.
Problem solved – zlib compression was turned on and was to blame.
I didn’t realize I had it on, I usually disable it.
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
You can edit your review with this link. Even if the topic is closed you can still edit your initial review.
https://wordpress.org/support/plugin/xml-sitemap-feed/reviews/#new-post
I’m closing this topic now, in the future please use the link I provided for support.
