1 | | Perhaps it is the issue identified in ticket #9936. I upgraded the Trac install from 0.11 to 1.0. From what I recall though, 0.11 didn't use JS at all, right? If that's the case, I assume it wouldn't be a server-side JS caching issue. |
2 | | |
3 | | Looking back at the docs, I didn't update Python (missed this part TracUpgrade#UpgradingfromTrac0.11toTrac0.12). That said, I can't imagine that running an older version of Python should have any impact on the JS...thoughts? |
4 | | |
5 | | I'll see if I can dig in a bit more to see if there is a plugin that might be affecting the JS. Is there anything else that you guys would suggest I look at? |
6 | | |
7 | | cboos - you mentioned something about a {{{deploy}}}. Are you referring to TracUpgrade#a5.Refreshstaticresources? I didn't think that applied to my install so I didn't run that command. |
8 | | |
| 16 | |
| 17 | Perhaps it is the issue identified in ticket #9936. I upgraded the Trac install from 0.11 to 1.0. From what I recall though, 0.11 didn't use JS at all, right? If that's the case, I assume it wouldn't be a server-side JS caching issue. |
| 18 | |
| 19 | Looking back at the docs, I didn't update Python (missed this part TracUpgrade#UpgradingfromTrac0.11toTrac0.12). That said, I can't imagine that running an older version of Python should have any impact on the JS...thoughts? |
| 20 | |
| 21 | I'll see if I can dig in a bit more to see if there is a plugin that might be affecting the JS. Is there anything else that you guys would suggest I look at? |
| 22 | |
| 23 | cboos - you mentioned something about a {{{deploy}}}. Are you referring to TracUpgrade#a5.Refreshstaticresources? I didn't think that applied to my install so I didn't run that command. |