• Great plugin, works out of the box and has great settings to play with. The pro version is a must have because the true value of this plugin lays in the automatic translation on the fly! Deepl paid API service works flawless with this plugin.

    Pro’s:
    1. Made for auto translation
    2. Easy to use and install
    3. Works flawlessly
    4. Pricing is great
    5. GREAT support (but no forum ??)

    Cons:
    1. Not as customizable as something like WPML
    2. Development documentation is minor
    3. No user feedback/support forum where you can search online for fixes. Also stackoverflow etc there is nothing about this plugin. To young?

    Five stars because its a great plugin and I only have minor personal development cons.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Support Alex

    (@alexcozmoslabs)

    Thank you for your comprehensive review and feedback, we greatly appreciate it!

    We are glad to hear that you find our plugin useful and that the DeepL paid API service works flawlessly with our plugin. We also appreciate your kind words about our pricing and support, these points are definitely important in providing a seamless user experience.

    Regarding your concerns:

    1. Customizability: While TranslatePress may not be as customizable as some plugins like WPML, we prioritize ease-of-use without compromising on the key features. We are constantly working to improve and introduce new features based on user feedback.

    2. Development documentation: We acknowledge that our documentation can be expanded and we’re always working to improve it. Your feedback is valuable in this respect.

    3. Support forum: We understand the need for a platform where users can share and search for solutions. For now, we recommend reaching out through our support ticket system or checking our knowledge base for any immediate concerns.

    We appreciate your five-star rating and are glad you find TranslatePress valuable. We hope to improve upon these points in the future. Please feel free to reach out to us if you have any more questions or further feedback.

    Thank you once again for your time and contribution!

    Thread Starter tatof

    (@tatof)

    Thanks for the reply!

    The point about customizability is only from a developers perspective. The settings the plugin offers are more then enough ?? I would like to do more through .php so I can alter functions through my theme.

    Also like an option to never translate any strings that ends on a domein like: .nl .com .de .be etc etc because bakker.nl should not become baker.co.uk. Thats just a wrong translation

    Plugin Support Alex

    (@alexcozmoslabs)

    Hi,

    Thank you for the feedback.

    Regarding the translation of the domain of a string/link, at the moment, you can exclude the string/link selectors using the Exclude strings section from TP Settings –> Advanced tab.

    Thank you again for your constructive point of view.

    Best Regards,

    Thread Starter tatof

    (@tatof)

    I know but there is no way you could add an wildcard. like (*).nl

    Plugin Support Alex

    (@alexcozmoslabs)

    Hi again,

    A workaround that might help your case is to exclude links from both translations and from being added to the database. This is useful if you don’t have the need to manually change external links in the translated pages. Internal links will still be converted automatically to ensure navigability in the same language for visitors. Check the following code as an example:

    add_filter('trp_skip_strings_containing_key_terms', 'trpc_exclude_strings_containing_certain_key_words' );
    function trpc_exclude_strings_containing_certain_key_words($array){
    $array[] = array(
    'terms'=> array( 'fb-messenger://share?app_id=', 'https://newsgeek.com.br/wp-admin/admin-ajax.php?action=', 'https://www.facebook.com/' ),
    'operator' => 'or'
    );
    return $array;
    }


    Kind Regards,

    • This reply was modified 1 year, 4 months ago by Alex.
    Thread Starter tatof

    (@tatof)

    thanks! Will try to rebuild this to a wildcard array with *.nl *.be.

    If string contains .nl -> dont translate .nl and everything before it until space. Something like that

    Thread Starter tatof

    (@tatof)

    I made this solution for links, email links, phone links etc.

    It uses the WP_HTML_Tag_Processor filter to change the A href data and add “data-no-translation” attribute.

    function wpdc_filter_affiliate_links_in_content( $content ) {
        $processor = new WP_HTML_Tag_Processor( $content );
    
        while ( $processor->next_tag( [ 'tag_name' => 'a', 'tag_closers' => 'skip' ] ) ) {
    
            $homeURL = wp_parse_url(home_url())['host'];
            $blockAHREF = (string)$processor->get_attribute('href');
            if(
                !str_contains($blockAHREF, '://'.$homeURL) // if link doesn't start with home url
                && !str_starts_with($blockAHREF, '/') // if link doesn't start with "/"
                && !str_starts_with($blockAHREF, '#') // if link doesn't start with "#" (this issn't translated anyway)
            ){
                //$processor->add_class( 'skiplang' );
                $processor->set_attribute( 'data-no-translation', '' );
            }
    
        }
    
        return $processor->get_updated_html();
    }
    add_action( 'the_content', 'wpdc_filter_affiliate_links_in_content' );
    • This reply was modified 1 year, 2 months ago by tatof.
    Plugin Support Alex

    (@alexcozmoslabs)

    Hi,

    Thank you for sharing the code with our community.

    Kind Regards,

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Just perfect! Automatic translate with Deepl API’ is closed to new replies.