sosukeinu

Thank you for the quick response. I could have sworn i searched for the string ‘error_reporting(0);’ throughout my wordpress project, but it obviously missed one. I appreciate you addressing the problem so quickly.

not sure if this will help, and I’m also not entirely sure I’m understanding what you are trying to do, but as a general suggestion, you could add a custom field that will insert metadata in UNIX timestamp format (this takes into account date and time so you should be able to sort asc or desc on this). If your custom field is returning something other than a timestamp, you can use PHP to convert the value https://php.net/manual/en/function.date.php

You can also filter the query with a function. For instance, here is a simple query filter that uses meta_query to order posts based on a custom field called post-weight, and excludes posts that have passed another custom field called expire-date:

function my_get_posts( $query ) {
    $today = current_time( 'timestamp', 0 );
        $query->set( 'meta_key', 'post-weight' );
        $query->set( 'orderby', 'meta_value_num title' );
        $query->set( 'order', 'ASC' );

        $meta_query = array(
            array(
                'key' => 'expire-date',
                'value' => $today,
                'compare' => '>='
            )
        );

        $query->set( 'meta_query', $meta_query );

    return $query;
}
add_filter( 'pre_get_posts', 'my_get_posts' );

same sql error

Latest version of Jetpack (2.0.4) seems to fix this. Is it working for you @zeaks

Same for me. To reiterate, this only affects mobile. You can see an example of this on any page but the index here. https://pasceverbo.com thank you.

nevermind, i figured it out. it was a css class on the nav a of block and float left. duh.

I figured this one out. After updating the custom redirect in the main options. I can redirect on a per-post basis on the edit post screen. Thank you.

I thought so too, but both of those redirect fields are filled in on my options, with the page I’d like to redirect to. After reading it more closely, I saw that the redirect was for when people tried to access a members only PAGE. I was hoping to redirect when someone tried to look at a members only POST. I can’t understand why they would include an option for a redirect for pages, but not posts.

Anyone?

I’m an idiot. There was a space in the path info, removed the space, and all is working well. Thank you very much for your help, and the great plugin.

Ok, just to reiterate. I use BackWPup as a daily auto backup, and use duplicator when I need to move back and forth between development environment and live. Duplicator does exclude the snapshot directory, no problem, but I noticed it was not excluding the BackWPup directory, resulting in duplicates well over 2GB. For now, I simply store my backups somewhere offsite, but I would like to get to the bottom of why it is not excluding directories. my log file is here. Thank you for your time.

It does properly exclude the snapshot directory. I also use BackWPup to perform automated backups. It stores these under the wp-content/backups directory. No matter how I enter this directory to be excluded, I does not exclude it. I will run it again, and send the log early next week. Thank you for taking the time to respond and look into this.

My theme cotains both wp-head() and wp-footer() and the error message is sporadic, sometimes it’s there, sometimes it’s not. I emailed you site details.

Awesome! You’re the best.

I can see right away the problem for me is right here is_page() and upon deleting this, it works a charm. As ever,…thank you a ton for your help and knowledge beaver6813. Is there a way that I can make this alteration so that it isn’t overwritten with each upgrade, or will i just need to remember, and fix it? Thank again.