hector-santos

Hi,

Yes, I tried as much as I understood it as a first timer and how it related to our web server. But I believe our WebServer script mapping logic in regards to supportinh the unix style pathinfo and what wp calls “ugly urls” is based on having the script part of the url per the CGI specifications for defining the environment strings:

PATH_INFO
PATH_TRANSLATED

and how PHP itself has a history with this and PHP_SELF. Last year, I spent quite an effort in getting this right for legacy PHP applications relying on PHP_SELF. I don’t recall all the details. Overall, we don’t require operators to do any “rewriting” stuff for script maps.

Fortunately, I was able to solve it using an alias redirection.

alias: wordpress/
url: index.php

This seem to resolve the links now in this WP setup. I’m still going to open a ticket to reexplore this againf, but without the actual script in the URL, the web server can only use the referer to make some automatic guess at the script map to use.

I think if there anything learn that might help the word press package for first timers, maybe add to the “5 Minute Install” outline

5.1 Per your web server implementation, add your Rewrite or Direction for the blog folder to point to the index.php file before running the install.php.

I believe that might resolve the initial Step=2 installation part or maybe not. ??

Thanks

I believe I am closer to resolving this, at least understanding what the problem is. Permanlinks and “Ugly Urls”

WordPress was installed to run the Wildcat! Web Server (https://www.santronics.com).

I am the chief developer so I can address this. I think once upon a time, the original programmer supported “ugly urls” directly where a url with

/?name=values

would use the referer for the script. I have to double check, but I know in recent urls this might have been changed to an incorrect url syntax since I followed the HTTP specs, it is technically an incorrect url. I have to now reopen this and see what are the issues, if any.

But I just wish to ask for a confirmation if this is the overall problem?

It might be easier if I edited the PHP files because I don’t understand why it must use this format. I tried the other formats but without having the index.php part in the url, it fails.

thanks