summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | Merge branch 'dev' of ↵AndreaChirulescu2021-09-041-10/+11
| |\ \ \ | | | | | | | | | | | | | | | https://code.volse.net/wordpress/plugins/gigologadmin.git into andreaschanges
| * \ \ \ Merge branch 'dev' of ↵AndreaChirulescu2021-09-0417-1472/+373
| |\ \ \ \ | | | | | | | | | | | | | | | | | | https://code.volse.net/wordpress/plugins/gigologadmin.git into andreaschanges
| * | | | | not sure why this change is here, can be ignoreAndreaChirulescu2021-09-041-3/+3
| | | | | |
| * | | | | Merge branch 'dev' of ↵AndreaChirulescu2021-06-1510-193/+453
| |\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | https://code.volse.net/wordpress/plugins/gigologadmin.git into andreaschanges
| * \ \ \ \ \ Merge branch 'dev' of ↵AndreaChirulescu2021-05-092-0/+110
| |\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | https://code.volse.net/wordpress/plugins/gigologadmin.git into andreaschanges
| * | | | | | | Recommitted, with removed head<<<<<< and >>>>AndreaChirulescu2021-05-093-67/+9
| | | | | | | |
| * | | | | | | Tried to fix the psalm local changes done when I manually installed itAndreaChirulescu2021-05-0920-107/+455
| |\ \ \ \ \ \ \
| * | | | | | | | After installing psalm, I got these files modified with, what seems to be, ↵AndreaChirulescu2021-05-094-5/+2003
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | local hashkeys?
* | | | | | | | | ConcertsTable: fix getting city row when changing cities.Harald Eilertsen2021-09-051-1/+1
| | | | | | | | |
* | | | | | | | | test: concertlogs table is gone, no need to clear itHarald Eilertsen2021-09-051-1/+0
| | | | | | | | |
* | | | | | | | | Don't error if obsolete indexes or keys are already deleted.Harald Eilertsen2021-09-051-2/+2
| | | | | | | | |
* | | | | | | | | Fix tests.Harald Eilertsen2021-09-051-0/+1
| |_|_|_|_|_|_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since the plugin only should load on the admin side, set the WP_ADMIN constant before loading it in the tests.
* | | | | | | | Drop extra query for venue_id in concert queries.Harald Eilertsen2021-09-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's not required since the id is in the concerts table too. That's what links them together.
* | | | | | | | Move the concerts table and edit form out of AdminPage.Harald Eilertsen2021-09-043-248/+291
| |_|_|_|_|_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | | | | | Fix so concert id is not overwritten by venue id.Harald Eilertsen2021-09-041-5/+8
| |_|_|_|_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | | | | Minor tweak: Only load plugin if in admin side.Harald Eilertsen2021-09-041-9/+11
| | | | | |
* | | | | | Remove obsolere require.Harald Eilertsen2021-09-041-1/+0
| |_|_|_|/ |/| | | |
* | | | | Remove obsolete source files.Harald Eilertsen2021-09-042-127/+0
| | | | |
* | | | | Drop obsolete database tables.Harald Eilertsen2021-09-041-97/+6
| | | | | | | | | | | | | | | | | | | | | | | | | These tables are no longer being used, so let's remove them and the code to add them.
* | | | | Remove obsolete shortcodes.Harald Eilertsen2021-09-045-731/+0
| | | | | | | | | | | | | | | | | | | | These are no longer in use, and have been replaced by the admin screens.
* | | | | Remove dangling $wpdb ref in AdminPage.Harald Eilertsen2021-09-041-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | AdminPage now references the database only through the Concert (and Venue) models.
* | | | | Mark recently added concerts as new again.Harald Eilertsen2021-09-042-21/+23
| | | | |
* | | | | Add timestamp columns to concerts and venues.Harald Eilertsen2021-09-041-2/+17
| | | | | | | | | | | | | | | | | | | | To keep track of creation and modification times for each record.
* | | | | Update db tables if needed on every load.Harald Eilertsen2021-09-041-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | No need to deactivate/activate plugin to get the right version of the tables.
* | | | | Make click to unassign from concert work again.Harald Eilertsen2021-09-042-15/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | | | Rename AdminPage::returnuser to assign_role_for_user_form.Harald Eilertsen2021-09-041-5/+5
| | | | | | | | | | | | | | | | | | | | It did not return any users, but a form so name it for what it does.
* | | | | Make click to assign concert/role to self work again.Harald Eilertsen2021-09-041-29/+25
| | | | |
* | | | | Editing concerts now work again.Harald Eilertsen2021-09-032-24/+63
| | | | |
* | | | | Handle updating concert status again.Harald Eilertsen2021-09-031-6/+7
| | | | |
* | | | | Rename AdminPage::get_user -> user_dropdown_for_roleHarald Eilertsen2021-09-031-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The original name did not make much sense. The function didn't return a user, but a dropdown list of users, where the user currently holding the given role for the given concert was preselected in the list.
* | | | | Drop ref to ConcertLogs in AdminPage::get_user method.Harald Eilertsen2021-09-031-7/+10
| | | | |
* | | | | Drop query to press status table in adminactions.Harald Eilertsen2021-09-031-6/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Replace the table with hardcoded strings in the AdminPage class. This makes it a pure presentation issue, while the statuses themselves are just mnemonics. There's one smell here, and that is that the status values and their textual representation is split across two modules. (Values in Concert, and textual representation in AdminPage.) This should probably be addressed later by refactoring both into a separate AccredStatus class or something.
* | | | | Shift value of Concert statuses to be 0-based.Harald Eilertsen2021-09-031-7/+7
| | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | | | Render adminactions in concert list view.Harald Eilertsen2021-09-031-9/+9
| | | | | | | | | | | | | | | | | | | | Clicking the buttons don't work quite yet.
* | | | | Redo concert list to use the Concert class.Harald Eilertsen2021-09-031-38/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Instead of directly accessing the database with a custom query, we now just use the Concert::find_concerts method to fetch the concerts that are to be displayed. This became much easier now that we don't rely on the extra concertlogs table. There's still stuff missing to be functionally equivalent to the old code, but this should be a lot easier to get in place now.
* | | | | emove dependency on ConcertLogs in gig import code.Harald Eilertsen2021-09-032-13/+0
| | | | |
* | | | | Allow empty concerts to be created.Harald Eilertsen2021-09-031-5/+5
| | | | |
* | | | | Make name and city required attributes for Venues.Harald Eilertsen2021-09-021-6/+21
| | | | | | | | | | | | | | | | | | | | It does not make sense to have anonymous venues nowhere.
* | | | | Fix more type issues in Concert and Venue classesHarald Eilertsen2021-09-022-6/+6
| | | | |
* | | | | psalm: Add type info to attrs and constructor for Concert.Harald Eilertsen2021-09-021-8/+18
| | | | | | | | | | | | | | | | | | | | Also make sure we explicitly set the venue attribute in the constructor.
* | | | | psalm: Ad types to attrs and constructor for VenueHarald Eilertsen2021-09-021-6/+6
| | | | |
* | | | | psalm: No need for null $opts param in select_field.Harald Eilertsen2021-09-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | It's initialized to an empty array if not specified, that should be good enough, and don't trip up iterating over it.
* | | | | Fix saving and fetching roles from Concerts table.Harald Eilertsen2021-09-012-41/+24
| | | | |
* | | | | Begin move roles and status field to concerts table.Harald Eilertsen2021-06-274-0/+43
| | | | |
* | | | | Remove Band class and tests.Harald Eilertsen2021-06-272-220/+0
| | | | |
* | | | | Remove some debug output.Harald Eilertsen2021-06-271-1/+0
| | | | |
* | | | | Refactor ConcertTest some more.Harald Eilertsen2021-06-271-58/+25
| | | | | | | | | | | | | | | | | | | | | | | | | Create more of the concerts used by tests into the wpSetupBeforeClass hook.
* | | | | Refactor ConcertTests and some cleanupHarald Eilertsen2021-06-271-68/+75
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The commit changes the way we populate the database for the tests by creating more entries up front. This reduces the amount of duplicated code between the tests, but also introduce some challenges. As modifications to the database done in the wpSetUpBeforeClass hook are not cleaned up automatically by the WP_PHPUnit framework, we also have to add a wpTearDownAfterClass hook so anything we set up in this class does not disturb any other tests in other classes.
* | | | | Clean tests env before running testsHarald Eilertsen2021-06-272-0/+2
| |_|_|/ |/| | | | | | | | | | | | | | | | | | | Since we're using our own database tables, these are not cleaned by the default WP_PHPUnit setup. To ensure that we start on a clean slate when running the tests, clean the env before the tests are run.
* | | | Begin move roles and status field to concerts table.Harald Eilertsen2021-06-143-13/+97
| | | | | | | | | | | | | | | | There's no need to have a separate table (concertlogs) for these fields.