.Tim Posted October 19, 2006 Share Posted October 19, 2006 10. Member signatures only parsed once per page load in a topic now(above quote from the original announcement of IPB 2.2's features)I just installed a clean copy of the RC1 from my client center. I added a signature to myself and made several replies to a post. This feature stated above does not work. I see my signature on every single post in the topic.I think this is a great idea, but I haven't a clue if it's been finalized, or removed, or what. Any ideas, or am I just not looking in the right place to enable it in the ACP?A per-user setting of this would be fantastic... let the user decide if they want to see a certain member's signature once or every time in a topic. Link to comment Share on other sites More sharing options...
TestingSomething Posted October 19, 2006 Share Posted October 19, 2006 I think it may mean that it still shows it in each post, but maybe in the past it had to go through a process each time it was in the post, but this time the process is a one time thing per page? Or maybe you're right, I am not sure. Link to comment Share on other sites More sharing options...
Mat Barrie Posted October 19, 2006 Share Posted October 19, 2006 (above quote from the original announcement of IPB 2.2's features)I just installed a clean copy of the RC1 from my client center. I added a signature to myself and made several replies to a post. This feature stated above does not work. I see my signature on every single post in the topic.I think this is a great idea, but I haven't a clue if it's been finalized, or removed, or what. Any ideas, or am I just not looking in the right place to enable it in the ACP?A per-user setting of this would be fantastic... let the user decide if they want to see a certain member's signature once or every time in a topic.The feature works perfectly fine. IPB correctly only parsed that signature once. The remaining occurrances on the page did not need to be reparsed. Link to comment Share on other sites More sharing options...
.Tim Posted October 19, 2006 Share Posted October 19, 2006 Ahhh then it wasn't meant to show it once per page.... I gotcha.Too bad... that would have been a nice feature lol Link to comment Share on other sites More sharing options...
dflorin Posted October 19, 2006 Share Posted October 19, 2006 i think you made a confusion. parsing (processing) has nothing to do with showing (the results of processing). the idea is to cut down processing time. previously ipb parsed the user signature (bbcode and stuff - i use a sequence that removes pictures from signatures) for every post displayed on a forum page, generating each time the result to be displayed. now they mean the signature is parsed (interpreted) once (probably at first ocurance in a page) and the output cached somewhere. if the same user has another post in the same page, the signature is taken from the cache instead of being processed again. what are the chances a user will change his signature in the mean time (less than a second)? therefore this is an improvement towards reducing page generation time. Link to comment Share on other sites More sharing options...
dflorin Posted October 19, 2006 Share Posted October 19, 2006 ah, it took a long time to write this. sorry, i was busy. it looks obsolete now.huh? consecutive posts are no longer merged in 2.2? Link to comment Share on other sites More sharing options...
Stuart Elliott Posted October 19, 2006 Share Posted October 19, 2006 ah, it took a long time to write this. sorry, i was busy. it looks obsolete now.huh? consecutive posts are no longer merged in 2.2?Nope not by default.Back on topic almost... how about my constantly ignored campaign to have an option to not include signatures in PMs. Link to comment Share on other sites More sharing options...
dflorin Posted October 19, 2006 Share Posted October 19, 2006 i am not sure about it, but can't you edit some skin template to avoid displaying signatures in pms? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.