| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Modified so that band is no longer in use
|
| |
|
|
|
|
| |
Refactored band
|
|
|
|
| |
Run `reuse lint` to verify that all material is licensed.
|
|
|
|
| |
Adjustments in admin page and import gigs to use the above adjustments
|
| |
|
|
|
|
| |
GiglogAdmin_Concert
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Add entry to concertlogs table, and fix some error reporting and misc
input cleaning.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
Just an emtpy placeholder for now.
|