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.

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

Screenshots showing backend UI and frontend result? #38

Open
paaljoachim opened this issue Feb 6, 2014 · 2 comments
Open

Screenshots showing backend UI and frontend result? #38

paaljoachim opened this issue Feb 6, 2014 · 2 comments
Assignees
Labels

Comments

@paaljoachim
Copy link

Hey

I noticed your post on LinkedIn regarding "Best plugin for multilingual sites?"

I came here to check out your plugin but am missing seeing screenshots.

@nikolov-tmw
Copy link
Owner

Hi,

Well I don't have a lot of screenshots from the back-end unfortunately. Here's one from the post edit screen - http://themoonwatch.com/wp-content/uploads/2013/03/mlwp-post-edit.jpg

As you can see it just adds buttons at the top that allow you to switch between languages.

The settings UI currently uses tabs on top and has sections for General Settings:

  • Default language(dropdown)
  • Enabled languages(checkboxes)
  • Default Flag size(my plugin comes with a set of very pretty country flags in 5 sizes - from 16 to 64 px in width)
  • Enabled Post types
  • Enabled taxonomies
  • Empty translation action(whether to display the default language content, or display the "no translation" message for the language)
  • Whether the extra UI for the translation post types should be displayed or not - since every language adds a "clone" of every enabled post type, you can select to have the UI for those post types to be accessible. It's basically the "show_ui" parameter of register_post_type()
  • Rewrite mode - currently can be "Query arg", "Pre-path" or "Sub-domain"
  • Whether to display the default language in the URL or not.

Language Settings - this allows you to manage the currently registered languages(there's a separate page for adding a new language).

Rewrite Settings - this tab allows you to modify various rewrite slugs:

  • Post Types Slugs - here you can change the slugs for each language for all of the enabled post types(except pages and posts and any post type that doesn't actually have rewrites enabled) - this way you can have your "products" URL translated in all of your languages
  • Taxonomies Slugs - just like the post types slugs allows you to have each taxonomy's slug different for each language
  • Search Slugs - even though not really used in core by default, you can view search results at /search/?s=s - it allows you to change that slug for each language.
  • Page Slugs - slugs for paginated results(like /page/2/)
  • Feed slugs - slugs for feeds - like /category/uncategorized/feed/)
  • Author slugs - slugs for the author archives - like /author/admin/
  • Attachment slugs - slugs for attachment pages
  • Date slugs - not really sure where those are used, but I saw them in core, so I decided to support them as well 😄

In addition to those tabs, you have 4 extra pages: Add New Language, Remove a Language, Fix Posts(this is used after changing the default language, after enabling/disabling a language, etc) and Credits(still empty, but I'll get to it at some point).

I might have time to put up a few screenshots, but I can't promise anything at the moment 😦

@nikolov-tmw
Copy link
Owner

I forgot about the front-end.

Well - there isn't much on the front end to be seen - you can add a widget that displays a language selector - either just language name, language flag or combined.
Also you get a "Languages" menu in your toolbar - on the front-end it acts the same way the widget would, but on the back-end it stores your preferred language in a user meta. This way your dashboard will always be in the language that you prefer.

I've also made it rather easy to implement your own language selector if you have some knowledge of PHP. You can do that either by passing various options that specify the HTML tags that will be used to create the selector, or by passing an option that returns an associative array of languages and the information about them.

@nikolov-tmw nikolov-tmw self-assigned this Feb 6, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants