Replies: 2 comments
-
I found a way to temporarily solve the problem by not doing asynchronous processing temporarily, so I will share it. Make the following settings in PICTURES = {
"BREAKPOINTS": {
"xs": 576,
"s": 768,
"m": 992,
"l": 1200,
"xl": 1400,
},
"GRID_COLUMNS": 12,
"CONTAINER_WIDTH": 1200,
"FILE_TYPES": ["WEBP"],
"PIXEL_DENSITIES": [1, 2],
"USE_PLACEHOLDERS": False,
"QUEUE_NAME": "pictures",
"PROCESSOR": "pictures.tasks._process_picture", # Change here !
} Change |
Beta Was this translation helpful? Give feedback.
-
Hi there 👋, Thanks for reaching out. In your second comment, you simply switched to synchronous processing. Which will work, but I wouldn't recommend. I believe the solution is simple and – maybe not well enough – documented:
If you need any assistance, please don't hesitate to reach out here on the Celery community. Cheers! |
Beta Was this translation helpful? Give feedback.
-
The task is loaded, but when I sent the image through the admin site, nothing happened.
Another task I implemented will be executed without problems, and there seems to be no problem with Celery.
Beta Was this translation helpful? Give feedback.
All reactions