Možda i ovo dobro dođe:
Ovo treba isprobati
Ovdje fejsbukovci nešto o tome kažu
Migrating Content/Updating URLs
If you migrate your content from one URL to another, likes and shares won’t automatically migrate. You can retain like and share counts with these two steps:
1. Exempt the Facebook crawler from your HTTP redirect
Use an HTTP 301 or 302 redirect to send people to the new URL when they visit the old URL.
The crawler still needs to be able to access the old page, so exempt the crawler’s user agent from the redirect and only send an HTTP redirect to non-Facebook crawler clients.
The HTML of the old URL should still contain Open Graph tags (including an og:url tag pointing to itself) and return an HTTP 200 response when the crawler loads it.
2. Use the old page as the canonical URL for the new page
Add this tag to the HTML of the new URL:
/ meta property=”og:url” content=”https://example.com/old-url” //
This tells our crawler that the canonical URL is at the old location, and the crawler will use it to generate the number of Likes on the page. New likes at either location will aggregate in both places.
- Back up the account in question before making any changes.
- In the account’s cPanel, remove the addon domain. This will not remove the subdirectory that contains the addon domain’s site content.
- In the WebHost Manager, use Main >> Account Functions >> Modify an Account to change the domain name associated with the account in question.
- Move your site content from the addon domain’s subdirectory to the public_html directory.
- Recreate any e-mail addresses and FTP users that belong to the domain that was the addon domain.
Please keep in mind that changing your Primary Domain will have other effects on the account, which have been outlined below:
- Email – All of the email accounts created for domainA.com will turn into @domainB.com accounts. You@domainA.com will now be You@domainB.com. If you still needed You@domainA.com then you will need to add domainA.com to your CPanel again as either a parked or addon domain name and recreate the email account.
- Files – If domainB.com was an addon domain name and all of the files were located in public_html/domainB, you will need to re-upload or move the files to public_html.
- Subdomains – All of your subdomains.domainA.com will turn into subdomains.domainB.com.
- Search Engine Results impact – When you are changing the main domain on your account, be aware that you can affect the search engine rankings of the website. You can take this into account by creating 301 re-directs and also by updating the preferred domain setting in the search engine (as per Google’s article under Webmaster Tools: 301 redirects).
The migration plugin https://wordpress.org/plugins/qtranslate-to-wpml-export/ is no longer under development nor supported and it became incompatible with WPML since 220.127.116.11.
A possible workaround is:
-Install WPML 18.104.22.168
-Migrate (do it with a minimal install, just the necessary plugins and a default WP theme)
You can get older versions of WPML here:
Ovdje se mogu skinuti i stare verzije WPML: https://wpml.org/account/downloads/ – click “Changelog” to download.
you need to be in LEGACY-mode, that is <–language–> not in [language:] – zapisi sa [language:] tagovima se neće prebaciti