summaryrefslogtreecommitdiffstats
path: root/includes/admin
Commit message (Collapse)AuthorAgeFilesLines
* Some cleanup in render_concerts_tableHarald Eilertsen2022-02-221-33/+23
|
* Fix so pagination remembers filters in shortcode too.Harald Eilertsen2022-02-131-4/+4
|
* Remember filter settings when paginating.Harald Eilertsen2022-02-131-33/+60
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch does changes quite a bit of how things work under the hood. It changes the filter settings from using POST to using query args in a GET request instead. This has some challenges: 1. The query args from the form will overwrite any query args in the original URL, so we have to keep the query args that was passed in as hidden fields in the form. 2. Since we try to keep the passed in query args, we need to filter out the query args that we expect to set in the form, otherwise query args that are dropped by the form will still be present as hidden args. Not too happy about how this works tbh, but at least it seems to work reasonably well for now. I've also renamed the args set by the form to make the URL a bit nicer, i.e "city" instead of "selectcity" etc for the query arg keys. I've also refactored quite a bit to make the code more manageable. Like using the view helper to create the month selector, so it's consistent with the others, and remembers it's selection. (I also simplified it to simply list the months from jan to dec, instead of starting at the current month. If it's important to keep the old behaviour I'll change it back.) There's a few problems still with this implementation. 1. It only works in the admin-section for now. Not sure why. Probably because shortcodes... 2. In the admin section it gains the `cid` and `pid` query args that should not be there. Not sure why. 3. If we change the filters while being on a page larger than the total number of pages after the filter change, we stay on the page even if it's not a valid page after the filter change. This should be trivial to fix.
* Refactor rendering of the concerts table.Harald Eilertsen2022-02-121-58/+79
| | | | | | | | The main render function was getting too large and difficult to work with. Splitting it up a little to make it more manageable. Also fix styling to make the pagination links fall on one line a bit nicer.
* Fix pagination of concert table.Harald Eilertsen2022-02-121-6/+7
| | | | | | | There's potential vulnerabilities here still, and I'm unsure if get_permalink() is entirely safe to use in this context. Seems to do the right thing, but the docs for the function indicates it has some edge cases.
* More indentation and format if statements.Harald Eilertsen2022-02-121-124/+134
|
* more pagination details fixesAndreaChirulescu2022-02-111-26/+57
|
* css small fixed for table displayAndreaChirulescu2022-02-092-75/+116
| | | | added pagination to concert list
* Added a div to make table scrollable on mobilesAndreaChirulescu2021-09-241-2/+2
|
* Changed order of date column in concerts tableAndreaChirulescu2021-09-191-4/+3
|
* Padding in table so text doesn't connect between cellsAndreaChirulescu2021-09-191-2/+2
| | | | Added a paragraph to have a bit of space under filters
* Add CSRF checks to new venue formHarald Eilertsen2021-09-172-0/+8
|
* Move New Venue form to a separate partial.Harald Eilertsen2021-09-173-9/+45
|
* Return better error for failed CSRF check on import.Harald Eilertsen2021-09-171-2/+2
|
* Add CSRF checks for edit concert form.Harald Eilertsen2021-09-172-1/+9
|
* Clean up, fix and rename db tables.Harald Eilertsen2021-09-161-49/+19
| | | | | | | | | | | | | | | | | 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.
* Reinsert created and updated columns for venues.Harald Eilertsen2021-09-161-0/+2
| | | | Was accidentally dropped during rewrite of base schema.
* Facelift of database table creation to use create tables instead of ↵AndreaChirulescu2021-09-131-323/+17
| | | | versioning. First attempt
* tests: Make an actual test for ConcertsTableHarald Eilertsen2021-09-111-3/+3
| | | | | | | | | | | 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.
* Fix indentation again.Harald Eilertsen2021-09-091-8/+10
|
* changes reagding mail sending on concert status changesAndreaChirulescu2021-09-071-14/+13
|
* Fixed wording in mails sent when concerts are assigned/unassingedAndreaChirulescu2021-09-061-4/+29
| | | | Added mailing for when concert status changes. Not sure how to get line break in text mails AND concert status as text
* fixed proper class naming for Apply buttonAndreaChirulescu2021-09-061-1/+1
|
* removed some extra characters that got lost in table HTMLAndreaChirulescu2021-09-061-1/+1
|
* Fix indentation and whitespace, add braces where missing.Harald Eilertsen2021-09-061-41/+46
|
* Merge remote-tracking branch 'andrea/andreaschanges' into devHarald Eilertsen2021-09-051-4/+5
|\
| * added images for checkbox and rediconAndreaChirulescu2021-09-051-4/+5
| | | | | | | | added class for City dropdown form
* | security: Add proper CSRF checking for the import_gigs form.Harald Eilertsen2021-09-051-3/+7
|/
* used auto ident this timeAndreaChirulescu2021-09-051-165/+165
|
* used is_admin() to check if user shoudl see xtra columnsAndreaChirulescu2021-09-051-184/+184
| | | | Re-idented the file
* Extra changes to hide admincolumns on giglog page If logged in but not using ↵AndreaChirulescu2021-09-051-6/+8
| | | | plugin
* CHanges in the concerts table for logged/non logged user. Fixed row header ↵AndreaChirulescu2021-09-051-19/+30
| | | | with city
* Fix some bugs in generated HTML for ConcertsTable.Harald Eilertsen2021-09-051-5/+5
|
* Merge remote-tracking branch 'andrea/andreaschanges' into devHarald Eilertsen2021-09-051-11/+14
|\
| * Re-added the changes for looks, and city/venue selectorAndreaChirulescu2021-09-051-11/+14
| |
* | ConcertsTable: fix getting city row when changing cities.Harald Eilertsen2021-09-051-1/+1
| |
* | Don't error if obsolete indexes or keys are already deleted.Harald Eilertsen2021-09-051-2/+2
|/
* 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.
* 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 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-041-17/+9
|
* Add timestamp columns to concerts and venues.Harald Eilertsen2021-09-041-2/+17
| | | | To keep track of creation and modification times for each record.
* Make click to unassign from concert work again.Harald Eilertsen2021-09-041-15/+13
| | | | | | 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-031-8/+24
|
* 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.
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-26 00:23:42 +0000