You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have set some of my collection backgrounds to a null value when I am unable to locate a nice enough image to use which previously prevented PMM from using whichever image it choose pre 1.3.0. With the latest release, PMM now skips the collection entirely with the message Collection Error: url_background attribute is blank.
The workaround would be to remove the url_background parameter from all collections that do not leverage it but I prefer to leave it in and set to null so that I can quickly search for url_background: null in the future and replace when I come across images I like.
With this said, is this new behavior as designed or unintentional?
The text was updated successfully, but these errors were encountered:
Thats the intended behavior. If you use an attribute but leave it blank I'm assuming you forgot to fill something in so I wanted a message for the user.
I have set some of my collection backgrounds to a null value when I am unable to locate a nice enough image to use which previously prevented PMM from using whichever image it choose pre 1.3.0. With the latest release, PMM now skips the collection entirely with the message
Collection Error: url_background attribute is blank
.The workaround would be to remove the
url_background
parameter from all collections that do not leverage it but I prefer to leave it in and set to null so that I can quickly search forurl_background: null
in the future and replace when I come across images I like.With this said, is this new behavior as designed or unintentional?
The text was updated successfully, but these errors were encountered: