• REGISTRATION REQUIREMENTS:

    Your username here MUST MATCH your XenForo username (connected to your XF license).

    Once you have registered here, then you need to start a conversation at xenforo.com w/Bob and provide the following:
    1. Your XenForo License Validation Token
    2. The Domain Name associated with the License
    NOTE: Your account will be validated once ALL requirements are verified/met. Thank you for your patience.

Fixed Article reattribution and connected thread

Status
Not open for further replies.

nicodak

Member
AMS Premium
CAS Premium
LD Premium
SC Premium
UBS Premium
Pick'em
Sportsbook
XenForo Version String: XenForo 2.2.10 Patch 1

Addon Version String: AMS 2.2.20 (Version ID: 2020770)

Stack Trace: N/A

Can you reproduce it here? No

I have configured articles to automatically create a thread.
If I create an article and reassign it to another member, here Regionalis the created thread is also reassigned as can be seen in the screenshot below.

Capture web_21-9-2022_231257_regionalis.fr.jpeg

But on the index of the forum it is the original creator of the article which appears, me in this case. And in the latest posts/threads widget this is also the case as can be seen in the screenshot below.

Capture web_21-9-2022_231234_regionalis.fr.jpeg

Thanks.
 
Rebuilding threads in ACP resolve the widget problem but not the index problem.
In the forum view the right member is displayed.
 
Rebuilding threads in ACP resolve the widget problem but not the index problem.
In the forum view the right member is displayed.
There are 2 different issues here. One pertains to a Widget that is cached and the other pertains to cache fields in a forum record.

The "messages" sidebar block is cached, so that would fix itself at x minutes (whatever the cache for that block is). There are no cache busters for widgets with the exception of EDITING a widget. Both the Thread Record (and all of its cache fields) and the First Post record) are updated instantly when reassigning an article. That data is INSTANTLY changed (there is no delay). The issue is that the block itself is cached, so that data will not change until the cache expires and new data is fetched. Rebuilding treads will NOT change a Cached Widget, only when cache is expired for that widget and the widget data is fetched again will it change.

The OTHER issue is due to cache fields in the Forum record that are not being updated as there is no function in XF to do that as XF does not have a reassign thread function (which is why XFRM does not reassign the associated thread when reassigning a resource). This would only ever be an issue on a very low traffic site. As soon as another thread gets posted in that forum or someone makes a post in a thread in that forum, the LAST POST data for that Forum record will change.

I'll look into seeing if there is a NON hackish way to deal with those forum cache fields for low traffic sites like yours. If not, I may just rollback the reassign thread function as its NOT a Core XF feature and was only added as a FAVOR to a long time AMS Premium license holder.

In the mean time, if you have not already, you should look in the Suggestions forum at xenforo.com and upvote the suggestion for reassigning a thread (which then addons that implement a Thread Type Handler, would have that be an automatic part of the Thread Type Handler).
 
I'll look into seeing if there is a NON hackish way to deal with those forum cache fields for low traffic sites like yours. If not, I may just rollback the reassign thread function as its NOT a Core XF feature and was only added as a FAVOR to a long time AMS Premium license holder.
It's a handy feature, I think I would miss it. Indeed as soon as a first message is posted the problem no longer arises and even on a not very active forum like mine I am not sure that the members would notice this malfunction, so I reported it here because I have noticed it.
 
I've marked this as fixed as the convert Article to Thread and Reassign Article now includes triggering the rebuildLastPost() function in the Forum Entity.
 
Status
Not open for further replies.
Back
Top