update admin backend to work with new routes

[JohnRDOrazio]

Most of the frontend has now been updated to work with the new routes.
See 779c373...8debcd2.

The admin backend still needs to be updated to accomodate the new routes and the snake_case parameters.

[JohnRDOrazio]

when we say "backend" we are actually referring to the "extending.php" page, which should probably be in a "backend" admin interface, like "admin.php".

In any case most of the work is now done: 8debcd2...9025a7d

[JohnRDOrazio]

Currently, to avoid unsupported locale errors with the wider region resources, we have implemented a "best bet" function. However this is not desirable. We should add locales to the wider region datalist, alongside the wider region name. That way the locale will be determined by the datalist selection, and we know exactly what we are getting. AND we can get event names for any supported locale.

[JohnRDOrazio]

Currently, to avoid unsupported locale errors with the wider region resources, we have implemented a "best bet" function. However this is not desirable. We should add locales to the wider region datalist, alongside the wider region name. That way the locale will be determined by the datalist selection, and we know exactly what we are getting. AND we can get event names for any supported locale.

Fixed.

Now just to fix up the submission of data with new routes, ensuring the routes are capable of handling and saving the data.