Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Detailed instructions to migrate Slugs from legacy #1404

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Detailed instructions to migrate Slugs from legacy #1404

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 11 additions & 5 deletions src/modules/slugs/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,12 +17,18 @@ If you want to translate also the base permastructs (ex. *category*, *tag*, etc)
- Set the base permastructs for **post types** and **taxonomies** (If you setup a base permastruct for *categories* or *tags* in *Settings/Permalinks*, these will be overwritten by the translated ones).
- Save settings and that's all!

### I've been using the QTS plugin, how can I find the existing slugs?
Enable the *Slugs* module, go in the "Import" settings of qTranslate and import QTS data.
The dry-run mode allows to test the import and see the number of rows changed before updating the database.
### How can I migrate from the legacy QTS plugin to the new module?
If you are migrating from using *qTranslate X* and the *qtranslate-slug* (QTS) plugin, migration should work with this sequence:

**Attention!** Do not uninstall QTS before migrating data to qTranslate, it deletes data permanently.
Once the migration is done, the data is not be visible in QTS anymore and the QTS plugin can be uninstalled.
1. Make sure that you are on **latest version of the legacy plugin**
2. **Deactivate the legacy plugin**
3. **Activate the *Slugs* module**
4. **Migrate** using `Migrate QTS slugs` in *QTX Settings > Import/Export*. The dry-run mode allows to test the import and see the number of rows changed before updating the database.
5. **Delete the legacy plugin**

If you are using functions from the legacy plugin in your theme files, you may want to switch to a neutral theme.

**Attention!** Do not uninstall QTS before migrating data to qTranslate, it deletes data permanently. Once the migration is done, the data is not be visible in QTS anymore and the QTS plugin can be uninstalled.

### I get a 404 error, what can I do?
In the admin go to *Settings/Permalinks* or *Settings/Languages* (qTranslate) options and save.
Expand Down