ThrawnCA

The `strptime` workaround is effective, but it's difficult to apply when dateutil is being called from a third party library like https://github.com/okfn/messytables We're currently resorting to patching messytables on the...

This needs to be rebased from master, will push soon.

I'm unclear on why this change would break the test that's failing. The only behaviour that's altered is conditionally preventing a Package model object from being updated, and I can't...

The ckanext-datarequests example doesn't use the Back button, though...

There's no external authentication provider at https://www.data.qld.gov.au which is where we're encountering this.

This is a bit of an info dump, but the interactions between multiple plugins really do need to be documented...I'm open to adjusting it or moving it to a better...

https://stackoverflow.com/questions/52936903/ckan-extensions-overwrite-each-other-what-is-the-correct-order describes some of this, and suggests adding it to the docs, but it wasn't (fully?) done.

@amercader I'm concerned about an approach that will break pretty much all existing extensions until they change their forms, and doesn't seem to provide a backwards-compatible solution; an extension that...

Oh - also, ideally there should be a mechanism for extensions to override and provide their own implementations of CSRF token generation and validation. For example, the default Django token...

> I guess at very minimum we should have a configuration option to disable the CSRF checks, ie keep the current behaviour (`ckan.csrf_protection.enabled=False`, defaults to `True`). This would allow sites...