Last post 25 min ago

Posts last week 81

Average response time last week 44 min

All time posts 70349

All time tickets 10858

All time avg. posts per day 20

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.

#9675 – 4SEO on local test server using XAMPP

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, 10 March 2023 05:50 UTC

arpraka

Hi,

I liked sh404sef quite a lot, and decided to go for 4SEO after upgrading to Joomla 4 and looks great. I am trying to see if I can get 4SEO to crawl all pages when the site is hosted on a local Windows machine using XAMPP. Is this possible ?

I went through some old tickets but couldn't find one related to this. After clicking on the Analyze Now button (set speed to slow/fast - didnt matter), it finished in a couple of seconds and the Pages section is empty. All articles are marked as indexed, followed and all are in Public domain permission.

Please give me some pointers as to why pages ends up being empty.

Thanks !

Dev

Friday, 10 March 2023 07:41 UTC

wb_weeblr

I am trying to see if I can get 4SEO to crawl all pages when the site is hosted on a local Windows machine using XAMPP. Is this possible ?

Yes, like all Joomla sites or extensions, 4SEO has no idea whether it runs on windows, Mac or linux, Apache or nginx, and does note really care. 4SEO is developped on windows actually, that's the only thing I use.

If no pages are found, the most likely reasons are outlined in the Troubleshooting documentation starting from this paragraph.

Most importantly you must check that:

- the website home address is correct, something like: https://localhost/ or https://localhost:8080/ (although I have to admit using a port in the address, 8080 or such, has not been tested - by me at least)

- disable TLS certificate verification if using a self-signed one

- double-check your robots.txt

- go to the Error | Broken links and Errors | Recorded errors pages and see if your home page (http://localhost/ or similar) is not marked in error.

Best regards

Yannick Gaultier

weeblr.com / @weeblr

Monday, 10 April 2023 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.