Users can now enable or disable helpful tooltips throughout the interface from their profile settings.
- Per-User Tooltip Preference - Enable/disable tooltips in profile settings under "Interface Help"
- Global Tooltip System - Automatically initializes Bootstrap tooltips based on user preference
- Helpful Hints - Tooltips on key navigation elements (Quick Add, theme toggle) and dashboard features (device toggle, map controls)
- Default Enabled - Tooltips enabled by default for all users
- Added
tooltips_enabledboolean field to UserProfile model (default=True)
cd /home/administrator
git pull origin main
python manage.py migrate # Runs migration accounts.0011_add_tooltips_enabled
sudo systemctl restart clientst0r-gunicorn.service- Update to v2.25.1 and run migration
- Go to Profile → Edit Profile
- Scroll to "Interface Help" section
- Toggle "Enable Helpful Tooltips" checkbox
- Save changes
RMM devices with location data now display on the dashboard location map with status-based markers.
- Device Map Layer - Toggle to show/hide RMM devices on location map
- Status Markers - Green for online devices, red for offline
- Device Popups - Click markers to see device details
- GeoJSON API - Organization and global device location endpoints
- Auto Location Parsing - Extracts coordinates from location, gps_location, or coordinates fields
- Added
latitudeandlongitudefields to RMMDevice model - Created index on lat/lon fields for query performance
cd /home/administrator
git pull origin main
python manage.py migrate # Runs migration 0006_add_device_location_fields
sudo systemctl restart clientst0r-gunicorn.serviceYour RMM must provide location data in format: "lat,lon" (e.g., "-32.238923,101.393939")
- Update to v2.25.0 and run migration
- Sync your RMM connection to import device locations
- Go to Dashboard → Location Map
- Click "Show Devices" button to display device layer
CRITICAL BUG: Fixed template syntax error that broke all pages in v2.24.126.
v2.24.126 introduced a Django template syntax error using parentheses in an if statement:
{% if global_kb_enabled and (is_staff_user or user.is_superuser) %}Django templates don't support parentheses for grouping logic, causing:
TemplateSyntaxError: Could not parse the remainder: '(is_staff_user' from '(is_staff_user'
Nested the if statements properly:
{% if global_kb_enabled %}
{% if is_staff_user or user.is_superuser %}
...
{% endif %}
{% endif %}- v2.24.126: Broke ALL pages with base.html template
- v2.24.127: Fixed - all pages working again
cd /home/administrator
git pull origin main
sudo systemctl restart clientst0r-gunicorn.serviceIf you're on v2.24.126, upgrade to v2.24.127 immediately!
Fixed issue where organization dropdown wasn't showing all available organizations for some users.
- Superusers not seeing all organizations - Superusers were not automatically seeing all orgs unless they were also marked as staff users
- Inactive organizations appearing - Org users could see organizations that were marked as inactive if they had an active membership
- Middleware not respecting superuser status - Organization middleware wasn't checking
is_superuserflag
- Context Processor: Added
request.user.is_superusercheck to show all organizations - Context Processor: Added
organization__is_active=Truefilter for org users - Middleware: Added
is_superusercheck for organization access - Middleware: Added
organization__is_active=Truefilter when auto-selecting organization
- Superusers: Now properly see all active organizations in dropdown
- Org Users: No longer see inactive organizations even if they have memberships
Before: Only staff users (user_type=STAFF) saw all organizations After: Both superusers AND staff users see all organizations
cd /home/administrator
git pull origin main
sudo systemctl restart clientst0r-gunicorn.serviceFixed browser console errors and form validation issues on document creation/editing pages.
- "An invalid form control is not focusable" error - The body textarea was marked as required but hidden by the WYSIWYG editor, preventing form submission
- Autocomplete warning - GitHub token field in bug report modal was missing autocomplete attribute
- Form submission failures - Users couldn't submit document forms due to hidden field validation
- Document Forms: Removed HTML5
requiredattribute from hidden textarea when WYSIWYG editor is active - Validation: Added JavaScript validation before form submission to ensure content exists
- Autocomplete: Added
autocomplete="off"to GitHub token password field - Consistency: Applied fixes to all document form templates (documents, global KB, templates)
docs/forms.py- Added data-required attributetemplates/docs/document_form.html- Fixed validationtemplates/docs/global_kb_form.html- Fixed validationtemplates/docs/template_form.html- Fixed validationtemplates/base.html- Added autocomplete attribute
- Forms now submit correctly without browser validation errors
- Clear alert message if content is empty on submission
- No more console warnings about form controls
cd /home/administrator
git pull origin main
sudo systemctl restart clientst0r-gunicorn.serviceUpdated error handling in RMM and PSA integrations to provide correct guidance when encryption errors occur.
When users encountered encryption errors (typically during Tactical RMM setup or password operations), the error message incorrectly suggested regenerating the APP_MASTER_KEY. This wasn't the right solution!
Encryption errors usually mean the Gunicorn service isn't loading the .env file containing the APP_MASTER_KEY environment variable.
Now when encryption errors occur, users see clear instructions:
- Run the fix script:
./scripts/fix_gunicorn_env.sh - Or run diagnostic:
./diagnose_gunicorn_fix.sh - Link to GitHub Issue #4 for full details
- All RMM integration views (create, edit, sync, test)
- All PSA integration views (create, edit, sync, test)
- Error messages now link to the correct fix scripts
- Added reference to Issue #4 for documentation
cd /home/administrator
git pull origin main
sudo systemctl restart clientst0r-gunicorn.serviceAdded Feature Toggles in Admin Settings to enable or disable major system features. When disabled, features won't appear in the navigation menu and will be inaccessible.
- Monitoring - Website & Service Monitoring, SSL tracking, expiration tracking
- Global Knowledge Base - Staff-only shared knowledge base across organizations
- Workflows & Automation - Process definitions and automated execution
- Admin dropdown → System Settings → Feature Toggles
- Toggle features on/off with simple switches
- Changes apply immediately after saving
- Simplified UI - Hide features you don't use to reduce menu clutter
- Focus on What Matters - Keep only the tools your team needs visible
- Flexible Configuration - Enable/disable features as your needs change
- Feature toggles stored in SystemSetting model
- Context processor makes toggles available to all templates
- Navigation menu conditionally hides disabled features
- Backward compatible - all features enabled by default
cd /home/administrator
git pull origin main
python manage.py migrate
sudo systemctl restart clientst0r-gunicorn.serviceAdded a diagnostic script that tells you EXACTLY what's wrong and how to fix it!
cd /home/administrator
git pull origin main
./diagnose_gunicorn_fix.sh- ✅ Checks if .env file exists and has APP_MASTER_KEY
- ✅ Checks if Gunicorn service file exists
- ✅ Checks if EnvironmentFile is configured (THE FIX)
- ✅ Tests if sudo permissions are configured
- ✅ Tells you EXACTLY what command to run to fix it
- If fix is already applied: Just restart Gunicorn
- If sudo not configured: Shows exact command to configure it
- If fix needs to be applied: Tells you to run
./scripts/fix_gunicorn_env.sh
The red alert in the web UI only checks if systemctl status works, but the fix needs sudo tee permission. This diagnostic checks BOTH!
The Gunicorn fix script was using sudo sed and sudo cp commands that weren't in the sudoers permissions, causing it to fail silently during web-based updates.
The fix: Changed the script to use only sudo tee, sudo systemctl, and sudo grep - commands that ARE in the sudoers permissions!
- Script reads the service file with
awk(no sudo needed) - Modifies the content in memory
- Uses
sudo teeto write (which IS allowed in sudoers) - Reloads and restarts service
# From web UI:
Admin → System Updates → Click "Apply Update"
# The fix script will NOW work correctly!- ✅ Demo data import encryption errors
- ✅ Password creation/editing from web UI
- ✅ All environment variable operations
- Old script: Used
sudo sed -iandsudo cp(not in sudoers) - New script: Uses
sudo tee(IS in sudoers) - Result: Fix actually applies during web-based updates!
This is a test release to verify the complete one-click update system works end-to-end!
On Systems WITHOUT Sudo Configured:
- Go to Admin → System Updates
- You should see a RED ALERT with the exact sudo command
- Copy and run the command shown
- Refresh the page - alert should disappear
- Click "Check for Updates" - should show v2.24.120 available
- Click "Apply Update" - should update automatically
On Systems WITH Sudo Already Configured:
- Go to Admin → System Updates
- No red alert (sudo already configured)
- Click "Check for Updates" - should show v2.24.120 available
- Click "Apply Update" - should update automatically
What Happens Automatically:
- ✅ Pulls v2.24.120 code
- ✅ Runs migrations
- ✅ Runs Gunicorn fix script (if present)
- ✅ Installs dependencies
- ✅ Collects static files
- ✅ Restarts Gunicorn service
- v2.24.120: Test release (version bump only)
- All functionality from v2.24.119 included
The System Updates page now shows a PROMINENT ALERT if passwordless sudo is not configured, with the exact command users need to run!
Web UI (Easiest):
- Admin dropdown → System Updates
- If you see a red alert, copy and run the command shown (one-time setup)
- Refresh the page
- Click "Check for Updates"
- Click "Apply Update"
- Done!
- ✅ Added sudo configuration check to System Updates page
- ✅ Shows prominent red alert if sudo is not configured
- ✅ Displays exact command users need to run
- ✅ Clear instructions: run command → refresh page → click update
- ✅ No more guessing or hidden errors!
- Users who don't read documentation
- Clear guidance right in the UI where it's needed
- One-time setup is obvious and easy to follow
Click the Update button in the web UI and EVERYTHING happens automatically - including the critical Gunicorn fix!
- Admin dropdown → System Updates
- Click "Check for Updates"
- Click "Update Now"
- Done! The update automatically:
- ✅ Pulls latest code
- ✅ Runs migrations
- ✅ Applies Gunicorn environment fix
- ✅ Installs dependencies
- ✅ Collects static files
- ✅ Restarts Gunicorn service
For web-based updates to work, configure passwordless sudo ONCE:
sudo tee /etc/sudoers.d/clientst0r-auto-update > /dev/null <<'SUDOERS'
administrator ALL=(ALL) NOPASSWD: /bin/systemctl restart clientst0r-gunicorn.service, /bin/systemctl status clientst0r-gunicorn.service, /bin/systemctl daemon-reload, /usr/bin/systemd-run, /usr/bin/tee /etc/systemd/system/clientst0r-gunicorn.service
SUDOERS
sudo chmod 0440 /etc/sudoers.d/clientst0r-auto-updateAfter this one-time setup, all future updates are ONE CLICK!
cd /home/administrator && ./update.sh- ❌ Demo data import failures
- ❌ Password encryption errors
- ❌ Any environment variable issues
The update process now includes an explicit step to run the Gunicorn environment fix script, ensuring the fix is applied even if the migration doesn't have sudo permissions.
Set up passwordless sudo once on each server, then all future updates are just clicking a button in the web UI!
The critical Gunicorn environment fix from v2.24.113/116 now applies automatically when you run the update script!
cd /home/administrator && ./update.shThat's it! The update script automatically:
- ✅ Pulls latest code from GitHub
- ✅ Runs database migrations (which applies the Gunicorn fix)
- ✅ Installs/updates dependencies
- ✅ Collects static files
- ✅ Restarts Gunicorn service
- ✅ Verifies service is running
- ❌ Demo data import failures
- ❌ Password encryption errors
- ❌ Any feature requiring environment variables from .env file
The migration automatically:
- Runs the fix_gunicorn_env.sh script
- Adds
EnvironmentFile=/home/administrator/.envto Gunicorn service - Reloads systemd daemon
- Restarts Gunicorn
This update is designed for administrators managing multiple Client St0r servers. Run the same single command on all servers - everything happens automatically!
No problem! The migration detects if the fix is already applied and won't duplicate the configuration.
Error you might see:
Error: Demo data import failed: Encryption failed: Invalid APP_MASTER_KEY format: Incorrect padding
cd /home/administrator
./scripts/fix_gunicorn_env.shThat's it! This fixes:
- ❌ Demo data import failures
- ❌ Password encryption errors
- ❌ Any feature requiring environment variables from .env file
- 📢 Emphasizes the critical Gunicorn environment fix
- 📚 Provides clear, simple instructions
- ✅ Includes the fix script (from v2.24.113)
If you've already run ./scripts/fix_gunicorn_env.sh after v2.24.113, you're good! This version just makes the instructions clearer for others.
Users can now report bugs from Client St0r! Click username dropdown → Report Bug.
Features:
- Submit title, description, steps to reproduce
- Upload screenshots (max 5MB)
- Auto-collect system information
- Use system GitHub PAT or your own credentials
cd /home/administrator
git pull origin main
python manage.py migrate
sudo systemctl restart clientst0r-gunicorn.service- Removed duplicate "System Updates" link from settings sidebar
- System Updates now only in Admin dropdown menu
Demo data import was failing with error:
Encryption failed: Invalid APP_MASTER_KEY format: Incorrect padding
This occurred when:
- Importing demo data from the web UI
- Creating/editing passwords from the web UI
- Any operation requiring encryption through the web interface
Command line operations worked fine - only web UI operations failed.
The Gunicorn systemd service was not configured to load the .env file, so the APP_MASTER_KEY environment variable was not available to the Django application when running through the web server.
Add EnvironmentFile=/home/administrator/.env to the Gunicorn service configuration.
cd /home/administrator
./scripts/fix_gunicorn_env.shThis script will:
- ✅ Check if the service file exists
- ✅ Verify .env file exists
- ✅ Backup the service file
- ✅ Add EnvironmentFile configuration
- ✅ Reload systemd and restart Gunicorn
- ✅ Verify the service started successfully
- Edit the service file:
sudo nano /etc/systemd/system/clientst0r-gunicorn.service- Add this line after the
Environment="PATH=..."line:
EnvironmentFile=/home/administrator/.env- The result should look like:
[Service]
Type=notify
User=administrator
Group=administrator
WorkingDirectory=/home/administrator
Environment="PATH=/home/administrator/venv/bin"
EnvironmentFile=/home/administrator/.env
ExecStart=/home/administrator/venv/bin/gunicorn \
...- Reload and restart:
sudo systemctl daemon-reload
sudo systemctl restart clientst0r-gunicorn.serviceAfter applying the fix:
- Go to Settings → General Settings
- Click "Import Demo Data"
- You should see: "✓ Demo data imported successfully!"
- Refresh the page
- Switch to "Acme Corporation" organization
- Verify you see:
- 5 Documents
- 3 Diagrams
- 10 Assets
- 5 Passwords
- 5 Workflows
This fix is required for any system where the Gunicorn service was set up before v2.24.113. The fix script is idempotent and safe to run multiple times.
- Removed background threading from demo data import
- Made import synchronous for better error handling
- Automatic organization switching after import
- Improved success/error messages
- Import completes in 2-3 seconds
cd /home/administrator
git pull origin main
sudo systemctl restart clientst0r-gunicorn.serviceSee git commit history for older version notes.