A default view file, when modified, is not overridden. This is a very difficult issue to discover because the JavaScript sources are updated, the new views are loaded, etc., but they simply aren't used.
What is happening is this: when a Jax controller is created, it is mapped to a default view if an overridden view can't be found. The route set converts names to underscored format; however, the code that maps the default view does not account for this, so it indicates that the view has not been defined because the view that has been defined, is not in underscored format.
If the user manually lowercases the view name (e.g. the path "Zones/index" becomes "zones/index"), the view is overridden as expected.
A default view file, when modified, is not overridden. This is a very difficult issue to discover because the JavaScript sources are updated, the new views are loaded, etc., but they simply aren't used.
What is happening is this: when a Jax controller is created, it is mapped to a default view if an overridden view can't be found. The route set converts names to underscored format; however, the code that maps the default view does not account for this, so it indicates that the view has not been defined because the view that has been defined, is not in underscored format.
If the user manually lowercases the view name (e.g. the path "Zones/index" becomes "zones/index"), the view is overridden as expected.