Jay

Hey Kaaven, thanks for the bug report. I’m aware of this issue with the number field. I’m mid-way through a settings re-write which also handles this.

Monster,

Can you provide a few more details like so:

• What theme are you using?
• What version of the theme
• What plugin version

Basically this ‘should’ work out of the box, but there can be a couple issues that would prevent it from doing so.

1.) If there’s a javascript fatal error on your page, it may be preventing the rest of the javascript from firing.
2.) If your theme does not have the standard wp_header() or wp_footer() methods in place, then no, this plugin will not work.

In the mean time, I’ll also double check to make sure I didn’t miss something myself.

You’re on the right track. I’m on mobile so I can’t provide code examples but it would look like so:

Create an event to fire every 24 hours. 15m if you want precision but you’ll want to short circuit the handler if conditions aren’t met.

Create the handler with this logic ( or a variation ):
If – day of week = mon-fri
And – time between 3pm & 10pm set published for draft posts
Else – set draft for published posts

Similar logic for weekend times. But it could go in the same handler. Depending on the amount of posts you have this can be heavy. But is definitely a quick solution.

To set the status you’ll need a query to pull all draft posts by post status then update those if not empty. Opposite for published posts.

For that look into get_posts or WP_Query.

Your Ajax is using the current page url. More commonly Ajax should be ran through wp-ajax

See here: https://codex.wordpress.org/AJAX_in_Plugins

Wrote an article some time ago with code examples if you need a visual guide: https://webdevstudios.com/2015/02/12/handling-ajax-in-wordpress/

I’m on mobile right now but if you can post the accompanying php script I can take a look when I’m home.

This is because it’s being handled incorrectly. When you use a string as the first parameter in the array, it assumes static.

register_activation_hook() is ran through _wp_filter_build_unique_id() which makes the determination of rather to use it as static or not. Look at line 945, that’s what is producing your error.

To fix this, you need to modify your code.

<?php

if ( class_exists('MyPlugin') ) {

  $MyPlugin = new MyPlugin();

  register_activation_hook( __FILE__, array( $MyPlugin, 'activate') );
  register_deactivation_hook( __FILE__, array( $MyPlugin, 'deactivate') );

  // Not sure why you have multiple new instances?
  $plugin = new MyPlugin();
}

When using hooks you must use an array for the second variable if you’re trying to use a method within an object ( class ). I’m sure there’s a way around it, but this is how it’s been for ages.

You are correct. The XML file is not a template, is not a page, and surely isn’t a post. Therefore it completely bypasses WordPress.

That seems about right for the redirect. I’m sure there’s a “WordPress Way” of editing the .htaccess file since Core does this already, but that’s not something I typically do.

It’s just one line, but if you want to do this across multiple sites etc, then I could understand the necessity of wanting an automated solution.

Here’s a great how-to on editing .htaccess via PHP – http://forums.devshed.com/php-development/552406-editing-htaccess-php-post2106528.html

Marking resolved due to no response in months.