thinkswan
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: WordPress 5.5 sitemap does not load on Nginx server@shehurin I’m not sure then, sorry.
Maybe @fierevere can help? 🤞
Forum: Fixing WordPress
In reply to: WordPress 5.5 sitemap does not load on Nginx server@shehurin Sorry to hear you’re having trouble with your WordPress sitemaps. Can you try the following:
1. Confirm the following is in your nginx config:
location / { try_files $uri $uri/ /index.php?q=$uri&$args; }2. If you modified your nginx config, restart nginx:
sudo service nginx restart
3. Deactivate all other sitemap-related plugins (Google XML Sitemaps, Yoast, etc.)
4. Confirm you have no posts or pages with awp-sitemap.xmlpermalinkAfter following those steps, does https://snakeisland.com.ua/wp-sitemap.xml work for you?
Forum: Fixing WordPress
In reply to: WordPress 5.5 sitemap does not load on Nginx serverAh, you’re right! Deactivating the Google XML Sitemaps problem solved the problem.
I removed that plugin and the custom rewrite rules and will rely on WordPress’s built-in sitemaps moving forward.
Thank you for your help, I really appreciate it!
Forum: Fixing WordPress
In reply to: WordPress 5.5 sitemap does not load on Nginx server@fierevere Appreciate your help here. I have that
location / {}directive in my Nginx config, but it doesn’t work for sitemaps.For example:
–
robots.txtloads: https://www.stressatschool.com/robots.txt
–/sitemap.xml(from Google XML Sitemaps) loads: https://www.stressatschool.com/sitemap.xml
–/wp-sitemap.xmlreturns a404 Not Found: https://www.stressatschool.com/wp-sitemap.xmlIs there an equivalent
/index.php?xml_sitemap=params=$2link for built-in WordPress sitemaps?You need to click the Administer Comments link under the commenting form and enable Anonymous Commenting in there.
What do you mean the stylesheet is deactivated? It may be a caching issue. Try clearing your browser’s cache.
It’s probably conflicting with another FB plugin. Make sure your page isn’t loading the same Facebook script (all.js) twice.
My webhost had a hiccup. It’s back up.
Upon taking a second look, I don’t think the plugin even needs to use jQuery.noConflict().
I’ll remove that line in the next version. For now, you can manually edit facebook-comments-functions.php and remove the jQuery.noConflict() line. You’ll have to replace the j’s that follow with $.
Notifications are sent to the site admin email.
If you’re not receiving them, the JavaScript is likely hitting an error due to conflicts with other Facebook-related plugins. Try disabling these to see if that’s the issue.
My only thought is that this plugin tries to use jQuery as follows: j = jQuery.noConflict();
That may be causing a jQuery conflict if your AJAX plugin uses the same variable.
It should only be slow the first time it’s loaded because it’s obtaining all of the comment counts from Facebook and caching them. After that, it should be quick.
It’ll only work if commenting is enabled by WordPress on any given page or post. You can hide the WP comments in the options.
Does your blog have a lot of posts?
The first time you activate the newer version of the plugin, it caches your comment counts, so you must be connected to the Internet to activate it. After that, you should be able to use it locally, but note that comment counts will not be updated and email notifications will not work. Custom CSS won’t work either. These all require a connection to the Facebook API.
You need to talk to your webhost and get them to enable it. cURL is a secure way to communicate with the Facebook API. I have no idea why they disabled it.