Merged but new

[rhondairv]

I can not find the exact code or i would put this in another section.


I am wondering if there is a way to merge double postings into the double posters last post and make it so it shows there is a new post also.

Before when i used it, it merged great, but there was no way to see that a new post had been made (but merged).

Is that even possible?

[Wormopolis]

you were using my automerge script?

[rhondairv]

I am unsure who's it was. It was nice. If someone double posted it just went into the last post already made.

[rhondairv]

It was yours i used. I found it today.

[Wormopolis]

well the "new" part might be hard to figure out. there isnt anything already on the page that indicates something is new.

my jump to last post code should still bring it up.

[rhondairv]

yeah, i was kinda thinking the same.

[Wormopolis]

"new" is relative to the user as well. Lets say you were on this site every day and checked all the new posts. tomorrow, if any new posts had occured, it would show them as new to you by having the little blue icon on the thread title in the thread listing.

if someone hasnt been here for a week, when THEY look at the thread titles, they will see little blue icons in different places then you did, because you had already cleared them as being new by visiting them today. Its not stored anywhere local when somethingis new for someone since its the PB server that puts those icons there.

when you click the little blue icon, it takes you to the first post that the PB server has stored in your account as not being viewed yet. the post itself doesnt actually have anything in it however to designate that its new. the URL might have a #num appended to it however, and THAT could be used.

but now a new problem arises, if we go by the #num being there, then anytime that is present a code would get confused thinking it means a new post, and it would try to label a post as being new when it wasnt. for example, click the "link to post" in your very first post of this thread. the URL now has #4413 at the end of it.

you might think, well what if the #num wasnt the last post then you could have the code ignore everything. thats fine and dandy for "link to post" example, but lets say 3 people post in a thread since you last looked at it. the PB server is goign to send you to the first post you havent viewed. if you have the code ignore the fact it isnt the last post on the page, then its going to ignore that the last 3 posts are new and wont run.

the jump to last post code I have running, takes into account my auto-merge script already. if the last post gets merged into a previous post, then it jumps to THAT post instead. I can give you the updated jump code if you dont have it.

[rhondairv]

I think i have it and just LOVE that code! It works FANTASTIC!!!

I was thinking that the flashing new post code would somehow flash if a new post had merged with a previous post ( double posting) for those that had been caught up with all the posts made before the merge ... if that makes sense lol. I can see how hard if not impossible that might be.

Thanks for all the thought about this.

[Wormopolis]

the flashing new post code will still flash on the main page, but it wouldnt have any idea about it being merged until it got the the thread itself. once at the thread, it wouldnt know it was being directed to a "new" thread anymore since the "action=gotonewpost" gets converted by PBS.

[Wormopolis]

I have looked, but I just dont find a way to tell if A) the new post on the main page will be merged when you get to the thread, or B) that the post you are looking at in the thread is ACTUALLY new since the URL doesnt provide any information different then any post that was directly linked to.

Im sorry.

[Wormopolis]

THIS version will scroll to the post that the new post is merged into:

<script type='text/javascript'>
<!--
//  Go to your post after posting.
//  Original code created by CrAzY_J
//  New Version by Wormopolis

if( location.href.match(/display&board=/)) {
 pst='';
 if(!location.href.match(/#(\d+)/)) {
   if(document.referrer && document.referrer.match(/action=modifypost/) && document.referrer.match(/post=(\d+)/)) {
     pst=RegExp.$1;
   } else {
     for (lnks=document.getElementsByTagName('a'), ll=lnks.length-1; ll>0; ll--) {
       if (lnks[ll].href.match(/action=gotopost/) && lnks[ll].innerHTML.match(/link to post/i) && lnks[ll].href.match(/post=(\d+)/)) {
         pst=RegExp.$1;
         break;
       }
     }
   }
 } else {
    pst=RegExp.$1;
 }
 if (pst && document.getElementsByName(pst)[0])  {
   parentcheck=document.getElementsByName(pst)[0].parentNode.parentNode;
   while (parentcheck.style.display=='none') {
     parentcheck=parentcheck.previousSibling;
     pst=parentcheck.firstChild.firstChild.name;
   }
   document.getElementsByName(pst)[0].scrollIntoView(true);
 }
}

// -->
</script>



[rhondairv]

This is awesome! It flashes there is a new post on homepage and goes to it. Exactly what i asked for!

wohooooooooooooooooooooooooooo

wormo on the job!

[Wormopolis]

Well not EXACTLY... your request was worded so that you wanted some sort of indicator on a merged post that it was "new". THAT part I couldnt do. The scroll was still attainable however. that is why I marked it as denied.

but if you are happy, then I am happy.

[rhondairv]

Well i do get a flashing indicator on my homepage that there is a new post and when i click it takes me to the new merged post. So, that is fantastic!