Why can't I see new links after replacing their old one?

Friends encountered such a thing, there is the Live Composer plugin with it very quickly and beautifully typeset and drawn as the template and the content of the site. But here's the problem after transferring a site from a local server (OpenServer) to hosting, the old links that were used when working with the plug-in does not change to the new despite the fact that have been replaced wherever possible (database, template files and the whole site in General).
Where to dig?
July 8th 19 at 15:45
1 answer
July 8th 19 at 15:47
Solution
Copy the same instruction to all who asks the same thing - "how to solve the problem of WordPress after manual migration":

In the modern world of WordPress do:
https://wordpress.org/plugins/duplicator/ - put plug.
Go to it, click the "Create package". Further, further, further.
Get installer.php and archive. Fill them to the new hosting (domain, folder - does not matter). Run site.com/installer.php. Enter new login and password from the database.
Further, further, further.
At the end do the instructions on the screen - log in VP, Peresechenie permalinks. Deleted files of the installer and archive.
All. All migrated. Any problems with paths etc.
That is a duplicator and was moved to the site, and the problem remained. And I have just not wise, and th Akkebo'also tried. Still references old not in database not in files NO. But on frontend there is. Something like Rum. - Hertha17 commented on July 8th 19 at 15:50
: Duplicator after this process is finished Warning writes in the log something? Probably there are Serialization Errors. This is when the theme or plugin stores data like this:

a:4:{s:5:"child";a:1:{s:0:"";a:1:{s:3:"rss";a:1:{i:0;a:6:{s:4:"data";s:3:"
";s:7:"attribs";a:1:{s:0:"";a:1:{s:7:"version";s:3:"2.0";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:1:{s:7:"channel";a:1:{i:0;a:6:{s:4:"data";s:49:"
......

If there are errors - there in the duplicator log will be written - which rows in the database need to change manually. And the machine does not change, because there are links for example can be stored not in this form: http;//server.com/bblabla... but shielded: http:\/\/server.com\/blablabla\/ and so on - keagan_Hartmann commented on July 8th 19 at 15:53
In General, this problem is not WordPress and not the server, but the plugin designer. Are you still writing it read - there will probably be a description of the problem (if the plugin is popular) - keagan_Hartmann commented on July 8th 19 at 15:56
: Thanks I will dig in this direction. - Hertha17 commented on July 8th 19 at 15:59
Hmm... In the database found one favorite link storage is in a familiar form. But it still appears with the old domain. The brain begins to explode. - Hertha17 commented on July 8th 19 at 16:02
WELL displayed on frontend - Hertha17 commented on July 8th 19 at 16:05
: after the edits the references in the database - don't forget to resave permalinks in the admin area of WordPress. - keagan_Hartmann commented on July 8th 19 at 16:08
Thank you. You can read more? - Hertha17 commented on July 8th 19 at 16:11
: VP admin - Settings - Permalinks and just click "Save". Therefore, overwrite rules, redirects, links, etc. - keagan_Hartmann commented on July 8th 19 at 16:14
UKTI )) ATP - Hertha17 commented on July 8th 19 at 16:17

Find more questions by tags WordPress