Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Contributor Robert Hanna

    (@robertdhanna)

    @esahin,

    I’m not sure why that isn’t working for you. I’ll have to check with the developer in charge of our HTML filters. Using div tags should work in the mean time while we sort this out.

    Sorry for the inconvenience!

    Plugin Contributor Robert Hanna

    (@robertdhanna)

    @esahin,

    I’m not sure why that is happening. Let me ask a couple of questions to see if we can troubleshoot the issue.

    What do you mean by “also span tags removed from translated content”?

    Do you mean that “this content” is no longer wrapped in span tags, or do you mean that “this content” is removed from the translated document?

    Plugin Contributor Robert Hanna

    (@robertdhanna)

    @esahin,

    Yes, you should be able to use <span> tags instead of <div> tags to mark content that shouldn’t be translated. If it doesn’t work for you please let us know and we can look into it.

    Thanks,

    Please let us know if you have any more questions!

    Plugin Contributor Robert Hanna

    (@robertdhanna)

    Hello @hananemdz,

    We believe we have discovered the solution to the problem you are describing. If you are registering the post type manually (ie. putting the post type registering code somewhere in the PHP code) then you need to set the priority to 1.

    For example:

    add_action('init', 'create_custom_post_init', 10);

    This line registers a new post type but sets the priority for loading this post type to 10 (10 is the lowest priority, 1 is the highest), so if you change that line to this:

    add_action('init', 'create_custom_post_init', 1);

    Your post type should now get registered before our code runs. This will allow our plugin to give you bulk action options on the custom post type.

    Please let us know if this works for you.

    Plugin Contributor Robert Hanna

    (@robertdhanna)

    Hello @el-asador-aleman,

    We believe we have discovered the solution to the problem you are describing. If you are registering the post type manually (ie. putting the post type registering code somewhere in the PHP code) then you need to set the priority to 1.

    For example:

    add_action('init', 'create_custom_post_init', 10);

    This line registers a new post type but sets the priority for loading this post type to 10 (10 is the lowest priority), so if you change that line to this:

    add_action('init', 'create_custom_post_init', 1);

    Your post type should now get registered before our code runs. This will allow our plugin to give you bulk action options on the custom post type.

    Please let us know if this works for you.

    • This reply was modified 8 years, 6 months ago by Robert Hanna.
    Plugin Contributor Robert Hanna

    (@robertdhanna)

    Hi mango532,

    That is an excellent question. Yes, we do support something similar. For content that you don’t want to be translated you can wrap it a div with the attribute translate=”no”. Here is an example:

    <div translate="no"><!-- excluded translating any text within this div -->
       <h2>Hello</h2>
       <p>Exclude this content from translation.</p>
    </div>

    The content inside the div will not be translated when the document is processed. Please let us know if you have any other questions!

    Plugin Contributor Robert Hanna

    (@robertdhanna)

    Hi Oclair,

    Thank you for bringing this issue to our attention. We are having trouble reproducing your problem. Would you mind answering a few short questions in order to help us troubleshoot this problem?

    What version of WordPress are you running?
    What version of PHP are you running?
    Are you seeing any error messages when you click dismiss or does the banner simply persist after clicking ‘Dismiss’?

    Thank you.

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