I'm using LinguaPlone in a site thas is written in English and Spanish. All site pages and folders can be translated, except the front page folder. I think that I can translate the page that the front page folder uses as view, but in that case when a user goes to front page, only the folder view is showed (not its translation).
I'm using Plone 4.1.4 and LinguaPlone 4.1.2. Maybe I need to try with other tool, as raptus.multilingualplone.
Normally, when setting up a LinguaPlone site you let LinguaPlone create top-level per-language folders that act as navigation roots. The root of the site itself is set up to redirect visitors to one of these roots depending on their language preferences and other factors, using a language selector.
Take a look at http://www.norden.org/ for an example of such a site. Notice that when you visit that URL you are automatically redirected to one of the supported languages, usually to http://www.norden.org/en/ for english. You can switch between the available languages on the top left, and you'll see that the first element of the URL changes between the language codes. Those are the top-level folders.
The advantage here is that each of these folders can have it's own default view. Another is that URLs are always crystal clear for visitors; switch from "About this website" (http://www.norden.org/en/about-this-website) to the Norwegian translation and you end up on on http://www.norden.org/no/om-nettstedet; anyone can see that the new URL is in the Norwegian language even if they do not understand that language.
You can set up these language folders after the fact, as documented in the LinguaPlone installation instructions; simply visit the URL:
http://localhost:8080/Plone/##language-setup-folders
but be sure to backup your site first and to adjust the address for your local situation.
Related
I am developing a CMS based on wordpress multi-site approach. So far i have 5 languages and i have created a site for each language.
Idea is when a user go to
www.mydomian.com/uk - displays English version.
www.mydomian.com/es - displays Spanish version.
www.mydomian.com/fr - displays French version.
Now I have reached localisation of my theme. As mentioned in theme developer handbook, i am aware of theme localisation functions and other options in wordpress. But i am confused, how would I inform my theme to load translations based on site which user is selected. for eg. if user is browsing www.mydomian.com/es theme should load all spanish translations.
Please let us know the best options for this.
Every site you add in WordPress multi-site has its own "Site Language" setting, so you don't need to set the locale from your URL pattern. The correct theme translations will be loaded automatically for each site just based on its settings.
If you didn't set the language when you added each site then go into each site's settings and change the field labelled "WPLANG" to "es_ES" and "fr_FR" respectively.
The site settings are found under My Sites > Network Admin > Sites then click edit under the site you want, and then select the "Settings" tab.
Or jump to: wp-admin/network/site-settings.php?id=<siteId> if you know the site ID number.
The site settings screen for multi-site isn't as user friendly as the standalone settings page. There is no dropdown menu for the available languages, so be sure to enter the locale code correctly.
It doesn't matter what you've chosen as your multi-site subdirectory or subdomain patterns just note that the codes you're using in your example are not the official WordPress locale codes.
Spanish is es_ES (not es)
French is fr_FR (not fr):
British English is en_GB (not uk)
Environment: Plone 4.3.4.1 , plone.app.multilingual 2.0.0 (from github)
I have two Plone sites, both with p.a.m enabled, but they behavior differently when visiting to their site root URL. Say, visit http://www.site1.com/ will redirect to http://www.site1.com/zh , that is what I need. But http://www.site2.com/ will show its item listing, that I want it redirect to http://www.site2.com/zh. See the below picture for reference.
How do I enable the auto-redirection to one of its Language Root Folder? Hints are appreciated.
Edit After the Comment and Answer:
Ulrich and Mathias are right for the hints. Here are some more details. First, when I select "Chinese" as my default site language, there is no "Root language switcher" under "Display" menu.
When I select "English" as my default site language, then I can see and select "Root language switcher" under "Display" menu. Everything works as expected.
It's like Ulrich mentioned, you can define the language-switcher View as default view on the plone root. This automatically redirects you to the desired language folder.
More Infos: https://github.com/plone/plone.app.multilingual/blob/2.x/src/plone/app/multilingual/browser/switcher.py
If you setup the a multilingual site, the default page of the plone root should be configured correctly: Check LanguageSetup: https://github.com/plone/plone.app.multilingual/blob/2.x/src/plone/app/multilingual/browser/setup.py#L245
I have a set of custom html pages that are not made with WordPress in folder DIR
In the WordPress blog I have a web page called SPECIAL that only some users can access (after being authenticated). I would like to know if there is a way to allow those users to open the web pages in DIR (in a comfortable way)
For now i am using a very non-pratical solution:
I make a zip archive of that folder, upload it from the Admin interface of WordPress, using WP-Filebase, and put a link to the DIR.zip in the web page SPECIAL.
Yes I agree that my solution is ridiculous. Please help me find a better one.
Thanks in advance.
One solution would be to link to the pages contained within the DIR folder on the SPECIAL page itself, or create an additional WordPress-based page, linked to from SPECIAL, that performs the same function as your DIR/index.html page.
Alternatively you could place an iframe of DIR/index.html on your SPECIAL page.
A longer term solution would be to migrate the contents of DIR into your WordPress installation, and restricting access to the same group of users who can currently see the SPECIAL page.
I want to create a static website and use wordpress only to "compose" the website. I want to create a template that only use the same header and footer and change the content of the page (home, contact ecc dcc). My site is not a blog or any other type of site that needs CMS I only want to use Wordpress to have only one header and footer and don' t want to change it in all pages when I need some customization to it. I hope I was clear enough! Thanks!
You can create a site in WordPress (or any other CMS) on your own local computer, then save a copy using an offline browser such as HTTrack. Then upload the HTTrack saved HTML to your webhost.
This will make your site faster, as there will be no need to execute PHP on page requests, and the webserver will use its default caching headers. (Also, you get the option of using a cheaper hosting without support for PHP and MySQL.)
Any time you change the site, you'll need to edit the live WordPress version, save it again, and reupload the files.
Disclaimer: I'm dev of the WP Static HTML Output project.
It's been around for a few years and still has 5k+ active installs, but jazzing it up with some more features now and its whole purpose is to allow you to use WordPress for your site development and export to a static HTML version for speed, security and portability.
For the OP, the basic FTP publishing option may be of use. For more advanced cases, there are services like Netlify which can auto build/deploy your static site from a Git branch.
In the Settings | Reading admin page, choose a static page for your front page display. Build your site out using Pages instead of Posts. Each Page will inherit your site's standard header and footer. Create your Main Menu from the Appearance | Menu admin page to hook together your Pages. Use widgets and standard HTML links as needed. Then dress up your site with one of the many available themes.
A bit late to the table on this one but it seems that Wordpress is totally overkill for a static site. Wordpress pages can be cached with cache plugins but when any Wordpress site loads there are a number of scripts and custom php functions that run each time a page loads.
Why not just build a flat file website and simply include your header and footer with PHP? Far quicker to set up and based on your question it seems that this is simply what you need.
Added to this, you won't have an admin area for your site or a database, just the files on the server - surely this makes your site less hackable too. An added bonus is a really easy site to version control with Git or SVN.
If there's someone else out there wanting to use a static site generator over Wordpress, here's a script called WP Static which does just this: http://mossiso.com/code/make-wordpress-static
Another great solution to this problem is to use a specific software that is created exactly to do that. For Mac, for example, there's a software called Hammer that "compile" your site every time you save and includes your header and footer to the page. Is really useful.
I have a my main site, called "mysite.com" (for arguments sake). On this site, you will find my blog and everything I do. But I am starting another site that I want to run on my domain. However:
The other site must have it's down domain name: newsite.com
If people go to mysite.com/newsite it must redirec to newsite.com
If people go to newsite.com, it must show the content of what they would see if they had gone to mysite.com/newsite in the past
So basically, I want a "page" or actually a whole section ( mysite.com/newsite/* ) to appear as newsite.com in the browser.
Why?
I want both sites to run off one drupal installation
I want both sites to look basically the same
However, keep in mind that I don't want to use a multi-drupal solution. i.e. a module that allows for more than one copy of drupal to run off 1 installation.
http://drupal.org/project/domain allows you to configure various things based on the domain, for example accessible nodes.
You can probably do the redirect with a Rewrite Rule, outside of Drupal or write a simple module that does that.
Sounds simple to do. Just install the second site using a regular multi-site installation. (Google "drupal multi-site instructions"). Then install the Path redirect module and create the external redirect to the new domain. http://drupal.org/project/path_redirect