I am having an issue with the "Show Bio" button at the bottom of the Assign Participant screen. File: StaffAssignParticipants.php

I pull up a session. I then pull up a person who has a bio and nothing happens when I click the button. No error in the console, no error I can see. I checked on my old version of Zambia that we used for Capricon and it works fine.

Can others replicate the issue? Any ideas?

Add code to allow a custom login method.

PlanZ for Capricon is set up to allow people to login using their Capricon account that is set up by Capricon's registration. This means that code to connect to the reg system needs to be called.

I wanted to abstract this out a bit so that other groups could do something similar using their own system.

I've revised the Brainstorm function, bringing the React code into our main React app. This has the effect of making the Brainstorm tool into something that is no longer a stand-alone app. Thus, the header, favicon, footer, and menubar are all managed in the typeical PlanZ way.

That changes the look and feel, but not too dramatically. Nonetheless, the end result is a bit more unified with the rest of the application.

The sidebar text is fetched from the CustomText table; I've populated this with a default message.

This PR implements volunteer shift support to PlanZ.

I think there's meaningful overlap between the idea of "program scheduling" and "volunteer scheduling": both deal with people, times, etc. At a con, it's often fruitful to consider when someone's volunteer schedule conflicts with their panel schedule. (I also intend to show both types of data in the WisCon mobile app -- a long-standing request is that the mobile app help with reminding folks of their volunteer shifts).

Importantly, this PR introduces two screens that are implemented in React. The React code must be built (see instructions in the client directory) and the resulting .js deployed to your web server.

The functionality is implemented using two additional stages: Volunteer Set-up and Volunteer Sign-up. I haven't bothered with a variable in the db_name file: my thinking is that you can exclude volunteer functionality by simply not turning on those phases.

Volunteer set up involves setting up two pieces of data -- jobs and shifts -- like so:

During the Volunteer sign-up, members can add a shift to their schedule, like so:

Lastly, there's a report of the sign-ups:

I've build the Rest endpoints using a more OO programming style, per James' discussions in the Discussions area. I've also tried to follow the new DB standards.

I would like to add a participant's social media links to the db and allow the participant to fill out these fields.

I am considering adding the fields to the ParticipantDetails table. Or I could do a separate table.

Fields I am thinking to add: facebook_link instagram_link linkedin_link tiktok_link twitch_link twitter_link website_link youtube_link other_link

I am also considering where to allow the participant to enter the values. I could modify the profile page and add a section for the links. (I like this best.) Or I could add a separate page. Or I could modify the personal details page, but it's currently labeled as "Optional Demographic Details", which would need to be changed.

Thoughts?

There are several places that Wiscon branding is present on the Brainstorming page.

Things that are working at present:

• Correct site logo from theme displayed in header.
• "Submissions are open for programming for ."

Things that need improving:

• Favicon currently has Wiscon logo. Would be nice if also could take the site theme one. Presumably the same mechanism used for the header logo should work.
• Navigation bar has Wiscon links hard coded. I think this is already available to app, so hopefully this can be added to navigation bar.
• Footer bar has "site maintained by SF3..." hard coded. It would be good if this text could either be defined in db_name or CustomText.
• Sidebar "What are we looking for? WisCon...". Ideally this should be coming from CustomText.
• Page <title> currently hard coded to "WisCon Panel Idea Submission/Brainstorm".

I'm hosting several convention PlanZ sites (although only one is using Brainstorming so far). It would make my life easier if I can deploy one Brainstorming "build", and have customisation through settings/tables.

I want to suggest naming standards for DB objects.

This is a starting point for discussion, so feel free to add or change, or if you have different preference please specify. I'm not too particular on what the standard should be, just that we agree one and follow it consistently.

I also think that now would be a good time to start a refactoring effort, before PlanZ is in use by a lot of conventions.

I've found that the Search Sessions page is not filtering the sessions as requested. For example, when the Track of Literature is selected, all sessions are still being displayed. I've done a little bit of review, but don't see any reason why this is happening. I was wondering if any else is seeing this issue?

This change adds the following tables to the Configuration Table Editor:

• perennial_con_info
• con_info
• con_key_dates

The change adds permission atoms for each table.

It also adds the display_order column to all three tables to enable editing.

Adds a foreign key to con_id on the con_key_dates table.

Added an extra function, lookupVarcharColumn, to the config editor to return the first column of type "varchar" on the table. If no column ends with "name" , lookupNameColumn will return null, this function gets called instead. This should make the configuration editor more flexible, and removes the need for anyone adding a new reference table to understand that it must have a column ending in "name".

I have discovered that there is a bit of an issue between our new naming conventions for tables and with the config table editor. The config table editor has specific code regarding tables that have references to other tables (like RoomHasSet). Our new naming conventions doesn't follow the usual Zambia naming conventions and so the config table editor doesn't work for any new tables with references. As best as I can tell.

I would appreciate it if someone else can check this out and verify what I am thinking is the issue.

I've made a new branch available called: adjust-public-grid-report The public grid report is something that I created years ago for Capricon and then shoehorned in for Zambia. It is not pretty, but is functional. I'm working (slowly) on making it better. Anyway, I had added a field in the Rooms table for divisionid, but I have decided to do something different. I've made a table called room_report_group to identify a "report group" and then a table called room_report_group_has_room to link a set of rooms to a report group. After updating the config table editor code, I find that I get an error when trying to edit the room_report_group_has_room table and I believe it's due to the naming convention differences.

Volunteer shifts are, of course, very con-specific (i.e.: people sign up for a shift at this year's con; that doesn't mean that they also volunteer for the same shift the next year). Conveniently, the volunteer shift table includes a full date (rather than, for example, the Session practice of specifying a time offset). But to make it easier to clearly specify a particular con, I've now linked the volunteer_shift table with the con_info table.

One consequence of this change is that the con_info table must be populated to use volunteer shifts.

This is an exclusively server-side with changes in:

• the database;
• the volunteer REST API implementation; and
• the volunteer report.

The configuration table editor uses foreign keys to populate reference table drop-downs. However, if a referenced (parent) table is empty, the linking (child) table will not display in the configuration table editor. This is fairly reasonable behaviour, since it won't be possible to add rows to the child table until the parent table is populated. However, currently no error message is displayed, so it isn't obvious why the table isn't displaying. This problem could be largely avoided by ensuring there is at least one sample row in all referenced tables. However, in the long term we should try adding logic to display a message such as "You cannot edit table X until table Y has been populated."

Several conventions I'm involved with have used program data to for streaming of virtual/hybrid program, and for displaying future program items on room projector. These take a JSON feed, and are very close to the KonOpas/ConClár feeds. I would like to add optional OBS feeds to the KonOpas/ConClár exports, with configuration settings to control them.

I've been working on a page for editing the site configuration.

On load it carries out the following steps:

• Verifies the user has admin permission.
• Reads the db_name_sample.php file.
• Parses the file, separating any lines before the first define.
• Displays a HTML table listing the setting name, the default value (from sample file), the current live value (from the current active constants), and any comments following.

When Save pressed to save changes, it also carries out the following steps:

• Load the current live db_name.php to get the initial lines before the first define.
• Copy the current live settings to db_name_backup_N.php where N increments by 1.
• Save the prefix lines from the form submitted values with names and comments from sample file to a temporary file.
• Rename temporary file to db_name.php.
• Catch and display any errors when saving.

I'm not quite ready to open a pull request, but I've uploaded the current version to a branch: https://github.com/lostcarpark/PlanZ/tree/ConfigSettings

I'd appreciate if anyone could try it out and provide feedback.

Overall, I'm very happy with how well it works, and it gives admin users the ability to edit configuration without needing to edit the file directly, without needing access to the webserver back end.

Some considerations:

• Currently anyone with the Administrator role can access the page. It may be preferable to create a new privilege so access can be taken away, as not all sites may want to use it.
• Any custom defines not in the sample file will not be retained. This is deliberate, as I feel keeping the sample file in step with the active one is crucial, but if sites are using custom settings, it could cause problems.
• The form does not use an XML template. Adding one would add significant development effort for little gain.
• There is not much validation of the submitted form values at present, as it's assumed it will only be used by trusted administrators. It may be worth adding some additional checks.
• At present the type of the setting is inferred from its value. We may want to add support for additional types, or add more explicit typing, perhaps using the comments.
• I prepare messages when saving the file. However, due to the page redirect, these never get displayed. It would be nice to find a way to display the message after the page reload.