• Resolved justinblayney

    (@justinblayney)


    Hello,

    I have read the other thread on custom fields and could not get it to work with my variation. I did try to use the built in, custom field function for qtranslate-x, instructions were clear but when i go to edit my custom post, it simple doesn’t work, it wont swap the fields out when i switch languages and i entered in the unique IDs for the text fields

    With all that out of the way I wrote this

    _e(“<!–:en–>”.the_field(‘sale_type’ ).”<!–:–><!–:fr–>”.the_field(‘sale_type_french’ ).”<!–:–>”);

    it just dumps both fields on the page, please help

    https://wordpress.org/plugins/qtranslate-x/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    Side note: your post hit the spam queue. Don’t make tests posts they just get deleted and someone will release your topic when the queue gets reviewed.

    Plugin Author John Clause

    (@johnclause)

    Hi @justinblayney, please, re-submit this under new topic and provide step-by-step instructions how to reproduce the problem you are experiencing. Specify theme, other plugins, specific pages and whatever is relevant. Screenshots may help too.

    I’m having a similar problem. I’m writing a plugin that simply adds a textarea to “page” type posts for custom excerpts that I’ll display on the homepage.

    I’m using metabox code from this site to do it:
    http://themefoundation.com/wordpress-meta-boxes-guide/

    I added my textarea’s id to the ‘custom fields’ section in the qTranslate-X advanced settings, so it switches between languages when I’m editing. But when I click update, and the page refreshes, both the Japanese and English values seem to be combined into a single string (or they’re both being spit out simultaneously because I don’t know how to tell it to discriminate).

    I’ve tried a combination of __() and _e(), with no luck. Any guidance or advice would be greatly appreciated! Thanks.

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

The topic ‘working with custom fields verion 2’ is closed to new replies.