This PR closes #118. The issue was triggered when checking for the user's permissions while booting the addon's CP navigation. The SeoVariablesPolicy requires existing SeoDefaultSet to determine a user's permissions. So if you don't have any SEO sets saved to file yet, you would run into this issue. We can easily fix this by ensuring we always have a set to work with, even if it's not saved to file yet.
This PR closes #118. The issue was triggered when checking for the user's permissions while booting the addon's CP navigation. The
SeoVariablesPolicyrequires existingSeoDefaultSetto determine a user's permissions. So if you don't have any SEO sets saved to file yet, you would run into this issue. We can easily fix this by ensuring we always have a set to work with, even if it's not saved to file yet.