Last post 10 hours 33 min ago

Posts last week 141

Average response time last week 4 hours 42 min

All time posts 67805

All time tickets 10478

All time avg. posts per day 21

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.

Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!

All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#8849 – troubleshooting 4seo on Joomla IIS.

Posted in ‘4SEO’

This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Friday, 17 June 2022 02:29 UTC

heinrich-zepter-pelicancorp-com

I am looking at the instructions for trobleshooting noted here

https://weeblr.com/doc/products.forseo/current/troubleshooting/#trying-to-read-sitemap-triggers-a-404-error

The issue is that I am running IIS, and not apache. My understanding is that htAccess is not actually relevant for this and that this should be done via web.config.

What would the documentation for IIS look like?

Friday, 17 June 2022 07:11 UTC

wb_weeblr

We do not support IIS (because I know nothing about it and don't have machines to run it on). I do know that the web.config file is the equivalent of .haccess (Joomla comes with one).

First thing to know is what the problem is. What happens? what do you see on the screen? depending on the type of error, we can determine if the problem is in the webserver, or elsewhere. If at webserver level, I'm sure we can find or ask for a proper configuration.

Please absolutely always provide a full and real URL to the site where we can see the problem.

Best regards

Yannick Gaultier

weeblr.com / @weeblr

Monday, 18 July 2022 05:34 UTC

system

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.