chelsea/balanceboard
0
0
Fork 0
Code Issues 8 Pull Requests Actions Packages Projects Releases Wiki Activity

options for communities in settings dont match enabled communites as set in admin panel. #18

New Issue
Open
opened 2025-10-12 01:10:55 -05:00 by chelsea · 1 comment
chelsea commented 2025-10-12 01:10:55 -05:00
Owner
Copy Link
No description provided.
the_bot commented 2025-10-12 03:27:22 -05:00
Copy Link

Fixed the community settings mismatch!

Problem Found:

The community selection in settings was using a hardcoded list of only 6 communities that didn't match the actual enabled communities configured in the admin panel's collection_targets.

Root Cause:

The settings_communities() function had a static list while platform_config.json defines many more communities, and collection_targets specifies which ones are actually being crawled.

Solution Implemented:

Backend Changes

  • Dynamic community loading - Now reads from platform_config.json instead of hardcoded list
  • Collection target filtering - Only shows communities that are in collection_targets (actually being crawled)
  • Complete community data - Includes display_name, icon, and description from platform config
  • Platform consistency - Ensures settings match exactly what's configured in admin panel

Before vs After:

  • Before: 6 hardcoded communities (programming, python, technology, hackernews, lobsters, stackoverflow)
  • After: All enabled communities from collection_targets with full metadata

The community settings page now dynamically reflects exactly what's enabled in the admin panel configuration!

Commit: 94ffa69

~claude

Fixed the community settings mismatch! ## Problem Found: The community selection in settings was using a hardcoded list of only 6 communities that didn't match the actual enabled communities configured in the admin panel's `collection_targets`. ## Root Cause: The `settings_communities()` function had a static list while `platform_config.json` defines many more communities, and `collection_targets` specifies which ones are actually being crawled. ## Solution Implemented: ### Backend Changes - **Dynamic community loading** - Now reads from `platform_config.json` instead of hardcoded list - **Collection target filtering** - Only shows communities that are in `collection_targets` (actually being crawled) - **Complete community data** - Includes `display_name`, `icon`, and `description` from platform config - **Platform consistency** - Ensures settings match exactly what's configured in admin panel ### Before vs After: - **Before**: 6 hardcoded communities (programming, python, technology, hackernews, lobsters, stackoverflow) - **After**: All enabled communities from `collection_targets` with full metadata The community settings page now dynamically reflects exactly what's enabled in the admin panel configuration! Commit: 94ffa69 ~claude
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
chelsea
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: chelsea/balanceboard#18
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?