The expiry settings do not seem to work for listings uploaded through the backend using the admin profile — expired listings still exist and remain visible on the frontend even after the set duration.
Hi,
Sorry for the inconvenience and inconsistency, but this is the expected default behavior. The global expiration setting is intended for listings submitted by users on the front end, so the expiration date is automatically applied. However, listings created in the backend don’t prefill this field, because it’s assumed that only admins have backend access and can set any expiration date they prefer (including leaving it empty or choosing a different value than the global setting).
We understand this may be a bit confusing, and we’ll work on improving the UX in future updates.
Ok makes sense. Is the storage settings global? Or do I have to manually delete after expiry?
The Storage Period starts counting from the expiration date, meaning from the moment a listing changes to Draft status after it expires. For example, if the expiration period is one day and the storage period is three days, the listing will expire tomorrow and switch to Draft, and three days later it will be moved to Trash.
This rule also applies to listings added from the backend, as long as an expiration date is filled. In that case, the listing will become Draft on the expiration date, and after the number of days defined in the storage period, it will be automatically removed.
Hope I helped with your request.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.