salescart

Tara, that is just pushing it off to the hosting provider. We ARE the hosting provider. There is no one to push it off to you.

If you could please direct me to the WordPress documentation of what the IIS (and Windows NTFS) file permissions “should be”, than I can make it so. All the documentation I can find is “UNIX/Linux” centric.

We could certainly can get by with manual installation but I would like to solve the actual problem.

Confusing product naming, distribution/purchase path, and slow support that takes days and days to answer…assuming the person can find it. We eventually got it working after nearly a week. Unfortunately a previous designer used your tool so we were stuck with it or we would have jettisoned it.

Yes, we did post in your support forum….it took us two days to be able to post there because of the steps and hoops you make your customers jump through before they can even make a post. It is VERY confusing which product to buy, how to get support.

We can’t get support there and can’t log-in. It’s a mess. This is just a warning for would be buyers. Avoid this software at all costs. The support is terrible with a 2 day turnaround promised even after you pay. We tried registering but never get any email.

We had to delete the plugin files via FTP, and then reload the plugin. That was the only way around it.

Ok, I give up and reverted back to the previous version. What a mess this version is. Most of what you think are improvements are actually a step in the wrong direction.

And it will probably get as much attention as this thread that you closed. I contacted them and they said unless you got $$$’s, they don’t help you. It appears to be easier to switch to a different plugin.

No, I’m not using any cache plugin and I’ve also disabled all plugins and the problem is not solved in any case. Yes, I have already resaved the permalinks and yes that is where the problem is. Now, I am wordpress on windows and perhaps it was not properly tested in that environment.

This is the what the xml file has for the .xsl xml stylesheet.

‘type=”text/xsl” href=”//www.web-hosters.com/main-sitemap.xsl”?>’

However, the stylesheet is REALLY at //www.web-hosters.com/index.php/main-sitemap.xsl

Its just a plain old bug from my viewpoint. It is not properly taking into account the permalinks and it seems to have somekind of “hardwired” idea of what the permalinks/pathing is. Resetting my permalinks doesn’t fix the problem.

These are my permalinks with the index.php in there.
https://www.web-hosters.com/index.php/sample-post/

Thanks…Yeh, I ended up finding that but it had no effect.

How did you increase memory?

The conflicting WordPress plugin you have is the Yoast SEO XML coding. If you do a Google search for “Yoast SEO sitemap not working”, you’ll get 21,000 entries. What is your URL to the sitemap?

Also Niles, that is a “terribly” written KB that explains lots of problems and gives you few good ways to solve the problems. I completely agree with YvonneTaylor.

YvonneTaylor we can’t get our Yoast XMLsitemap to work either. What we are going to do is turn that off. There are lots of other WordPress plugin that do sitemaps and they just work….not special hoops to jump through.

Pretty typical. Google takes weeks and sometimes months before it will take a look at your sitemap. They are backed up cataloging the world. Just be patient. Pending means Google knows about it, and its’ in the stack to be cataloged.

The yoast SEO plugin feels like it can take over your entire wordpress website and is very buggy….we can’t get it to work either and we’re looking at alternatives. However, I can see your sitemap at https://happybirthdayimagesquotes.com/sitemap.xml

Take a look at it…does it look right?
It looks right to me. If so, then those warnings are just more bugs and can be ignored as just nag messages…annoying but not destructive.

Thanks…yep. It did it.

On Windows, there is the IUSR account which represents the “web browser” essentially. In my case, this website is not yet visible to the public so the IUSR permissions did not exist. I’m not sure exactly what permissions you need to give the ISUR account since we gave it Change/modify permission and then removed it again afterwards. However, I’m guessing you need to give the IUSR account at least RX (Read Execute) permissions. That was the original purpose of my thread as I’m unsure of exactly “where” or “what” the “correct” NT file permissions are documented for Windows machines.