Thanks. I checked on my main website and it's working fine, it's just my test site (and 2.0 on my laptop) that isn't, so I'll look into getting those sorted.Typically this kind of thing would be down to the configuration of the server. For example, if your own server can't resolve your domain name internally to an IP address or the server can't route back in on that IP address without being blocked by a firewall.
For information for anyone else who encounters this - the problem on my test site is because it is in a password protected directory (so only I have access) and it's that the prevents the convert URL to title from working. With no directory protection, it functions as expected.
See this:What directory is that?
How do you set a password for a directory? Did not think this is possible. My site is live and everyone can access it as normal https://www.gnonline.net and all the files sit in public_html so where am I exactly looking for this password protection?
You can do that with .htaccess - copy the instructions here but apply it to the directory where the test installation is located instead: Protecting admin.php and the install directory using .htaccess
Instructions are in those resources, you need to ask questions in those discussion threads.What so you had the following in your .htaccess in you forum route directory:
<Files admin.php>
AuthType Basic
AuthName "ACP"
AuthUserFile "path/to/passwd/file"
Require valid-user
</Files>
The reason it wasn't working was in my case (and it also turns out in the duderuud's case too) that our sites were in password protected directories. So my "For information for anyone else who encounters this" post IS helpful as it clearly states what the problem was for us.Well "For information for anyone else who encounters this" is not really helpful.
What is solution for nginx for title in internal url linksI'm using Nginx anyway, not Apache, so my solution is different.
We use essential cookies to make this site work, and optional cookies to enhance your experience.