Currently application root is always an instance of cone.app.model.AppRoot. There's no way to properly provide a custom application root implementation. Add and implement cone.root.factory configuration property and use it for creating app root if set.

Please add something like this:

<?xml version="1.0" encoding="utf-8" ?>
<configure xmlns="http://pylonshq.com/pyramid">

  <include package="pyramid_zcml" />
  <include package="bdajax" />
  <include package="yafowil.widget.datetime" />
  <include package="yafowil.widget.richtext" />
  <include package="yafowil.widget.dict" />

  <scan package=".browser" />

  <view
    for="*"
    view=".browser.static_view"
    name="static"
  />

  <authtktauthenticationpolicy
    secret="secret"
    cookie_name="__ac__"
    secure="false"
    include_ip="false"
    callback=".authentication.groupcallback"
  />

  <aclauthorizationpolicy />

</configure>

Reference browser should support datatype uuid.UUID to receive UUID instances on extraction

If application node not implements call, cone.app.workflow.persist_state fails.

Check whether app node callable

Currently, the general error view always returns an bdajax action response.

Fix for regular JSON requests.

Check for ajax forms.

cone.app.init

XXX: is this needed anywhere? If not, let's remove it.

APP_PATH = os.environ.get('APP_PATH', '')

APP_PATH is currently used to determine the directory containing file based application configuration. So, yes, it's needed, but the
name is probably confusing, or at least not very significant.

We might rename this. Suggestions?

if setting a default child for root and define 'listing' as default_content_type for this child, the listing gets rendered on root instead of child.

Issue found at: Getting Started Documentation

Currently the Run Application Command is:
./bin/pserve serve example.ini

A ValueError is triggered with this command: Variable assignment 'example.ini' invalid (no "=")

The correct command would be:
./bin/pserve example.ini

Use #ajax-form instead of #ajax-overlay selector for displaying overlay forms. This way form widgets can still use the #ajax-overlay container for widgets.

If error occurred during ajax form processing, the error gets displayed properly, but all subsequent submits in the same browser window fail.