Closed
Description
Describe the bug
The "Groups to Import" dropdown is blank but the 7 or 8 groups that I had previously selected are still being imported correctly on each run. I have the "preprocess playlist" ticked and I can confirm the process is working as I still see channels being added and removed from the list. When I go back in to modify the groups the list is blank and it shows nothing is selected.
I also notice that the "ignored file types" I had previously set are now blank. If I add them again and press save they are gone again when i refresh.
To Reproduce
Steps to reproduce the behavior:
- Setup the system and everything was working fine
- Returned to the Processing page on the playlist and the groups to import is blank
Expected behavior
I would expect to see the groups as I have in the past so I can remove or add new ones
Actual behavior
see screenshot
Screenshots
showing the playlist with the channels and groups
docker-compose.yml contents
services:
m3u-2:
image: sparkison/m3u-editor:latest
container_name: m3u-2
environment:
- TZ=Etc/EST
- APP_URL=http://10.2.1.114 # or http://192.168.0.123 or https://your-custom-tld.com
# This is used for websockets and in-app notifications
# Set to your machine/container IP where m3u editor will be accessed, if not localhost
- REVERB_HOST=localhost # or 192.168.0.123 or your-custom-tld.com
- REVERB_SCHEME=http # or https if using custom TLD with https
volumes:
# This will allow you to reuse the data across container recreates
# Format is: <host_directory_path>:<container_path>
# More information: https://docs.docker.com/reference/compose-file/volumes/
- /disk1/docker/m3u-2/data:/var/www/config
restart: unless-stopped
ports:
- 36400:36400 # app
- 36800:36800 # websockets/broadcasting
Container/Host Logs
⚡️ Starting app at: http://10.2.1.114:36400
cp: cannot stat '/usr/share/zoneinfo/Etc/EST': No such file or directory
📅 Timezone set to Etc/EST. Current date/time: Sun May 4 23:54:24 UTC 2025
🔑 App key check confirmed
✅ No updates available.
INFO Caching framework bootstrap, configuration, and metadata.
config ........................................................ 24.87ms DONE
events ......................................................... 1.46ms DONE
routes ........................................................ 33.80ms DONE
views ........................................................ 347.16ms DONE
blade-icons ................................................... 25.42ms DONE
filament ...................................................... 20.69ms DONE
INFO Application is already up.
🗂️ Enabling SQLite WAL mode...
The 'sqlite' connection has been set as [wal] journal mode.
💾 Running migrations...
INFO Nothing to migrate.
🛠️ Building assets...
up to date, audited 208 packages in 816ms
42 packages are looking for funding
run `npm fund` for details
3 vulnerabilities (2 moderate, 1 high)
To address all issues, run:
npm audit fix
Run `npm audit` for details.
> build
> vite build
vite v6.0.3 building for production...
transforming...
✓ 12 modules transformed.
rendering chunks...
computing gzip size...
public/build/manifest.json 0.20 kB │ gzip: 0.14 kB
public/build/assets/app-mvnv8j6y.css 117.24 kB │ gzip: 16.38 kB
public/build/assets/app-DUaD4pXU.js 132.18 kB │ gzip: 39.22 kB
✓ built in 1.35s
🚀 Starting services...
2025-05-04 23:54:29,112 INFO Set uid to user 0 succeeded
2025-05-04 23:54:29,113 INFO supervisord started with pid 1
2025-05-04 23:54:30,115 INFO spawned: 'crond' with pid 84
2025-05-04 23:54:30,117 INFO spawned: 'redis' with pid 85
2025-05-04 23:54:30,118 INFO spawned: 'php-fpm' with pid 86
2025-05-04 23:54:30,120 INFO spawned: 'nginx' with pid 87
2025-05-04 23:54:30,121 INFO spawned: 'websocket' with pid 88
2025-05-04 23:54:30,122 INFO spawned: 'queue' with pid 89
2025-05-04 23:54:31,328 INFO success: crond entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-05-04 23:54:31,328 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-05-04 23:54:31,328 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-05-04 23:54:31,328 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-05-04 23:54:31,328 INFO success: websocket entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-05-04 23:54:31,328 INFO success: queue entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)