Opened 15 years ago
Closed 13 years ago
#110 closed defect (fixed)
the WordPress URL hack breaks pingbacks (and other XMLRPC stuff)
| Reported by: | geofft | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | autoinstallers | Keywords: | |
| Cc: |
Description
We have a hack that sets "WordPress? URL" to /~user/blog and "Blog URL" to http://user.scripts.mit.edu/blog. This seems to break pingbacks; if you set "WordPress? URL" to the full URL, and leave "Blog URL" blank so it defaults to the WordPress? URL setting, pingbacks start working.
Change History (3)
comment:1 Changed 15 years ago by mitchb
- Summary changed from the WordPress URL hack breaks pingbacks to the WordPress URL hack breaks pingbacks (and other XMLRPC stuff)
comment:2 Changed 14 years ago by xavid
- sensitive set to 0
The WordPress? autoinstaller now no longer includes the ~locker part, but still uses a path instead of a full URL, which is really the worst of both worlds. IMO it should just use the locker.scripts.mit.edu URL and be done with it.
(See http://codex.wordpress.org/Editing_wp-config.php#WordPress_address_.28URL.29)
comment:3 Changed 13 years ago by ezyang
- Resolution set to fixed
- Status changed from new to closed
Punted the hack entirely in 0a65aa9223cfd4f3cca5fec2e477942ee29601ad. Pingbacks should now work out of the box now.
Actually, we also had an issue months back where a user wanted to post via an XMLRPC app, and that didn't work due to this hack either, because the derived path to xmlrpc.php (or whatever it's called) was incorrect. We really shouldn't be putting something that's not a URL into a URL field. I know it makes scripts.mit.edu/~locker and locker.scripts.mit.edu both work at once, but we need to get WordPress? to somehow grow the ability to detect the URL it's using dynamically.