#12502 closed enhancement (wontfix)
wordpress portability
| Reported by: | significance | Owned by: | significance |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | General | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
i find it really frustrating moving wordpress from server to server and to a new url.
this is mainly due to the fact that the url is hard coded in the database, requiring me to open up the sql and do a find and replace.
would it be possible to use the $SERVER globals to get the 'blog url' rather than making entries in the database with the http://blog.url/ part of the url?
that would make the process so much easier, since you could just backup/reup the database using your normal database admin tools without messing around with editing the .sql file or going through the processes described at
http://codex.wordpress.org/Moving_WordPress#Moving_WordPress_to_a_New_Server
would it be possible to make wordpress more portable? i would be happy to help design/code the feature.
Dan
Change History (6)
#3
@
16 years ago
Related forum thread:
http://wordpress.org/support/topic/371404
#4
@
15 years ago
- Keywords portability removed
It's also a GSoC project, see http://gsoc2011.wordpress.com/wordpress-move/
#5
@
12 years ago
- Milestone Future Release
- Resolution → wontfix
- Status accepted → closed
Closing this off as wontfix. The ticket is too open-ended and will sit here forever without a patch. If WordPress did consider changing how URLs are stored or referenced, it would require significant planning and discussion beforehand.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
That's a terrible idea, IMO.
Related to this ticket: #11394 [12978]