In my Flask app running on PythonAnywhere, I encountered a persistent issue where newly introduced template variables failed to render in Jinja2 templates using render_template(), even though older ones worked as expected. This suggests the problem is possibly due to server-side caching, route mismatches, or stale templates being served. Despite clearing the cache, restarting the web app, and verifying template content, only variables that existed early on in development rendered correctly. As a workaround, I renamed route or repurposed existing known-to-work variables — a frustrating but effective solution in the face of what appears to be a PythonAnywhere caching or sync issue. So, for example if I initially used:
return render_template("atFrameBlocks.html",
bbConsoleTitle = cConsoleTitle,
bbTopPageMode = cTopPageMode)
and I want to add a new parameter
return render_template("atFrameBlocks.html",
bbConsoleTitle = cConsoleTitle,
bbBallotSelectList = cSelectList, #new parameter
bbTopPageMode = cTopPageMode)
The new parameter bbBallotSelectList doesn't seem to work and comes across as null. I have to redefine the routine and change the name of the route. Also, if I change the name of the variable, for example from cSelectList to cSelectionList, no bueno. I always have to use the original variable name, cSelectList if I want it to work without changing the route name. Strange I know. This is highly inconvenient and I'm not aware of any other way to make new mods to my app work. Also literals never seem to work as parameters. If anybody knows of another fix or has better insight please tell.
So thats why in my app, the variable called bbConsoleTitle is used to hold the BallotSelectList, it's because I didn't feel like renaming my route subroutine.
