| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
|
| |
This allows querying the database for the count of concerts that will
match a given filter. Useful to find the total number of pages in a
pagination setting, for instance.
|
| | |
|
| |
|
|
| |
added pagination to concert list
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch got a bit more involved than what was originally planned, but
since we're messing with the tables I decided to do it all right away.
- Moves the constraint definition to the CREATE TABLE statement for the
concerts table. This replaces the existing KEY definition that it had.
- Make sure the venues table is created before the concerts table so
that the above mentioned constraint definition works.
- Rename the tables. Use the wpdb-prefix and make the name a bit
prettier. This caused some changes in the Concert and Venue classes,
and for slightly silly reasons some test classes. The code actually
turned out better (for the most part), but some refactoring can still
be done. The column names remains unchanged for now.
|
| |
|
|
| |
Missed quitation marks around search term.
|
| |
|
|
|
| |
Make it a bit more compact and fix use of $wpdb->prepare for
`currentuser` filter.
|
| |
|
|
|
| |
Should get rid of most of the annoying output during testing, and allow
moving error handling and logging to the presentation layer.
|
| |
|
|
| |
This also adds a number of new filters to find_concerts.
|
| | |
|
| |
|
|
|
| |
Makes it clearer that we're just fetching _one_ row from the database.
Also updated doc comment to hopefully be a bit clearer.
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
https://code.volse.net/wordpress/plugins/gigologadmin.git into andreaschanges
# Conflicts:
# includes/admin/views/giglog_admin_page.php
|
| | |
| |
| |
| |
| | |
It's not required since the id is in the concerts table too. That's what
links them together.
|
| | |
| |
| |
| | |
Added CSS and extra fromatting to table
|
| |/
|
|
| |
Added order by concert date in concert list
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We originally had a more specified query, but simplified it to:
SELECT * FROM wpg_concerts LEFT JOIN wpg_venues ON ...;
But since both the concerts table and the venues table has a column id,
the concert id would be overwritten with the venue id. MySQL/MariaDB
does not allow columns with the same name in multiple tables when using
unqualified column names in the query.
So we need to be more explicit again.
I was hoping that the following would work:
SELECT wpg_concerts.*, wpg_venues.* FROM .... ;
I think MySQL/MariaDB would handle that, but now since php turns the
result into an array, where each key must be unique, this again
overwrites the concert id with the venue id.
So thus a more verbose specification of the columns was necessary.
|
| | |
|
| |
|
|
|
|
| |
As a user can only be assigned to one role at the time, we remove the
current user from any role that they may have when clearing the
assignment.
|
| | |
|
| |
|
|
|
| |
This will trip up any existing records in the db, but that should not
matter, since we're changing how this entire stuff works now.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Also make sure we explicitly set the venue attribute in the constructor.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
There's no need to have a separate table (concertlogs) for these fields.
|
| | |
|
| | |
|
| |
|
|
|
| |
Reduce to one find_concerts function taking a filter to limit the
selection.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
The previous changes required the full venue data to be included in the
constructor. This patch ensures that we handle the old case, where only
the venue id was passed in.
We still should get the full concert object including the venue name and
city back.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes the concert a full object containing all relevant info, while
we can still segment the data in the db.
Instead of this:
$concert = GiglogAdmin_Concert::get($concert_id);
$venue = GiglogAdmin_Venue::get($concert->venue());
echo "{$concert->name()} @ {$venue->name()} : {$concert->cdate()}"
You can now do:
$concert = GiglogAdmin_Concert::get($concert_id);
echo "{$concert->name()} @ {$concert->venue()->name()} : {$concert->cdate()}"
And yeah, renamed Concert::find_cid() to Concert::get() and changed it's
semantics somewhat. It now either returns the given concert if it
exists, or NULL if it does not. Simpler function; simpler to use.
|
| | |
|
| | |
|
| |
|
|
| |
Added test to create duplicate concert with varied cases in string
|
| |
|
|
|
|
|
|
|
|
| |
Restructure the method a bit, drop the `c`prefix on variables, rename
the variable to hold the created concert, and use object notation to
pass the attributes to the constructor.
Also rename the method `get` to `find`, the only call site was the
`create` method. Drop the unnecessary method `check_duplicate`. Just use
`find` instead.
|
| |
|
|
|
|
| |
We probably need some better error handling here. There's a myriad of
reasons why this call could fail, and we might need to communicate the
failure reason somewhere.
|
| | |
|
| |\ |
|
| | |
| |
| |
| | |
Modified so that band is no longer in use
|
| |/ |
|
| | |
|
| |
|
|
| |
Refactored band
|
