starflow

Stet that last message… I had another wordpress test site set up, so I upgraded that to WP3.3 then upgraded your plugin and all works well!

Brrrrrrrrrilliant Thank you Scott!

Thank you Scott – I’m in the middle of updating my theme at the moment and don’t want to mess things up by upgrading the latest wordpress just yet, just in case other plug-ins stop functioning.

When I get the chance to install WP3.3, I shall test out your upgrade and let you know if it works.

HAPPY NEW YEAR!

please excuse my poor typing skills ??

I’ve tried dleteting all other plugins to see if that cuased the problem, but it still did not work. So I took note of the difference form one install and another and the only difference was the database name.

I don’t know, all I know is that it’s not working with the current database.

It does however, work another database without the “1” in it nd when I create a new database

None at all!

However, I am in contact with someone who understands PHP coding well, so if you can give me some clarity on what code to alter and where, hopefully he will have a better understanding of what can be done to achieve what I want.

To me, logically it should be a simple case of redirecting the search results to display posts by “display_name” rather than “authorname”, but nothing is ever as easy as it sounds is it!

Can someone please simplify and expand on what Erik suggested or at least have another suggestion based on the coade above?

Thanks for your reply Erik, but what you suggested just went completely over my head – I am a WP novice ??

This is the code I am trying to alter…

<?php

//This sets the $curauth variable
if ( isset($_GET[‘author_name’]) ) :
$curauth = get_userdatabylogin($author_name);
else :
$curauth = get_userdata( intval($author) );
endif;

?>

and…

<?php
// show all random ads but make sure the sticky featured ads don’t show up first
$paged = ( get_query_var(‘paged’) ) ? get_query_var(‘paged’) : 1;
query_posts( array(‘post_type’ => APP_POST_TYPE, ‘post_status’ => ‘publish’, ‘display_name’ => $curauth->ID) );
?>

Cheers simplistik! ??

Understood
No, but now I know it exists, I’ll look into it
Thanks for the heads up

fairy snuff ??

If that is the only way, then so be it. Annoying, but I’ll try that approach. Thanks for the heads up Simplistik and Fonglh.

If anyone else has another approach, other than instructing new users to change their “nickname” than please let me know

I guess I’m just looking for a much simpler way, than having to explain that if they do register with a username that is already in use, and they can still register with a different username, then go on to change the “nickname”….

Nope, you’re right, I didn’t get that at all.

As I said before, as soon as user attempts to register using the same username, they get an ERROR message telling them they cannot register because the “username is already in use”.

Therefore, they cannot go any further in the registration process.