karlazz

Hi Jamie,

Thank you for responding. My apologies, this is in an alternate mailbox.

The URL in for these translation pages look like:
x.com/ja/mypage
The english URL looks like x.com/mypage

When I use revisionize from the tool bar, it creates a revision but it probably does not do some magic to assign it to the ja language in WPML.

When I use revisionize from inside the editor page, then it gets assigned properly. Maybe something gets copied into the revision from inside the editor that is not copied when the revision is triggered from the toolbar? Some javascript setting?

This might be a repeat of what I sent you before.

Is there some way to help you with a demo?

Regards,
Karla

Here is the code that fails. It is failing on a call to Zemanta because the json decode does not work.

function se_post_publish_ping($post_id) {
	//should happen only on first publish
	$status = false;
	if( !empty( $_POST['post_status'] ) && ( $_POST['post_status'] == 'publish' ) && ( $_POST['original_post_status'] != 'publish' ) ) {
		$permalink = get_permalink($post_id);
		$zemanta_response = se_api(array(
			'method' => 'zemanta.post_published_ping',
			'current_url' => $permalink,
			'post_url' => $permalink,
			'post_rid' => '',
			'interface' => 'wordpress-se',
			'deployment' => 'search-everything',
			'format' => 'json'
		));
	  <strong>$response = json_decode($zemanta_response['body']);
		if (isset($response->status) && !is_wp_error($zemanta_response)) {
			$status = $response->status;
		}</strong>
	}
	return $status;
}

I am having a similar problem with a dropdown selector on a custom taxonomy.

When I look in the form editor page and I choose ‘show values’, my custom taxonomy drop down selector shows the values as the same as the text for each item.

When I view the select box options in the rendered HTML via inspector, the values are the term id numbers (value=73, for example).

I have a confirmation rule that triggers a page and the url to the page has a query string of the field values. The query string item for my selected taxonomy is the name, not the term id.

My confirmation actually just refreshes the page with the form on it, and the form has a rule to dynamically populate the drop down list. This fails because the query string contains the text of the choice, not the value of the choice. If I manually set the value then the selector works fine.

mydomain.com/mypage?sid=’MMM’ is a model of what the form submission creates from the dropdown.
mydomain.com/mypage?sid=123 is what the form needs to dynamically populate the dropdown.

where <option value=123>MMM</option>

This was answered in an earlier thread.

Thank you.

Hi there,

The errors here are from the php7 compatibility checker that wp-engine provides. I see them also when I run the checker over our WatuPro files.

Is this plugin compatible with php 7? Have you tested it with PHP 7?

Thank you very much.

Thanks for the clarification and the quick response. I am testing the plugin locally. I will push it up to a staging server as soon as possible and continue testing there.

Please notify me of replies

Hello,

I had a similar problem and it mysteriously resolved when I copied the URL that is provided in the /wp-admin/options-general.php?page=nextend-google-connect options page where you add your google credential.

Item 8 say:

Click on the more options link and copy and paste [a URL is provided here] to the text area.

Item 8 deals with this part of the google credentials process:

Authorized redirect URIs

For use with requests from a web server. This is the path in your application that users are redirected to after they have authenticated with Google. The path will be appended with the authorization code for access. Must have a protocol. Cannot contain URL fragments or relative paths. Cannot be a public IP address.

This section appears on the Credentials panel of your product declaration in the API set up process.
I am assuming you got to this point.

I don’t know why copying the redirect address from my NextEnd WordPress settings screen worked when copying it from the 404 page did not. Maybe it is a character set encoding issue. I hope this works for you.

So, if you copy from the settings page, not from the error 404 page, the URL at item 8 which should look like : https://mydomain.com/wp-login.php?loginGoogle=1

That should work. It did for me.

• This reply was modified 7 years, 12 months ago by karlazz.

If it is not expiring posts, then it won’t send emails. At one point, our installation was not expiring posts and I looked at wp-cron. There is a plugin called wp-crontrol which is very helpful and lets you see when wp-cron last ran and you can kind of see if it is not running as you expected.

In the end, I set define( ‘ALTERNATE_WP_CRON’, true ); in wp-config.php and that worked. When you do that, you will start to see a “doingcron” string on your URLs. I tuned that by telling the content scheduler to check for expiring posts only once an hour.

See if that clears up your troubles. Once I had posts expiring, there was no emails, and that was related to a system configuration that I worked with the operations manager to resolve. So first, get your posts to expire!

Regards,
Karla

Me too! Thanks JochenT.

Thanks. Here is quicksand’s home: https://razorjack.net/quicksand/. It is a cool plugin.

Glad you could get so much mileage out of it! Thanks for a great plugin, we’ll look for the upgrade

Hello,

Thank you for all your responses. I turned off the search in feature and the speed went up to acceptable levels. I see you came to the same conclusion. And thanks for the tip about entries per page.

Cheers,
Karla

How would the performance settings in the settings option table be affecting the filter? Here they are —

Where-used database access tuning
Featured in enabled

Inserted in enabled

Gallery in cached

MLA Gallery in cached

Thanks