| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
Code is now located in the GiglogAdmin_AdminPage::update method.
|
|
|
|
|
|
| |
Moved processing of POST requests to it's own method, and added a visual
clue that a slot has been selected. Also moved relevant code into the
AdminPage class.
|
| |
|
|
|
|
|
|
|
| |
Use the Venue class to fetch venue related info from the database, and
clean up the generation of html a little.
Also sanitize input, to try to prevent XSS vulnerabilities.
|
|
|
|
|
|
| |
Moved it to the admin page for now. May move it further to a partial or
something later. There's quite a bit of cleanup needed. It still refers
to some utility functions in the old shortcode module.
|
|
|
|
|
| |
Add entry to concertlogs table, and fix some error reporting and misc
input cleaning.
|
|
|
|
|
|
|
|
|
| |
Was missing in the first import. This looks like pure static data,
though, and will probably be moved to constants in the code instead.
While this doesn't really change the db schema, the db version was
incremented to version 2, to make sure the new data is added, even if
the db is already initialized.
|
|
|
|
| |
Added help file for photo galleries
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
Display the table for assigning photographers to the different gigs on
the main admin page for the plugin. Somehow this does not work as it
should, but leave that for later.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
Currently nothing useful on the page, but a placeholder for a more
useful page later, and possibly submenus for other functionality.
The menu is placed right below the 'Media' menu for now, and is
available to anyone with the 'upload_files' capability. Both of these
may be adjusted later if there's a better location or other capabilities
fit better.
|
| |
|
|
|
|
|
|
| |
Introduces a database schema version which we store in the wordpress
options table. We could just use a flag, but if the schema ever will
change, it will be good to have it versioned.
|
|
Tables, constraints and country data taken from database dump of
prototype dataset by Andrea.
|