string not replaced

[richtrefz]

Shouldn't the string shown below be replaced? I put echo's around the call to recursive_unserialize_replace

---

search: /home/meicvs5/public_html/wp-content

replace: E:/TwdDevel/WSFiles/twd_wp_website/communityplugin2/www/wp-content

data_to_fix: a:8:{i:0;b:0;s:39:"peters-post-notes/peters_post_notes.php";s:13:"ppn_uninstall";s:35:"si-contact-form/si-contact-form.php";s:24:"si_contact_unset_options";s:102:"/home/meicvs5/public_html/wp-content/twd/v01/plugins/twd-admin-page-options/twd-admin-page-options.php";s:30:"twdadmin_delete_plugin_options";s:94:"/home/meicvs5/public_html/wp-content/twd/v01/plugins/twd_seller_welcome/twd_seller_welcome.php";s:32:"frswelcome_delete_plugin_options";s:49:"twd-admin-page-options/twd-admin-page-options.php";s:30:"twdadmin_delete_plugin_options";s:41:"twd_seller_welcome/twd_seller_welcome.php";s:32:"twdwelcome_delete_plugin_options";s:27:"twd-reports/twd-reports.php";s:31:"twdreport_delete_plugin_options";}

edited_data: a:8:{i:0;b:0;s:39:"peters-post-notes/peters_post_notes.php";s:13:"ppn_uninstall";s:35:"si-contact-form/si-contact-form.php";s:24:"si_contact_unset_options";s:102:"/home/meicvs5/public_html/wp-content/twd/v01/plugins/twd-admin-page-options/twd-admin-page-options.php";s:30:"twdadmin_delete_plugin_options";s:94:"/home/meicvs5/public_html/wp-content/twd/v01/plugins/twd_seller_welcome/twd_seller_welcome.php";s:32:"frswelcome_delete_plugin_options";s:49:"twd-admin-page-options/twd-admin-page-options.php";s:30:"twdadmin_delete_plugin_options";s:41:"twd_seller_welcome/twd_seller_welcome.php";s:32:"twdwelcome_delete_plugin_options";s:27:"twd-reports/twd-reports.php";s:31:"twdreport_delete_plugin_options";}

---

Completed

In the process of replacing "/home/meicvs5/public_html/wp-content" with "E:/TwdDevel/WSFiles/twd_wp_website/communityplugin2/www/wp-content" we scanned 26 tables with a total of 1599 rows, 0 cells were changed and 0 db update performed and it all took 0.645770 seconds.

[roborourke]

Looking at that it should have worked. The script hasn't been extensively tested on IIS though. I guess that's what you're using.

Can you tell me a bit about your database setup? Is it innodb, myisam, etc...

[richtrefz]

Actually, I'm running XAMPP 1.7.7 on WIndows 7. It's a plain wordpress MYSQL DB. Looks like they are all InnoDB tables. And I put those echo's around the recursive_unserialize_replace call, so I think that would isolate the issue to recursive_unserialize_replace - i.e. doesn't matter where the string came from or went to.

[user882023912867]

Probably the bug is not about the unserialize calls, actually the search and replace into serialized data is needed since some plugins developers are not useing the default ABSPATH defined in the wp-config.php instead they are using hard links into the database, if they are already doing the things bad, why we are expecting a good and well constructed serialized data? I am doing something with Regex to fix these cases

I have always problems with these plugins Memphis Custom WordPress Login, WP Sharely, XML Image Sitemap when I tried to migrate the site to a new server

I am working in a solution right now, I am using this code to test

$cornercase1=<<<END
s:338:"a:6:{s:8:\'imageurl\';s:84:\'http://ecuadorbeaches.org/wp-content/uploads/2013/04/mwpl-bgimage-20130418013758.png\';s:9:\'imagepath\';s:85:\'/home/ecuadorb/public_html/wp-content/uploads/2013/04/mwpl-bgimage-20130418013758.png\';s:5:\'width\';i:170;s:6:\'height\';i:68;s:4:\'type\';i:3;s:4:\'attr\';s:23:\'width=\'170\' height=\'68\'\';}";
END;
$cornercase2=<<<END
a:1:{s:7:"classes";a:1:{s:99:"/home/ecuadorb/public_html/wp-content/plugins/wpsharely/items/viewtables/locker-viewtable.class.php";a:2:{s:4:"name";s:21:"SocialLockerViewTable";s:7:"extends";s:17:"PFactoryViewTable";}}}
END;
$cornercase3=<<<END
O:28:"GoogleSitemapGeneratorStatus":24:{s:10:"_startTime";d:1348688574.968719005584716796875;s:8:"_endTime";i:0;s:11:"_hasChanged";b:1;s:12:"_memoryUsage";i:0;s:9:"_lastPost";i:0;s:9:"_lastTime";i:0;s:8:"_usedXml";b:1;s:11:"_xmlSuccess";b:0;s:8:"_xmlPath";s:38:"/home/ecuadorb/public_html/sitemap.xml";s:7:"_xmlUrl";s:37:"http://ecuadorbeaches.org/sitemap.xml";s:8:"_usedZip";b:1;s:11:"_zipSuccess";b:0;s:8:"_zipPath";s:41:"/home/ecuadorb/public_html/sitemap.xml.gz";s:7:"_zipUrl";s:40:"http://ecuadorbeaches.org/sitemap.xml.gz";s:11:"_usedGoogle";b:0;s:10:"_googleUrl";s:0:"";s:15:"_gooogleSuccess";b:0;s:16:"_googleStartTime";i:0;s:14:"_googleEndTime";i:0;s:8:"_usedMsn";b:0;s:7:"_msnUrl";s:0:"";s:11:"_msnSuccess";b:0;s:13:"_msnStartTime";i:0;s:11:"_msnEndTime";i:0;}
END;

echo recursive_unserialize_replace('/home/ecuadorb/public_html/','/XXXXX/',$cornercase1)."<br>\n";
echo recursive_unserialize_replace('/home/ecuadorb/public_html/','/XXXXX/',$cornercase2)."<br>\n";
echo recursive_unserialize_replace('/home/ecuadorb/public_html/','/XXXXX/',$cornercase3)."<br>\n";

the first one fail to change s:338 lenght
the second and third one fail to replace the path

[roborourke]

@ITGabs thanks for the test case. I'm going to be putting some time into search replace this week so hopefully will be able to shed some light on the problem.

You're absolutely right though plugins should only store file paths relative to ABSPATH if at all.

[roborourke]

@richtrefz there's a new version of search replace available if you want to try that, let me know if you do.

[richtrefz]

@sanchothefat I had a site I needed to move. The URL was different and the file system paths in the DB also needed to be changed. I used Search-Replace-DB-3.0.0-release.zip for this (it's labeled 3.0.0 beta on site). I didn't dig very hard looking for trouble yet but the site came up fine.

The interface is very straightforward and the Dry-Run is very nice. Those NextGen plugin guys seem dedicated to saving absolute paths in the DB - instead of paths relative to Doc Root. I work in XAMPP windows and they are putting c:/website/public_html ... which won't make the linux shared hosting happy.

I think it was a good decision to treat it as a search/replace tool (vs. a site move tool). I can imagine other uses for a good generic S&R tool - fixing some phrase in posts that was typo'ed repeatedly, ... So far so good and thanks for updating this tool.

PS: The only thing was wasn't completely obvious to me was what "update details" would do.

[matt-icit]

Satisfied user. :)