hehafner

Ok, I will do that. Thanks

Hi @jeherve, I did try that but to no avail.

I tried enabling XML-PRC but Jetpack still does not work. I’ll have to leave it off for right now. Awaiting further instructions.

Upon further testing, I found there is a conflict between iThemes Security and Jetpack. If I turn off iThemes, Jetpack works. Any idea what the problem is between the two?

I checked my .htaccess and it has:

	# Disable XML-RPC - Security > Settings > WordPress Tweaks > XML-RPC
	<files xmlrpc.php>
		<IfModule mod_authz_core.c>
			Require all denied
		</IfModule>
		<IfModule !mod_authz_core.c>
			Order allow,deny
			Deny from all
		</IfModule>
	</files>

Not sure how it became disabled.

I deleted the plugin and then reinstalled. After reinstalling I was locked out. The diagnostic says:

Debug
XML-RPC is not responding correctly ( 404 )
It looks like XML-RPC is not responding correctly. Please make sure XML-RPC is turned on for your site and is set up to respond to all content types. You can test this yourself by running the following command from the command line:

curl -A ‘Jetpack by WordPress.com’ -d ‘<methodCall><methodName>demo.sayHello</methodName></methodCall>’ https://chefeliana.com/xmlrpc.php
The answer should be:

<?xml version=”1.0″ encoding=”UTF-8″?>
<methodResponse>
<params>
<param>
<value>
<string>Hello!</string>
</value>
</param>
</params>
</methodResponse>

I haven’t done anything to the XML-RPC file.

@ambmills I checked all links to confirm it wasn’t operator error. All links in the product were all correct. When I clicked on the affiliate product, it went to the pdf, on all affiliate paperback products. My client got tired of waiting. She has customers trying to buy the paperback books, so she had me bypass the plugin.

I have run a conflict check with all plugins and themes. There is no interaction/conflict. My assumption is that it is conflicting with WordPress.

Version 1.0.1 has worked fine up until July. This is the first purchase in August and there have been a lot of updates since July. My client reports this is the first time this has occurred. I am running a conflict test right now. So far, it’s not conflicting with any of my plugins.

Thanks, @rogierlankhorst! You’ve helped a great deal. I’ll close this ticket now! Thank you for all your hard work!

Correct. My client hasn’t. I opened them up so she would see them to fill in. So, I’m sure that she would fill them in when she sees them. However, if having blanks cause Google to choke, I may need to hide them. Please correct me if I’m wrong.

Thank you

Thanks again @rogierlankhorst! I’m still getting email from google saying:

Top new issues found, ordered by number of affected pages:

Invalid value type for field “prepTime”

Invalid value type for field “cookTime”

But I think if I shut those off I’ll stop getting the alerts.

Thank you, @rogierlankhorst for looking into this deeper for me.

I went back into the post and found that there is a Markup Scheme under the editor that WP supplies and the skin that I use, Agility, also supplies one. Both of these were set on “Recipe.” Perhaps this is the problem? Other than that, there is only one recipe in the post.

I have turned off the skin schema for now and will see if that helps.

Thanks

Is this something that I need to do to my website, or just wait for the update?

Thank you for helping with this problem.

Heidi

@binarywc Thanks for the links of plugins, but none of them seem to organize the appearances > widgets area, as far as I can see.