| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
| |
Added a paragraph to have a bit of space under filters
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Was accidentally dropped during rewrite of base schema.
|
|
|
|
| |
versioning. First attempt
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since we now have code that should be available, both on the public blog
and in the admin section, we need to be more graular when loading the
various parts of the plugin.
We still try to avoid loading admin-only parts for the public blog, but
allways load the parts that we need in either case. Also avoid running
the db migrations when running unit tests, as the schema is copied over
from the dev environment it just caues problems.
Finally, don't hardcode unit tests to always be in_admin, but rather
determine that for each test.
|
|
|
|
|
|
|
|
|
|
|
| |
There's a bit of setup to make this work as it should, we need to ensure
that the current user and current screen is set to proper values so that
the WordPress api's `is_admin()` and `current_user_can()` work as they
should.
This first test just tests that all the expected forms are being
rendered for the admin user accessing the table through the site admin
interface.
|
| |
|
| |
|
|
|
|
| |
Added mailing for when concert status changes. Not sure how to get line break in text mails AND concert status as text
|
|
|
|
| |
Missed quitation marks around search term.
|
|\ |
|
| | |
|
| | |
|
|/
|
|
|
| |
Make it a bit more compact and fix use of $wpdb->prepare for
`currentuser` filter.
|
|
|
|
| |
Move logging to presentation/logic layer if necessary.
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| | |
added class for City dropdown form
|
|/ |
|
| |
|
|
|
|
| |
Re-idented the file
|
| |
|
|
|
|
| |
plugin
|
|
|
|
| |
with city
|
| |
|
|\ |
|
| | |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
https://code.volse.net/wordpress/plugins/gigologadmin.git into andreaschanges
# Conflicts:
# includes/admin/views/giglog_admin_page.php
|
| | | |
|
| | |
| | |
| | |
| | | |
Added CSS and extra fromatting to table
|
| | |
| | |
| | |
| | | |
Added order by concert date in concert list
|
| | | |
|
| |/
|/| |
|
| |
| |
| |
| |
| | |
It's not required since the id is in the concerts table too. That's what
links them together.
|
|/
|
|
|
|
|
|
|
|
|
| |
Currently the AdminPage is still responsible for updating changes to any
of the concerts, but I'd like to get that into their respective classes
too. That way the AdminPage will just be a simple class to handle the
layout of the page, while all the specific functionality is in their
own classes.
This is also the first step to be able to reuse the concerts table on
the public end of the site.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
These tables are no longer being used, so let's remove them and the code
to add them.
|
|
|
|
| |
These are no longer in use, and have been replaced by the admin screens.
|