Trying to add language for Paid Membership Pro

It looks pretty normal. Does that file get loaded into option “Configuration Files”? It would be loaded there on activation of plugin or has to be put there manually. My guess would be that you skipped that step, did you?

BTW, you do not have to keep i18n-config.json under /wp-content/plugins/qtranslate-x/i18n-config/plugins/paid-memberships-pro/, this is where files distributed with the plugin are kept.

You probably better to keep it somewhere, where it will not be overwritten by an update, like /wp-content/uploads/i18n-config/plugins/paid-memberships-pro/ – to keep it organized. We plan to even include that place in automatic search of .json files.

Wherever you put it, add its path to the list of files in option “Configuration Files” on page /wp-admin/options-general.php?page=qtranslate-x#integration

Do not forget to re-save qtx configuration every time when that file is modified.

I assume “name” is the “id” of the field, which you wish to make ML, is that right? Otherwise you would need to use “jquery”.

Line “pages”: { “admin.php”:”” }, may look like this

"pages": { "admin.php":"page=pmpro-membershiplevels" }

if you do not wish to put LSB for all other plugins that use page admin.php.

I would also use something more descriptive instead of “admin” in the second line. Something like the following would be better:

"admin-config": {
	"paid-memberships-admin": {

That string is a key which identifies this configuration item. Other people may alter this item if needed, using this key as an identifier. It is just a way to keep it organized, but not very important functionality wise, unless you accidentally alter someone else configuration token. A descriptive name helps to prevent it.

Does it work now?

When you get it working, please, send the file to us (or submit PR at GitHub), and we will put it permanently under /wp-content/plugins/qtranslate-x/i18n-config/plugins/paid-memberships-pro/ in qtx disctribution.

Thanks a lot.

Thanks for your answer. I think I did forget to put the new file in the qTranslate options. After deactivating/activating the file was loaded there automatically.

Then I had to do some fixes on the json file, but no it works as expected.

Here is the code:

{"vendor":{"plugins/paid-membership-pro":"1.0"},
"admin-config": {
	"membership-levels": {
		"pages": { "admin.php":"" },
		"forms": {
			"main":{
				"fields":{
					"name": { "jquery": "input[name='name']" },
					"description": { "jquery": "textarea[name='description']" },
					"confirmation": { "jquery": "textarea[name='confirmation']" }
				}
			}
		}
	}
}
}

But as I thought this doesn’t fix my problem.

Before I implemented this json I did the magic with [:en]English[:de]deutsch[:]. The problem is that when an e-mail is sent, as far as I found out, it just takes the name from the database directly (so it doesn’t get translated to the language, it’s sent as a complete string).

Is there any easy way to fix that? Otherwise I will try to search for those and replace it with a substring.

Thanks again for your help.

Admin side or front end? They probably pass the e-mail values through some filters, which you need to find in PHP code and then you may include them in .json configuration. For example, as in one of the distributed files for MailChimp:

{"vendor":{"plugins/mailchimp-for-wp":"1.0"},
"front-config":{
	"all-pages":{
		"filters":{
			"text":{
				"mc4wp_form_before_fields":"20",
				"mc4wp_form_after_fields":"20",
				"mc4wp_form_content":"20"
			}
		}
	}
}
}

Token “filters” can be also used in “admin-config”.

Awesome. It did work. Here is the file for paid-membership-pro:

{"vendor":{"plugins/paid-membership-pro":"1.0"},
	"admin-config": {
		"membership-levels": {
			"pages": { "admin.php":"" },
			"forms": {
				"main":{
					"fields":{
						"name": { "jquery": "input[name='name']" },
						"description": { "jquery": "textarea[name='description']" },
						"confirmation": { "jquery": "textarea[name='confirmation']" }
					}
				}
			}
		}
	},
	"front-config":{
		"all-pages": {
			"filters": {
				"text": {
					"pmpro_email_filter":"20"
				}
			}
		}
	}
}

Thanks for your help.

For those who want to use it too, I did add the following to the admin page, where the membershiplevels can be changed:

<form id=”main” name=”main” action=”” method=”post” enctype=”multipart/form-data”>

Thanks a lot! Would be anything wrong with this:

"pmpro-membershiplevels": {
		"pages": { "admin.php":"page=pmpro-membershiplevels" },

if we use that in the distribution? Just in order not to load unnecessary items on other pages?

I will try it out tomorrow and gice you feedbacks.

Works like a charm. Over and out.