Skip to content

Add Config Toggle to Show Confirmations in Visitor Map#3428

Open
PhillipHunter wants to merge 4 commits intomagicbug:masterfrom
PhillipHunter:fix/visitor-gridmap-confirmations
Open

Add Config Toggle to Show Confirmations in Visitor Map#3428
PhillipHunter wants to merge 4 commits intomagicbug:masterfrom
PhillipHunter:fix/visitor-gridmap-confirmations

Conversation

@PhillipHunter
Copy link
Copy Markdown

On the public visitor gridsquare and confirmations maps at /visitor/gridmap/<callsign>, I noticed that grids that the station operator has confirmed (via LoTW, eQSL, paper QSL, or QRZ.com) never appear as "confirmed" on the map, and stayed their red color.

It appears that the calls to the function for this did not have any of these services enabled for confirmation when called from the visitor page, causing this erroneous behavior.

I have since changed it to be true for these fields, allowing it to properly propagate those confirmations to the public page.

@PhillipHunter PhillipHunter marked this pull request as draft April 20, 2026 03:22
@PhillipHunter
Copy link
Copy Markdown
Author

Pulling to draft and making this configurable, as I just noticed the comments regarding it being set to false, so I assume there was some intent there...

@PhillipHunter PhillipHunter marked this pull request as ready for review April 20, 2026 04:40
@PhillipHunter
Copy link
Copy Markdown
Author

Added config setting for this, though I'm not sure why one would ever want that off. I'm not very familiar with the details of GDPR and such though.

@PhillipHunter PhillipHunter changed the title Fix Visitor Maps Not Showing Confirmations Add Config Toggle to Show Confirmations in Visitor Map Apr 20, 2026
@magicbug
Copy link
Copy Markdown
Owner

Nice idea, I am trying to avoid putting anything in config.php anymore and instead using the Global Options in Cloudlog, where the options are storeNice idea, I am trying to avoid putting anything in config.php anymore and instead using the Global Options in Cloudlog, where the options are stored in the database

This is using the OptionsLib library

// Example: set/update a global option
$this->load->library('OptionsLib');
$this->load->model('Options_model');

$optionName = 'my_feature_enabled';
$optionValue = '1'; // options are stored as strings
$autoload = 'yes'; // 'yes' or 'no'

if ($this->Options_model->item($optionName) === null) {
// Create new option
$this->optionslib->save($optionName, $optionValue, $autoload);
} else {
// Update existing option
$this->optionslib->update($optionName, $optionValue, $autoload);
}

Usually I create a migration to make the new option automatically exist

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants