Cristian Antohe

Yes, you’ll use the Profile Builder Form. Then simply add an extra field with the subscription plans as described here: https://www.cozmoslabs.com/docs/paid-member-subscriptions/integration-with-other-plugins/profile-builder/

Best Regards

Hi,

Hmm… the recaptha field does appear in the page and so does it’s JS code:

<li class="wppb-form-field wppb-recaptcha" id="wppb-form-element-19"><div id="wppb-recaptcha-element-pb_register1" class="wppb-recaptcha-element wppb-v3-recaptcha"><input type="hidden" name="g-recaptcha-response" class="g-recaptcha-response wppb-v3-recaptcha"></div></li>

However, your pages seam to be using https://www.ads-software.com/plugins/phastpress

Can you disable it for testing purposes and try again maybe it’s interfering with the script

Hi,

While we currently don’t have this feature, a plugin like WordFence can help with this. https://www.wordfence.com/help/blocking/country-blocking/

It allows you to block certain pages from being accessed from various countries.

Best Regards

Hi,

To add custom fields you can combine Profile Builder free(https://www.ads-software.com/plugins/profile-builder/) with Paid Member Subscriptions.

You can then have a registration form that’s fully customizable, with extra fields https://www.cozmoslabs.com/docs/paid-member-subscriptions/integration-with-other-plugins/profile-builder/

As for styling, signup form styles are only available in the paid versions of the plugin, however, you can use CSS to make changes to the styles.

Best Regards

I meant to make sure it’s not checked. It can’t work without it unchecked.

Unfortunately if you can’t select the HTML added text, it’s possible we simply can’t detect it using our current method. The only other solution is to create two different forms, one for each language and use the conditional shortcode mentioned above.

Best Regards.

The wetransfer expired, but if you refer to the Lorem Ipsum text on page 3, then it should work as long as dynamic translation is enabled.

Please go to TranslatePress -> Settings -> Advanced -> Troubleshooting -> Disable dynamic translation
and make sure it’s not checked. Because I can’t see any ajax calls to trp-ajax.php file. Usually there is something that gets loaded with JS and we should detect various strings.

It does not seam to be a JS error issue per say.

Can you send me a link to where the issue is happening?

A possibility could be the fact that your “trp_*” tables have different collations.
Could you tell me what collation you have right now in your database? Try to access it and see if you can change it with utf8mb4_general_ci. Here are some tips: https://mediatemple.net/community/products/dv/204403914/default-mysql-character-set-and-collation.

That’s very weird. Do you use a copywright blog? It’s possible it’s dynamic and brakes in secondary. Change that to text and just place 2024 there.

You can also try to go to

TranslatePress -> Settings -> Advanced -> Miscellaneous options -> Date format and change the format for the second language to be exactly the same as the one from English.

Can you send me some screenshot with the Translation Editor, the actual string in the front-end and post a link to where this is happening. Some strings don’t get detected correctly. I’m trying to figure out if it’s an issue we know of or just a string that doesn’t get detected.

Best Regards,

Thank you for your kind words! Best of luck with your project!

Hello,

Unfortunately no. That’s because we do not create standalone pages. We store everything, string by string in the trp_dictionary_* named tables. So we can’t match the original NL content (that your TP website is written in) to the external websites Spanish & French.

It’s not even possible if you write custom code.

Best way would be to create a staging website, enable automatic translation, translate everything in ES and FR and then, manually make changes based on the standalone websites and their information.

Best Regards,

Hi,

This is a weird bug. Those characters seam to be dates?

If you try to manually translate “2024” from Translate Page , what exactly you see in the translation editor?

Also, the newsletter doesn’t show. Did you use a conditional shortcode to hide it in the secondary language?

Best Regards

Hello,

issue is with links added manually inside of content on pages and posts.

It looks like you might have the setting “Force language in custom links” disabled in TranslatePress Settings page. Make sure it’s checked then try again.

If it still doesn’t work, please tell me the actual URL you point to. Is it like example.com/about or /about ?

Ideally you would use full url’s like: https://example.com/about/ . This should add the correct language parameter.

Finally, if the button has the URL added on it with Javascript (has a data-url attribute on it or something similar) this won’t work at all.

In this case you can use our Conditional Shortcode Based On Language to display different content for different languages https://translatepress.com/docs/translation-shortcode/, or if your website is built with Elementor, you can restrict the modules based on language using our Restrict by Language integration: https://translatepress.com/docs/restrict-by-language/elementor-integration/.

Also, we have similar integrations with Oxygen Builder, https://translatepress.com/docs/restrict-by-language/oxygen-builder-integration/, and WP Bakery, https://translatepress.com/docs/restrict-by-language/wpbackery-integration/.

And write here as well so I can be notified after you opened a ticket on our website.

Thank you!

You’ll have to revert back to the translatepress-personal license as well.

Please contact us to https://translatepress.com/support/ask-a-presale-question/ , a link to this www.ads-software.com ticket for reference and we’ll provide you with the 1.2.8 version that should work.

Best Regards,