Title: luckyray's Replies | WordPress.org

---

# luckyray

  [  ](https://wordpress.org/support/users/luckyray/)

 *   [Profile](https://wordpress.org/support/users/luckyray/)
 *   [Topics Started](https://wordpress.org/support/users/luckyray/topics/)
 *   [Replies Created](https://wordpress.org/support/users/luckyray/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/luckyray/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/luckyray/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/luckyray/engagements/)
 *   [Favorites](https://wordpress.org/support/users/luckyray/favorites/)

 Search replies:

## Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WeShareAI – AI-Powered Share Buttons (formerly E-MAILiT)] share buttons not showing](https://wordpress.org/support/topic/share-buttons-not-showing/)
 *  Thread Starter [luckyray](https://wordpress.org/support/users/luckyray/)
 * (@luckyray)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/share-buttons-not-showing/#post-5970285)
 * Thank you, [@e-mailit](https://wordpress.org/support/users/e-mailit/).
    It’s 
   now working.
 * But it seems that when sharing it only use the page title and there is no excerpt.
   And there is no url shortening. And it doesn’t support multiple Google+ pages
   within one Google Account.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[qTranslate X] qTranslate-X conflict with Appointments](https://wordpress.org/support/topic/qtranslate-x-conflict-with-appointments/)
 *  Thread Starter [luckyray](https://wordpress.org/support/users/luckyray/)
 * (@luckyray)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/qtranslate-x-conflict-with-appointments/#post-5943138)
 * Thank you for your reply, [@gunu](https://wordpress.org/support/users/gunu/).
 * After examining the code of Appointments plugin, I found that there is some code
   as below:
 * >  if ( $this->use_cache() ) {
   >  if ( has_filter( ‘wpautop’ ) ) { $this->had_filter
   > = true; } remove_filter( ‘the_content’, ‘wpautop’ ); remove_filter( ‘the_excerpt’,‘
   > wpautop’ ); }
 * I am not sure the purpose of doing this, but after commenting out the remove_filter
   statement, the problem is gone. I still don’t know why the mqTranslate worked
   fine with the Appointments plugin without my change.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[qTranslate X] SEO : meta keywords, meta description and title for every language](https://wordpress.org/support/topic/seo-meta-keywords-meta-description-and-title-for-every-language/)
 *  [luckyray](https://wordpress.org/support/users/luckyray/)
 * (@luckyray)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/seo-meta-keywords-meta-description-and-title-for-every-language/#post-5698088)
 * To my surprise, this problem has gone away this morning when I browse [my website](http://www.bestacupuncture.com.au/zh/),
   but I didn’t do anything! And When I tested yesterday it got the problem even
   I purged the cache and disabled the cache plugin. Any way, the good thing is 
   it works now!
 * The “WordPress SEO by Yoast” v2.0 comes out today, anyone has update experience
   to share?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[qTranslate X] qTranslate-X conflict with Appointments](https://wordpress.org/support/topic/qtranslate-x-conflict-with-appointments/)
 *  Thread Starter [luckyray](https://wordpress.org/support/users/luckyray/)
 * (@luckyray)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/qtranslate-x-conflict-with-appointments/#post-5943103)
 * Thank you for your reply, [@gunu](https://wordpress.org/support/users/gunu/).
 * I did tick the “Compatibility Functions” checkbox in the settings. But it seemed
   make no difference.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[qTranslate X] SEO : meta keywords, meta description and title for every language](https://wordpress.org/support/topic/seo-meta-keywords-meta-description-and-title-for-every-language/)
 *  [luckyray](https://wordpress.org/support/users/luckyray/)
 * (@luckyray)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/seo-meta-keywords-meta-description-and-title-for-every-language/#post-5698087)
 * I am using qTranslate-X along with the WordPress SEO plugin (by yoast team), 
   with the “WordPress SEO & qTranslate-X” plugin installed on [my site](http://www.bestacupuncture.com.au/).
 * It seems everything is good except the static home/front page. I can set the “
   SEO title” and “Meta description” in the static page for different language, 
   and after saving the changes I can see something like “[:en]Acupuncture Melbourne
   | BEST Acupuncture & Chinese Medicine Clinic | Melbourne Acupuncturist | Acupuncture
   Forest Hill[:zh]墨尔本中医 | 倍思堂中医针灸诊所 | 肩颈痛腰痛中医调理IVF支持[:]”
   appears in the “SEO Title” in the “All Pages” view. But in the browser my site
   title still showing the old English one, no matter I toggle the language.
 * Anyone using “WordPress SEO” along with qTranslate-X has the problem?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[qTranslate X] migration from mqtranslate – fatal error in code snippets-plugin](https://wordpress.org/support/topic/migration-from-mqtranslate-fatal-error-in-code-snippets-plugin/)
 *  [luckyray](https://wordpress.org/support/users/luckyray/)
 * (@luckyray)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/migration-from-mqtranslate-fatal-error-in-code-snippets-plugin/#post-5810351)
 * I just tried to migrate my website ([http://www.bestacupuncture.com.au/](http://www.bestacupuncture.com.au/))
   from mqTranslate to qTranslateX, but I had to roll back because the qTranslateX
   seemed to have different behavior in terms of handling new lines (paragraph).
   By looking into the html source, I noticed that mqTranslate uses the <p> html
   tag, but qTranslateX just use plain text CR/LF new line. So the pages looked 
   messy after the migration and I chose to roll back.

Viewing 6 replies - 1 through 6 (of 6 total)