Re: Bug: Old field value persists after change, gets used in default macro call

Posted by DavidJCobb on Jul 24, 2012; 4:55am
URL: https://support.nabble.com/Bug-Old-field-value-persists-after-change-gets-used-in-default-macro-call-tp7580796p7580817.html

Pedro <Nabble> wrote

DavidJCobb wrote

Did you look at the NAML for Reaching Perfection, or the NAML for Testing Perfection?

Testing Perfection still has the problem -- the field's value is changed before a macro is called, yet that macro's output writes the old value.

I've looked Testing Perfection. In this forum, Testing Perfection, that I'm asking you if there is some script that are changing the node input.

OH, I think I know what you mean.

If you click "Reply" on a post, then the Quick Reply form attaches to that post, and the node field is changed by a script.

If you just use the Quick Reply form without clicking "Reply" on anything, however, the node field retains the value that the NAML code writes out. That value should be the ID of the page_node (first post in the thread), but instead, it is the ID of Testing Perfection's root node. The NAML bug I'm reporting makes it impossible for me to fix the value using just NAML.

So what ends up happening is that some users use the form without picking a specific post to reply to. This should result in them sending a reply to the first post in the topic, but instead, their reply becomes a direct child of the site's root node.