Problem with port number in domain name
-
I have multisite wp running under IIS 8. The site is on an internal url for security reasons: https://localhost:8100. I am using subdirectories for sites.
When I create a new site it correctly shows localhost:8100/_________ allowing me to enter the subdirectory name but after saving it and returning to sites it shows
localhost8100/<site folder> instead of localhost:8100/<sitefolder> which of course results in a 404 when I try to access the site or its dashboard.If I edit the site, the site url on info tab and site url and home on settings tab all show http:localhost8100/<site folder> If I insert the colon and do save changes then the port disappears alltogether and I get https://localhost/<site folder>
-
Currently it is not possible to use WordPress Multisite with other ports rather then 80 or 443.
There’s a ticket recently opened in the Trac suggesting WordPress Developers to make this feature available for the new versions to come:
https://core.trac.www.ads-software.com/ticket/42993There are a couple of forums teaching how to work this around by changing the core (the user also says it in the ticket bellow), but hacking the core is not indicated.
- The topic ‘Problem with port number in domain name’ is closed to new replies.