Ron Strilaeff

I had the exact same error message as you but for a different reason. I’m posting this to help others who stumble across this solution.

I moved a site to a new server by importing the database and copying over the entire program folder.

The problem occurred because the server had a redirect of yourdomain.com to https://www.yourdomain.com and the wp general settings wanted it to be yourdomain.com (or vice versa not sure now). I could not get to the wp dashboard, so I changed the value of those “options” in the database.

I made them both want to be yourdomain.com and everybody’s happy.

Good luck, have fun, hope this helps!

Hi, I realized that I do not need to do anything special to make it work, and no hooks to set up in crontrol.

What I did was un-check “Enable MailPoet’s Cron” under the advanced “geeky options” and set the Send frequency (under the “Send with” tab) to whatever I want. The built in wp cron works perfectly since the website is pretty active and apparently that is enough to wake it up.

By the way, I think you guys should clarify that the Mailpoet Ping is simply a last resort if for some reason your built-in wp-cron is broken or you have almost no traffic. Currently it reads like a “premium” feature that we should use for better performance. Turning it on made my newsletter sending unreliable (maybe because the mailpoet ping never came some days? … who knows).

Thanks ragulka! This is more intuitive in my case.

This guy seems to have the pagination working on the admin side:
https://www.ads-software.com/plugins/order-up-custom-post-order/

But It was overkill for what I needed. ??

It should, since by default SE searches the post_title and post_content.

An image caption (editable by the wp visual editor), as well as the link title (if any) and alt attributes are saved as raw text in the wp_post.post_content database column, so whatever you put in there will be found.

Thanks for replying and sorry for the almost duplicate question. I immediately fell in love with this plugin by the way since I have numerous background functions to prepare meta data and cleanup garbage that I’ve been triggering off of periodic user or admin actions. It is nice to have a ui to keep track of them (and actually change them or execute manually ). Thanks for doing this.

I did not realize there were two parts to the built in wp-cron.

Now that you enlightened me that it won’t do any work (other than a quick check) unless it has an event scheduled, it looks like there is no significant advantage in disabling the built in wp-cron.

It would only take a few milliseconds for wp to check a few cached db records (the scheduled tasks).

From your experience, is it ever worth disabling?

Hey Steven,

Did you figure out how to sort the meta value numerically?

I’m having trouble with “99” always coming before something like “673”. The wpdb datatype of meta_value is longtext.

Thanks if you can help, Ron

I can reproduce this problem (I have version 1.2.2 of this plugin) and am on UTC-5 time.

Here is a simplified test case:

– under the table it says utc = 14:00:00 , local = 9:00:00
– edit a hook
– enter 15:00:00 under Next Run (UTC) since I desire to run this 1 hour from now
– press “Modify Cron Event” button
– the hook is changed in the table but the Next Run time says “10:00:00 (6 hours)”

The problem is that the Next Run time should say “10:00:00 (1 hour)” if it is intended to show local time in that column.

It is wrong because in following the prompt I entered the next run as 1 hour from now in UTC, but the program scheduled it for 6 hours from now even though it shows the time of day in the table as one hour from now.

Do you see that?

John, what I think the OP is asking is this:

Is there a way to prevent the built-in wp-cron from executing whenever someone (or a robot) visits the site?

Either way, I’d like to know this answer… Does the built in wp-cron functionality really execute whenever a page is loaded? If so, that is an obvious waste of resources. Does your plugin prevent that?

Thanks, Ron

try changing this:

if (isset($_POST['goto_Page'])) { goto_page() ; }

to this:

if (isset($_POST['goto_Page'])) {
  $pagefrominput = $_POST['goto_Page'];
  goto_page($pagefrominput);
}

to pass the value from your input field on the form to that function.
I have not tested this but that piece looks like it is missing

I spent some time to create an ajax call (after page load) to my update view count function, but it still won’t execute for cached pages!

I know it works for ratings and favorites (with serverside php and database updates) but those depend on a user action like clicking on something.

Has anybody been able to execute ajax automatically after a cached page is ready? Any advice is greatly appreciated.

btw: I’ve abandoned my original strategy of using that wpsc_cachedata hook because I want to use the mod_rewrite method of caching.

Did you resolve this?

I don’t see any tabs or bulleted list so on that page.

Thanks Justin, I understand the trade off.

There was a silver lining for me though… one thing I was planning on doing with the category widget was to add the Term Group value to some of my custom taxonomy terms so I could order them more exactly.

But instead I realized since I only wanted to include a few terms in a specific order, the “Navigation Menu” widget worked way better for that. I just created whatever grouping and order of terms I wanted in a custom menu with the fancy drag and drop that is built in to wp admin and use it and change it on a whim.

Who was it that said “necessity is the mother of invention”?

Thanks for keeping up with things!

There seems to be many legitimate cases were someone should be allowed to change their vote.

For example, I rate product 5/5 based on a friend’s experience. Then I decide to buy one and it realize that it has some serious design flaw that my friend did not care about. So I would like to change my rating to a 3/5.

This is not a matter of inflating a rating artificially because it is mine or whatever.

No reason other than when I wrote that code I wasn’t quite sure how to use the json format and wanted to make sure that all my ajax responses were using json to eliminate anything unexpected. So I put in a $.ajaxSetup({…} call along with my serverside url and a couple other options. I was a little over-zealous to “just make it work”.

In hindsight, the description and notes here says it is strongly not recommended https://api.jquery.com/jQuery.ajaxSetup/ so I un-did all that and specified json right before each of my ajax posts or gets if it was truly required.

Thanks for your patience. Maybe this will help some other reader from the future.