search

wombats-writing-code / fbw-components

Fly-by-Wire components for building user interfaces
http://fbw.mit.edu
MIT License
0 stars 1 forks source link

Edits displaying inconsistently on authoring tool #35

Closed dnshah closed 7 years ago

dnshah commented 7 years ago

It doesn't happen everytime, but yesterday and today, when edits are made to an item (stem, answer choices, solution), sometimes things display correctly, sometime not. I can't figure out a trend. I've been working on the Inventory Costing module in accounting. @cjshawMIT @luwen-huang

coleshaw commented 7 years ago

Okay, let me try to replicate it on my end … are you doing this on campus, at home, VPN, etc.?

El oct 7, 2016, a las 9:34 AM, dnshah notifications@github.com escribió:

It doesn't happen everytime, but yesterday and today, when edits are made to an item (stem, answer choices, solution), sometimes things display correctly, sometime not. I can't figure out a trend. I've been working on the Inventory Costing module in accounting. @cjshawMIT https://github.com/cjshawMIT @luwen-huang https://github.com/luwen-huang — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/wombats-writing-code/fbw-components/issues/35, or mute the thread https://github.com/notifications/unsubscribe-auth/AEs6UeClpMF89n8xVL3AnPohcSE7GLBOks5qxkpJgaJpZM4KRCKT.

coleshaw commented 7 years ago

Okay, let me try to replicate it on my end … are you doing this on campus, at home, VPN, etc.?

El oct 7, 2016, a las 9:34 AM, dnshah <notifications@github.com mailto:notifications@github.com> escribió:

It doesn't happen everytime, but yesterday and today, when edits are made to an item (stem, answer choices, solution), sometimes things display correctly, sometime not. I can't figure out a trend. I've been working on the Inventory Costing module in accounting. @cjshawMIT https://github.com/cjshawMIT @luwen-huang https://github.com/luwen-huang — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/wombats-writing-code/fbw-components/issues/35, or mute the thread https://github.com/notifications/unsubscribe-auth/AEs6UeClpMF89n8xVL3AnPohcSE7GLBOks5qxkpJgaJpZM4KRCKT.

dnshah commented 7 years ago

Yesterday, on campus. Today, from Acela train wifi. Not on VPN.

I can’t figure out what triggers the non-updating scenario. The first question I edited, it didn’t update (visually, but pretty sure it must be updating on backend); then I edited 6 or 7 questions with no problem, then another question didn’t update…

Outcomes update just fine as long as you minimize the question and then re-expand it.

Darshita (Dipa) Shah, Ph.D. Associate Director for Teaching and Learning Teaching and Learning Lab, MIT (617) 324-4503 Follow @MIT_TLL TLL Blog: mitcogblog.nethttp://mitcogblog.net

On Oct 7, 2016, at 11:48 AM, cjshawMIT notifications@github.com<mailto:notifications@github.com> wrote:

Okay, let me try to replicate it on my end … are you doing this on campus, at home, VPN, etc.?

El oct 7, 2016, a las 9:34 AM, dnshah notifications@github.com<mailto:notifications@github.com> escribió:

It doesn't happen everytime, but yesterday and today, when edits are made to an item (stem, answer choices, solution), sometimes things display correctly, sometime not. I can't figure out a trend. I've been working on the Inventory Costing module in accounting. @cjshawMIT https://github.com/cjshawMIT @luwen-huang https://github.com/luwen-huang — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/wombats-writing-code/fbw-components/issues/35, or mute the thread https://github.com/notifications/unsubscribe-auth/AEs6UeClpMF89n8xVL3AnPohcSE7GLBOks5qxkpJgaJpZM4KRCKT.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/wombats-writing-code/fbw-components/issues/35#issuecomment-252288298, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AVMFNLNO01t2ueUgyDuxGs7rHm2n1ex6ks5qxmm7gaJpZM4KRCKT.

coleshaw commented 7 years ago

Hm, okay. Thanks for the added detail. I was running into a similar issue when running the app on my laptop, but only for wrong-answer LOs, but then it didn’t reappear after I deployed it to a server. Let me see.

To confirm, for all scenarios, when you refresh the page your changes show up?

El oct 7, 2016, a las 12:07 PM, dnshah notifications@github.com escribió:

Yesterday, on campus. Today, from Acela train wifi. Not on VPN.

I can’t figure out what triggers the non-updating scenario. The first question I edited, it didn’t update (visually, but pretty sure it must be updating on backend); then I edited 6 or 7 questions with no problem, then another question didn’t update…

Outcomes update just fine as long as you minimize the question and then re-expand it.

Darshita (Dipa) Shah, Ph.D. Associate Director for Teaching and Learning Teaching and Learning Lab, MIT (617) 324-4503 Follow @MIT_TLL TLL Blog: mitcogblog.nethttp://mitcogblog.net

On Oct 7, 2016, at 11:48 AM, cjshawMIT notifications@github.com<mailto:notifications@github.com> wrote:

Okay, let me try to replicate it on my end … are you doing this on campus, at home, VPN, etc.?

El oct 7, 2016, a las 9:34 AM, dnshah notifications@github.com<mailto:notifications@github.com> escribió:

It doesn't happen everytime, but yesterday and today, when edits are made to an item (stem, answer choices, solution), sometimes things display correctly, sometime not. I can't figure out a trend. I've been working on the Inventory Costing module in accounting. @cjshawMIT https://github.com/cjshawMIT @luwen-huang https://github.com/luwen-huang — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/wombats-writing-code/fbw-components/issues/35, or mute the thread https://github.com/notifications/unsubscribe-auth/AEs6UeClpMF89n8xVL3AnPohcSE7GLBOks5qxkpJgaJpZM4KRCKT.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/wombats-writing-code/fbw-components/issues/35#issuecomment-252288298, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AVMFNLNO01t2ueUgyDuxGs7rHm2n1ex6ks5qxmm7gaJpZM4KRCKT.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/wombats-writing-code/fbw-components/issues/35#issuecomment-252293437, or mute the thread https://github.com/notifications/unsubscribe-auth/AEs6UbW7wZKhPgjfteeSr4fYfzcjPBvmks5qxm5fgaJpZM4KRCKT.

coleshaw commented 7 years ago

Hm, okay. Thanks for the added detail. I was running into a similar issue when running the app on my laptop, but only for wrong-answer LOs, but then it didn’t reappear after I deployed it to a server. Let me see.

To confirm, for all scenarios, when you refresh the page your changes show up?

El oct 7, 2016, a las 12:07 PM, dnshah <notifications@github.com mailto:notifications@github.com> escribió:

Yesterday, on campus. Today, from Acela train wifi. Not on VPN.

I can’t figure out what triggers the non-updating scenario. The first question I edited, it didn’t update (visually, but pretty sure it must be updating on backend); then I edited 6 or 7 questions with no problem, then another question didn’t update…

Outcomes update just fine as long as you minimize the question and then re-expand it.

Darshita (Dipa) Shah, Ph.D. Associate Director for Teaching and Learning Teaching and Learning Lab, MIT (617) 324-4503 Follow @MIT_TLL TLL Blog: mitcogblog.net http://mitcogblog.net/<http://mitcogblog.net http://mitcogblog.net/>

On Oct 7, 2016, at 11:48 AM, cjshawMIT <notifications@github.com mailto:notifications@github.com<mailto:notifications@github.com mailto:notifications@github.com>> wrote:

Okay, let me try to replicate it on my end … are you doing this on campus, at home, VPN, etc.?

El oct 7, 2016, a las 9:34 AM, dnshah <notifications@github.com mailto:notifications@github.com<mailto:notifications@github.com mailto:notifications@github.com>> escribió:

It doesn't happen everytime, but yesterday and today, when edits are made to an item (stem, answer choices, solution), sometimes things display correctly, sometime not. I can't figure out a trend. I've been working on the Inventory Costing module in accounting. @cjshawMIT <https://github.com/cjshawMIT https://github.com/cjshawMIT> @luwen-huang <https://github.com/luwen-huang https://github.com/luwen-huang> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://github.com/wombats-writing-code/fbw-components/issues/35 https://github.com/wombats-writing-code/fbw-components/issues/35>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEs6UeClpMF89n8xVL3AnPohcSE7GLBOks5qxkpJgaJpZM4KRCKT https://github.com/notifications/unsubscribe-auth/AEs6UeClpMF89n8xVL3AnPohcSE7GLBOks5qxkpJgaJpZM4KRCKT>.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://github.com/wombats-writing-code/fbw-components/issues/35#issuecomment-252288298 https://github.com/wombats-writing-code/fbw-components/issues/35#issuecomment-252288298>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AVMFNLNO01t2ueUgyDuxGs7rHm2n1ex6ks5qxmm7gaJpZM4KRCKT https://github.com/notifications/unsubscribe-auth/AVMFNLNO01t2ueUgyDuxGs7rHm2n1ex6ks5qxmm7gaJpZM4KRCKT>.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/wombats-writing-code/fbw-components/issues/35#issuecomment-252293437, or mute the thread https://github.com/notifications/unsubscribe-auth/AEs6UbW7wZKhPgjfteeSr4fYfzcjPBvmks5qxm5fgaJpZM4KRCKT.

dnshah commented 7 years ago

Yes…I think...

On Oct 7, 2016, at 12:11 PM, cjshawMIT notifications@github.com<mailto:notifications@github.com> wrote:

To confirm, for all scenarios, when you refresh the page your changes show up?

coleshaw commented 7 years ago

Have a hack in place, will deploy soon and let you know. I can't replicate it exactly on my end, but this at least fixed the wrong-answerLO issue I saw, which I think is the same root-cause as the issue you're seeing.