summaryrefslogtreecommitdiffstats
path: root/includes/admin/views/giglog_import_gigs.php
Commit message (Collapse)AuthorAgeFilesLines
* Fixed calls to cretae band/venue functions in import gigs codeAndreaChirulescu2021-04-121-2/+2
|
* Change venues into proper objects.Harald Eilertsen2021-04-101-1/+2
| | | | | | | | | This means most static functions now either return a venue object, or an array of venue objects. The exception is the `all_cities` method, which still return an array of cities as strings. The constructor has been made private, as it should not be used directly from anywhere but the static methods on the Venue class.
* Fix gig import logic.Harald Eilertsen2021-04-011-16/+22
| | | | | Add entry to concertlogs table, and fix some error reporting and misc input cleaning.
* Refactor processing uploads.Harald Eilertsen2021-03-081-58/+41
| | | | | | | | | | Moves all database operations to separate classes for each type of object, bands, venues and concerts. This makes the logic cleaner, and concentrates the db related code to logically distinct parts of the code. This means we no longer need the global access to the $wpdb object from the processing code.
* Import gigs directly from uploaded file.Harald Eilertsen2021-03-071-11/+77
| | | | | | | | | | The original snippet based design expected an unknown number of files with gig data to be available at some specific location, and an admin could "process" these at will. When transforming to a plugin based design, we don't really need this two stage import anymore, so just process the imported data right away. This also makes the `wpg_files` table obsolete.
* Implement upload of gig data files.Harald Eilertsen2021-03-071-1/+41
|
* Add a sub page for importing gigs in admin.Harald Eilertsen2021-02-231-0/+25
Just an emtpy placeholder for now.