After latest update, cron job errors

  • Resolved fatjay

    (@fatjay)


    8 years, 6 months ago

    corn job starts now every 10 mins

    thats the error msg .. it happend after i updated to the lastes version ??

    [ Moderator note: code fixed. Please wrap code in the backtick character or use the code button. ]

    <!DOCTYPE html>
<!-- Ticket #11289, IE bug fix: always pad the error page with enough characters such that it is greater than 512 bytes, even after gzip compression abcdefghijklmnopqrstuvwxyz1234567 890aabbccddeeffgghhiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz11223344556677889900 abacbcbdcdcededfefegfgfhghgihihjijikjkjlklkmlmlnmn mononpopoqpqprqrqsrsrtstsubcbcdcdedefefgfabcadefbghicjkldmnoepqrfstug vwxhyz1i234j567k890laabmbccnddeoeffpgghqhiirjjksklltmmnunoovppqwqrrxsstyt uuzvvw0wxx1yyz2z113223434455666777889890091abc2def3ghi4jkl5mno6pqr7stu 8vwx9yz11aab2bcc3dd4ee5ff6gg7hh8ii9j0jk1kl2lmm3nnoo4p5pq6qrr7ss8tt9uuvv0 wwx1x2yyzz13aba4cbcb5dcdc6dedfef8egf9gfh0ghg1ihi2hji3jik4jkj5lkl6kml7 mln8mnm9ono
-->
<html xmlns="https://www.w3.org/1999/xhtml" dir='ltr'>
<head>
	<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
	<meta name="viewport" content="width=device-width">
	<title>WordPress ? Error</title>
	<style type="text/css">
		html {
			background: #f1f1f1;
		}
		body {
			background: #fff;
			color: #444;
			font-family: "Open Sans", sans-serif;
			margin: 2em auto;
			padding: 1em 2em;
			max-width: 700px;
			-webkit-box-shadow: 0 1px 3px rgba(0,0,0,0.13);
			box-shadow: 0 1px 3px rgba(0,0,0,0.13);
		}
		h1 {
			border-bottom: 1px solid #dadada;
			clear: both;
			color: #666;
			font: 24px "Open Sans", sans-serif;
			margin: 30px 0 0 0;
			padding: 0;
			padding-bottom: 7px;
		}
		#error-page {
			margin-top: 50px;
		}
		#error-page p {
			font-size: 14px;
			line-height: 1.5;
			margin: 25px 0 20px;
		}
		#error-page code {
			font-family: Consolas, Monaco, monospace;
		}
		ul li {
			margin-bottom: 10px;
			font-size: 14px ;
		}
		a {
			color: #0073aa;
		}
		a:hover,
		a:active {
			color: #00a0d2;
		}
		a:focus {
			color: #124964;
		    -webkit-box-shadow:
		    	0 0 0 1px #5b9dd9,
				0 0 2px 1px rgba(30, 140, 190, .8);
		    box-shadow:
		    	0 0 0 1px #5b9dd9,
				0 0 2px 1px rgba(30, 140, 190, .8);
			outline: none;
		}
		.button {
			background: #f7f7f7;
			border: 1px solid #ccc;
			color: #555;
			display: inline-block;
			text-decoration: none;
			font-size: 13px;
			line-height: 26px;
			height: 28px;
			margin: 0;
			padding: 0 10px 1px;
			cursor: pointer;
			-webkit-border-radius: 3px;
			-webkit-appearance: none;
			border-radius: 3px;
			white-space: nowrap;
			-webkit-box-sizing: border-box;
			-moz-box-sizing:    border-box;
			box-sizing:         border-box;

			-webkit-box-shadow: 0 1px 0 #ccc;
			box-shadow: 0 1px 0 #ccc;
		 	vertical-align: top;
		}

		.button.button-large {
			height: 30px;
			line-height: 28px;
			padding: 0 12px 2px;
		}

		.button:hover,
		.button:focus {
			background: #fafafa;
			border-color: #999;
			color: #23282d;
		}

		.button:focus  {
			border-color: #5b9dd9;
			-webkit-box-shadow: 0 0 3px rgba( 0, 115, 170, .8 );
			box-shadow: 0 0 3px rgba( 0, 115, 170, .8 );
			outline: none;
		}

		.button:active {
			background: #eee;
			border-color: #999;
		 	-webkit-box-shadow: inset 0 2px 5px -3px rgba( 0, 0, 0, 0.5 );
		 	box-shadow: inset 0 2px 5px -3px rgba( 0, 0, 0, 0.5 );
		 	-webkit-transform: translateY(1px);
		 	-ms-transform: translateY(1px);
		 	transform: translateY(1px);
		}

			</style>
</head>
<body id="error-page">
	<p><strong>:</strong> Method Not Allowed

</p></body>
</html>

    https://www.ads-software.com/plugins/wp-spamshield/

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Contributor redsand

    (@redsand)

    At the top of the support forum there is a sticky post that we ask users to read first because it guides you to excellent troubleshooting options we have already put together for our plugin users.

    Please take a few minutes to work through the Troubleshooting Guide and FAQs, as these solve over 90% of issues users have. (Please be sure to follow all the steps, not just read through them.)

    If the information provided doesn’t solve the issue for you, we’ll need a bit more info from you on the specifics, and we’ll need to email back and forth, so please head over to the WP-SpamShield Support Form, and take a moment to fill out a support request. That will allow us to help you diagnose this, find out what the real issue is, and get things working right for you.

    – Scott

    Please note that the WP-SpamShield Support page is our main support venue, not the WordPress forums here, so that will always be the best way to get a quick response and resolve any tech support issues.

    I have the same issue on my blogs.

    After update I receive a mail like this avery 30 minutes, my Server provvider had adviced to deactive your plugin.
    Now It’s deactived but I would like to re-active again.

    p.s.: your link to support form and support page have 403 page error

    Plugin Contributor redsand

    (@redsand)

    What browser and OS were you using when you got the 403 error?

    Thread Starter fatjay

    (@fatjay)

    pietro.montagna

    yeah that same thing i have… after the latest update the cron job on my server is going crazy ??

    @red

    Firefox and Chrome

    Error 403: Forbidden
    Access to this page is restricted. We apologize for any inconvenience.

    This is for all pages of the sites.

    Thanks

    Plugin Contributor redsand

    (@redsand)

    @pietro @fatjay

    Ok, try the Support Page again.

    Once you submit your support request we can look into it for you.

    Thread Starter fatjay

    (@fatjay)

    I try that and get only this msg after sending the msg

    There is a problem with your support request.

    As noted above, you need to work through the FAQs and Troubleshooting Guide before submitting a Support Request. You checked the box saying you have worked through these, but you haven’t visited the Known Issues and Plugin Conflicts page yet. This is step 2 of the Troubleshooting Guide. Please go back and work through these completely before submitting a support request.

    We receive many support requests that are easily solved by reading the FAQs and Troubleshooting Guide. This is a requirement for submitting a support request.

    Being that this plugin is provided free, and support is provided free on a volunteer basis, we ask that you be respectful and take a few minutes to look into the issue on your own using the resources we have provided, before you submit a support request. Consider that we have over 100,000 sites actively using this plugin, and if we don’t make this requirement, we will have to move to premium paid support only.

    We are more than happy to help those who are willing to take a few minutes to help themselves.

    ??

    Plugin Contributor redsand

    (@redsand)

    @fatjay

    Yes…?

    I think that’s fairly self-explanatory…no?

    You checked the box saying you have worked through these, but you haven’t visited the Known Issues and Plugin Conflicts page yet. This is step 2 of the Troubleshooting Guide. Please go back and work through these completely before submitting a support request.

    We offer extensive support, but as noted above in my first response, users do need to work through the Troubleshooting Guide and FAQs first.

    It’s simply a form validation feature. If you got that response, it means you checked the validation box saying you had worked through the Troubleshooting Guide and FAQs, but hadn’t yet visited one or more of the pages…so it just means you need to go back and finish up. Then submit your request when you’re done.

    Thread Starter fatjay

    (@fatjay)

    But i visited the sites before… ?? even before you answered on my fist post now i can send the msg …

    Plugin Contributor redsand

    (@redsand)

    Ok. No worries. ??

    Just go ahead and submit the support request, and we’ll be happy to help you fix your issue.

    ** Please keep in mind that the WordPress forums here are not our main support venue…The WP-SpamShield Support page is our main support venue. Please direct your questions there, as that will always be the best way to get a quick response and resolve any tech support issues.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘After latest update, cron job errors’ is closed to new replies.