[email protected]

ntm,

Do you have any further insights on this? It seems I’m having an almost identical issue as cranky_wheeler. I moved the location of my mp3s from “olddomain.com/tracks” to “newdomain.tv/wordpress/wp-content/uploads/audio” and am experiencing some issues in getting podpress to recognize the new URIs in the database.

First, I managed to export the wp_postmeta table from my old blog’s database. The _podPressMedia entries in it contained absolute paths to the .mp3s at “olddomain.com/tracks” in their meta_value.

I then imported this table into my new blog’s database. All the IDs correspond, and as expected, all blog posts featuring podpress display their mp3(s) embedded inline within the content area. However, the location of the mp3 files still reside at olddomain.

To address this, I used a search and replace WordPress plugin on the new blog to find all instances of “olddomain.com/tracks” in the database and replace with “newdomain.tv/wordpress/wp-content/uploads/audio/”

Upon completing that final step, all blog posts featuring podpress no longer display the embedded mp3s within their content area. Further, when I login and inspect the podpress settings for a specific post, the fields are all blank, where they were previously filled out with track info, file location, etc.

When I revert the wp_postmeta table back to its original state (so that file URIs point to olddomain again), and refresh.. the blog posts return back to normal and properly display their embedded mp3s.

There has to be something I’m missing. I can’t imagine why simply changing the URI from one location to another in the database would cause the mp3s to drop away from the posts they’re associated with entirely.

As a test, much like cranky_wheeler I also tried manually changing the location of an mp3 from olddomain to newdomain for just one post via the wysiwyg (as opposed to bulk find / replacement in the database). That method seemed to work fine, but is obviously not ideal. In fact, once I did that, I went back and inspected the database and the meta_value for that modified entry is formatted identically to the old ones. The only difference is the URI.

If you could provide any clarity, assistance or recommendations in resolving this, I would greatly appreciate it.

Victor