Post appeared as #1 when it should have been #13 - Post Numbers
Post appeared as #1 when it should have been #13
Hi. Just made a post in a topic that already had 12 posts so assumed my post would be numbered 13. Instead, it was numbered 1. I hit Ctrl+F5 (hard refresh) and that fixed the problem, the post was numbered 13 then, but why was it numbered 1 when I first created it?
-
- Registered User
- Posts: 1383
- Joined: Thu Sep 25, 2014 10:36 am
Re: Post appeared as #1 when it should have been #13
I can't think of a possible reason. Report back if it happens again in the future.
-
- Former Team Member
- Posts: 4900
- Joined: Sat Sep 10, 2011 7:12 pm
- Location: Germany
Re: Post appeared as #1 when it should have been #13
kasimi wrote:I can't think of a possible reason. Report back if it happens again in the future.
Hi. I tested it a couple of more times. Turns out every time I make a new post, it's numbered 1. I have to refresh the page every time for the numbering to correct itself.
-
- Registered User
- Posts: 1383
- Joined: Thu Sep 25, 2014 10:36 am
Re: Post appeared as #1 when it should have been #13
I can't reproduce this. What extensions do you have installed?
-
- Former Team Member
- Posts: 4900
- Joined: Sat Sep 10, 2011 7:12 pm
- Location: Germany
Re: Post appeared as #1 when it should have been #13
kasimi wrote:I can't reproduce this. What extensions do you have installed?
So far,
Advanced BBCode Box
Birthday Cake
Board Rules
Custom User Title - v1.0.0
Display Last Post
Genders
Last Post Avatar
Lightbox
National Flags
Obscure Contact Us
Password Strength
phpBB Countdown
phpBB Display Age Users
PM Welcome
Poster IP in Viewtopic
Post Links
Post Numbers (yours)
Profile side switcher
QuickReply Reloaded
Red title for new topic and new reply
Search user topics
smilies scroll box
Snowstorm & Lights
Stop Forum Spam
Topic Preview
Username Colour Changer
Was This Topic Useful?
Welcome back
-
- Registered User
- Posts: 1383
- Joined: Thu Sep 25, 2014 10:36 am
Re: Post appeared as #1 when it should have been #13
That's a lot. Try to disable one by one and see if the problem is fixed. I don't have any other ideas at the moment.
-
- Former Team Member
- Posts: 4900
- Joined: Sat Sep 10, 2011 7:12 pm
- Location: Germany
Re: Post appeared as #1 when it should have been #13
kasimi wrote:That's a lot. Try to disable one by one and see if the problem is fixed. I don't have any other ideas at the moment.
I've pinned it down. There's some kind of a conflict between your extension and the QuickReply Reloaded extension. For some reason, with QuickReply Reloaded enabled, any post I make is automatically numbered 1 until I refresh the page when it's assigned the correct number, whatever that is. But with QuickReply Reloaded disabled, posts are automatically correctly numbered.
-
- Registered User
- Posts: 1383
- Joined: Thu Sep 25, 2014 10:36 am
Re: Post appeared as #1 when it should have been #13
I see. When posting with QuickReply Reloaded the contents of the new post is rendered and returned via Ajax, i.e. the page doesn't reload. The numbering fails because only that one post is rendered, making the Post Numbers extension treat it as the first post of the topic/page.
There is a way for me to detect if QuickReply Reloaded is used when calculating the post numbers. However, I'd have to re-calculate the start value which requires an additional database query and a bunch of logic. A simpler solution would be for the QuickReply Reloaded extension to send the last post number to the server when making a post, so that I can use that value as a starting point.
Keeping in mind that reloading the page fixes the wrong post number, in my opinion both of those solutions don't justify the effort. Unless I can think of an easier solution I'm afraid there won't be a fix for this.
There is a way for me to detect if QuickReply Reloaded is used when calculating the post numbers. However, I'd have to re-calculate the start value which requires an additional database query and a bunch of logic. A simpler solution would be for the QuickReply Reloaded extension to send the last post number to the server when making a post, so that I can use that value as a starting point.
Keeping in mind that reloading the page fixes the wrong post number, in my opinion both of those solutions don't justify the effort. Unless I can think of an easier solution I'm afraid there won't be a fix for this.
-
- Former Team Member
- Posts: 4900
- Joined: Sat Sep 10, 2011 7:12 pm
- Location: Germany
Re: Post appeared as #1 when it should have been #13
kasimi wrote:I see. When posting with QuickReply Reloaded the contents of the new post is rendered and returned via Ajax, i.e. the page doesn't reload. The numbering fails because only that one post is rendered, making the Post Numbers extension treat it as the first post of the topic/page.
There is a way for me to detect if QuickReply Reloaded is used when calculating the post numbers. However, I'd have to re-calculate the start value which requires an additional database query and a bunch of logic. A simpler solution would be for the QuickReply Reloaded extension to send the last post number to the server when making a post, so that I can use that value as a starting point.
Keeping in mind that reloading the page fixes the wrong post number, in my opinion both of those solutions don't justify the effort. Unless I can think of an easier solution I'm afraid there won't be a fix for this.
No problem. Don't worry about it. Thanks.
-
- Registered User
- Posts: 1383
- Joined: Thu Sep 25, 2014 10:36 am
Re: Post appeared as #1 when it should have been #13
I have the same issue on my board with quick reply.
I love both extensions, and waiting for the fix of one of them
I love both extensions, and waiting for the fix of one of them
-
- Registered User
- Posts: 2
- Joined: Mon May 07, 2018 10:24 am