KeithAdv

If I can’t get it to appear on the top line as a sortable field, I’d be equally happy if I could get author name to appear in the small type on the next line, where the font awesome icons are. Any hope?

Thank you for the response. Really nice plugin and great support.

You’ve cleared up one mystery for me, so thank you!

TubePress does filter out those videos. From my perspective, the routine doesn’t seem to affect load time in any appreciable way and I’m on a shared server, so take that for whatever it’s worth. Your answer does explain why TubePress has it as a selectable option when logic would suggest it’s something you would always want “on”–it’s because they know it’s adding time to the call.

I think you’re right about the awkward display, I didn’t understand why I didn’t always get the full number of thumbnails on a page; it’s no doubt because TubePress is grabbing a set of 20, then dropping out the problem videos, and displaying the remaining thumbnails.

Still–all things being equal–if I had to choose between the sometimes awkward-looking gallery and the well-ordered gallery that is displaying a couple “Sorry this video is private” thumbnails, I’d personally take the first.

However, thank you for the thoughtful answer. I understand how troublesome the API can be. I had the pro version of your advanced plugin and have had to replace it with this one. I appreciate how you handled the API deprecation problem.

Thank you!

That was a mess! Turns out that the theme on that old site wasn’t ready for the new world, either. Before I saw your tip, I decided to install another XAMPP with an earlier PHP. From there, I could update everything and then migrate the site to my current XAMPP with no issues.

Probably the long way around but I finally got the job done! Thanks again.

I think I’m starting to see light at the end of the tunnel. I’m using XAMPP with PHP v7.0. The site I’m trying to install was on WordPress 3.6 and that’s the version I’ve been unzipping. If I unzip WP 4.5.2, I don’t get the error message. So PHP 7.0 is incompatible with that earlier version of WP? Can someone verify?

So, this is just weird. I exported the database for one of the installs to a safe location then deleted both it and its user in phpmyadmin. Then I saved wp-content from that install to a safe location and deleted the rest of the install together.

So, everything’s gone, right?

Now if I recreate the folder in HTDOCS and point the browser to it, it will read and display that its an empty directory. But if I unzip a fresh WordPress into that directory and try to read it again, I’ll get the “Your PHP installation appears to be missing…, etc.“

I don’t get it. wp-config.php doesn’t even exist at this point. Neither do the old database and user. What is it about this directory that is causing the error message?

Holy cow. That was quick! Thank you!

Brilliant, George!

That fixed everything. And yes, after the URLs went away, I could easily tweak everything else.

Thank you!

Thanks. Webtaurus

This is a very impressively coded plugin. I’ve been able to make all needed modifications from within my child theme, so can now update the plugin when new versions are released without worries.

Thanks again, Ron!

The good news is that everything is working perfectly.

The bad news is that I know I did it the wrong way! I know just enough about PHP to realize your plugin is smartly coded to make it easy to do what I want but I don’t know enough to take advantage of that the right way.

You’ll cringe, but I’ve done surgeries on class-listings.php in three places. The first is hardcoding the slug change referenced above (because I haven’t yet learned the specific code I would use in functions.php to use the filter).

The second is hardcoding agentpress_property_details to change the number of columns (to 1) and the specific fields returned. I’m guessing I could the same fix as above when I learn how.

The third is I removed this line (at 223):

$output .= sprintf( '<p><b>%s</b><br /> %s</p></div>', __( 'Additional Features:', 'agentpress-listings' ), get_the_term_list( $post->ID, 'features', '', ', ', '' ) );

There will never be any additional features in these listings and I don’t know how to stop that from appearing on screen without just deleting the line altogether.

Yes, I’ve already experienced having to re-make these changes after you update the plugin, but I’ll keep working on learning how to make them the right way.

Thanks again!

Thank you so much, Ron!

Sorry about the misinfo in the first part of my post. You’re right, the permalink does not end in PHP.

I need just a little more hand holding, please.

I changed the line:

'name' => __( 'Listings', 'agentpress-listings' ),

to

'name' => __( 'Projects', 'agentpress-listings' ),

and that got me 90% of the way there. That MIGHT be all I need to satisfy the client with his tab concern.

However, the word “listings” still appears as part of the URL in the URL box, i.e.:

https://(mainsite)/listings/

This is where my PHP knowledge crashes and burns.

I tried changing:

'rewrite' => array( 'slug' => 'listings' ),

to

'rewrite' => array( 'slug' => 'projects' ),

But that clearly wasn’t a good idea! It just reforms the URL when calling a specific project to:

https://(mainsite)/projects/(specific project)

…resulting in a 404.

Maybe there’s no easy way to do this?

Any more advice would be greatly appreciated!

Hey, bcworkz–

I found this code snippet that unregisters the CPT altogether. In addition, it removes “Events” from the admin menu. My calendar plugin, (that apparently gets registered after all this) puts its own “Events” on the menu. I like this because it will keep the client from accidentally doing Event entries in the wrong place.

Right now, I have it directly following your code in the child theme functions.php and it seems to be working well. I wonder–is it doing something redundant to your code?

function unregister_post_type( $post_type, $slug = 'Events' ){
    global $wp_post_types;

    if ( isset( $wp_post_types[ $post_type ] ) ) {
        unset( $wp_post_types[ $post_type ] );

        $slug = ( !$slug ) ? 'edit.php?post_type=' . $post_type : $slug;
        remove_menu_page( $slug );
    }
}

That worked. Thank you! I’ve programmed in a few different languages, including assembler–and I think PHP is just plain weird.

Do you think, to be on the safe side, I should follow your code with the original create_event code above (with my changed “slug” variable)?

Thank you, Travis! Unfortunately, that seems to have surprisingly little effect.

If I drop just that line into the child theme, restore the parent theme’s functions.php to the original code, and resave Permalinks, the original “collision error” comes back, resulting in the 404 error.

In order to make the site work, I still have go back to the parent’s functions.php and change the word “event” in this line…

'rewrite' => array('slug' => __('event', 'jollytheme' )),

…to something else.

I think I follow. However, I want to clarify what I’m trying to do. I may have overexplained it.

In the theme’s functions.php, the slug is set to the word ‘event’. I’ve already discovered that all my problems get solved if I change the word ‘event’ to something else on that line. (I did re-save Permalinks after). That’s where the code stands right now and I’m happy with it.

(And no, I never use the CPT in question.)

I’m simply trying to bulletproof this solution against a possible theme update by transferring it to my child theme’s functions.php, which gets called after the original theme’s functions.php. I would restore the original functions.php to its default code.

What I don’t know how to do is redeclare or change or recreate or whatever that variable once it has been created.

I literally copied and pasted the entire code above from the original theme to my child theme. That got a “cannot redeclare” error. So…is there a way to undeclare it and recreate it? Or just change the slug?

Thank you, Nicola!

I will keep that possible solution in mind.

Funny thing–before I saw your post, I actually went the other way–I got into functions.php for the theme and changed the slug for its Event type. After I resaved permalinks everything seemed to work.

I’m glad I’ll be able to use this plugin!

Thanks again.