www.domain.com
. Let's suppose that we want to migrate this to Frontity in Decoupled Mode. We will need to make the following changes:www.domain.com
will point to the Frontity serverwp.domain.com
will point to the WordPress serverwp.domain.com
will still point to www.domain.com
. However, if any content is added after the change then internal links will point to wp.domain.com
. This creates a situation where internal links in the content are inconsistent, with "old" links pointing to www.domain.com
and "new" links pointing to wp.domain.com
.Settings
to determine where the internal links should point to.wp.domain.com
) to convert links to a <Link />
component. So if the internal links are left pointing to www.domain.com
the link processor won't work on those links because it will only convert links pointing to wp.domain.com
, i.e. the URL of the WordPress data source.WordPress Address
and the Site Address
in the "Settings" page of the WordPress admin so they point to new URL (e.g. wp.domain.com
).wp.domain.com
). This can be done in 2 ways:phpMyAdmin
or an application such as Sequel Pro or Sequel Ace.