WordPress.org
Get WordPress

Plugin Directory

Changeset 385375


Ignore:
Timestamp:
05/16/2011 09:36:28 AM (15 years ago)
Author:
stevevls
Message:

merging readme changes and bugfix for finding nested page if parent not translated.

Location:
gts-translation/tags/1.1.7
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • gts-translation/tags/1.1.7/readme.txt

    r385352 r385375  
    122122
    123123= How do I use the virtual host feature? =
    124 Please see the *Virtual Host Setup* tab.
     124Please see the *Virtual Host Setup* section in the *Other Notes* tab.
    125125
    126126= What is theme translation? =
    … …  
    171171
    172172= How secure is the system? =
    173 Please see the *Security* tab.
     173Please see the *Security* section in the *Other Notes* tab.
    174174
    175175
    … …  
    185185* Widget now rewrites links using virtual hosts when set.
    186186* Send 301 redirects to virtual host when a translated blog request comes in via any other host name.
     187* Find nested pages in translated languages if parent page hasn't been translated yet.
    187188
    188189= 1.1.6 =
    … …  
    276277
    277278So far, the plugin is self-upgrading...if there's something to report later, we'll add it!
     279
     280== Virtual Host Setup ==
     281
     282### How to setup the Virtual Host feature on the GTS Plugin ###
     283
     284By default, the translated versions of your website/blog resolves to a URL address which is a subdirectory of your site’s URL address. For example,
     285the Spanish version of your site resolves to http://mywebsite.com/language/es.
     286
     287With the GTS Translation Plugin Virtual Host feature you can publish translated versions of yor website/blog under a separate subdomain or top-level
     288domain (TLD). So for example, if your blog is www.mywebsite.com you can serve the Spanish version from www.mywebsite.es.  Alternately, you can use
     289 subdomains (e.g. es.mywebsite.com) so that you don't have to buy a domain for each language.
     290
     291To implement the virtual hosts feature, follow these steps:
     292
     293### 1. Configure DNS ###
     294
     295**For Top Level Domains:**
     296
     2971. Register your new domain (e.g. www.mywebsite.es.) with a recognized domain registrar.
     2981. In your DNS zone, set the A record for www.mywebsite.es to point to the IP address of your web server.
     299
     300**For Subdomains:**
     301
     3021. Create a CNAME alias for your web server (e.g. es.mywebsite.com)
     303
     304How to complete these steps will depend on your hosting provider.  If you get stuck, please follow up with your support team.
     305
     306### 2.  Configure your Web Server ###
     307
     308Please note that all of the translated blogs will be hosted from the same WordPress installation as your current blog.
     309
     310**For Hosted Blogs:**
     311
     312Your hosting provider will provide a control panel to map a hostname to a Document Root.  For each translated host name, enter the exact same Document
     313Root as your blog.
     314
     315**For Self-hosted Blogs:**
     316
     317These instructions are only valid for Apache.  If you use IIS or another web server, please consult the relevant documentation.
     318
     319First off, you need to be set up with Name Based Virtual Hosts (http://httpd.apache.org/docs/2.0/vhosts/name-based.html).  Once you have your blog's
     320virtual host set up, add the new hostname to the ServerAlias directive.
     321
     322
     323>     <VirtualHost *:80>
     324>
     325>       ServerName     www.mywebsite.com
     326>       ServerAlias    www.mywebsite.es
     327>       DocumentRoot   /path/to/wordpress/install
     328>
     329>       # Other configuration here...
     330>
     331>     </VirtualHost>
     332
     333If you have multiple aliases, remember that the ServerAlias can be a list or can include wildcards…it can save time!
     334
     335
     336### 3.  Configure the GTS Plugin ###
     337
     338This is the easiest part:
     339
     3401. Go to the "GTS Settings" admin page.
     3411. Enter the host name in the "Virtual Host" input next to the desired language.
     3421. Click the "Save Changes" button.
     343
     344Voila, translated links will point to your new host!
     345
    278346
    279347== Security ==
    … …  
    310378We have dedicated lots of thought to locking down this system, and we are very confident that it's secure.
    311379After reading this, we hope you will be too!
    312 
    313 == Virtual Host Setup ==
    314 
    315 ### How to setup the Virtual Host feature on the GTS Plugin ###
    316 
    317 By default, the translated versions of your website/blog resolves to a URL address which is a subdirectory of your site’s URL address. For example,
    318 the Spanish version of your site resolves to http://mywebsite.com/language/es.
    319 
    320 With the GTS Translation Plugin Virtual Host feature you can publish translated versions of yor website/blog under a separate subdomain or top-level
    321 domain (TLD). So for example, if your blog is www.mywebsite.com you can serve the Spanish version from www.mywebsite.es.  Alternately, you can use
    322  subdomains (e.g. es.mywebsite.com) so that you don't have to buy a domain for each language.
    323 
    324 To implement the virtual hosts feature, follow these steps:
    325 
    326 ### 1. Configure DNS ###
    327 
    328 **For Top Level Domains:**
    329 
    330 1. Register your new domain (e.g. www.mywebsite.es.) with a recognized domain registrar.
    331 1. In your DNS zone, set the A record for www.mywebsite.es to point to the IP address of your web server.
    332 
    333 **For Subdomains:**
    334 
    335 1. Create a CNAME alias for your web server (e.g. es.mywebsite.com)
    336 
    337 How to complete these steps will depend on your hosting provider.  If you get stuck, please follow up with your support team.
    338 
    339 ### 2.  Configure your Web Server ###
    340 
    341 Please note that all of the translated blogs will be hosted from the same WordPress installation as your current blog.
    342 
    343 **For Hosted Blogs:**
    344 
    345 Your hosting provider will provide a control panel to map a hostname to a Document Root.  For each translated host name, enter the exact same Document
    346 Root as your blog.
    347 
    348 **For Self-hosted Blogs:**
    349 
    350 These instructions are only valid for Apache.  If you use IIS or another web server, please consult the relevant documentation.
    351 
    352 First off, you need to be set up with Name Based Virtual Hosts (http://httpd.apache.org/docs/2.0/vhosts/name-based.html).  Once you have your blog's
    353 virtual host set up, add the new hostname to the ServerAlias directive.
    354 
    355 
    356 >     <VirtualHost *:80>
    357 >
    358 >       ServerName     www.mywebsite.com
    359 >       ServerAlias    www.mywebsite.es
    360 >       DocumentRoot   /path/to/wordpress/install
    361 >
    362 >       # Other configuration here...
    363 >
    364 >     </VirtualHost>
    365 
    366 If you have multiple aliases, remember that the ServerAlias can be a list or can include wildcards…it can save time!
    367 
    368 
    369 ### 3.  Configure the GTS Plugin ###
    370 
    371 This is the easiest part:
    372 
    373 1. Go to the "GTS Settings" admin page.
    374 1. Enter the host name in the "Virtual Host" input next to the desired language.
    375 1. Click the "Save Changes" button.
    376 
    377 Voila, translated links will point to your new host!

  • gts-translation/tags/1.1.7/wordpress/GtsLinkRewriter.php

    r385352 r385375  
    371371                }
    372372
    373                 $original_path[] = $post->post_name;
     373                $original_path[] = $post ? $post->post_name : $part;
    374374            }
    375375        }
Note: See TracChangeset for help on using the changeset viewer.