I am getting the same. Please provide a valid fix.
Hey there, @keepsmilyn – apologies, I didn’t see your post earlier. Thanks to @cedashuv for piping in and pushing it to the top of my inbox.
Sorry for crowding up your logs! It looks like this error shows up when the user lands on a custom taxonomy archive, but there is not anything actual wrong going on.
I’ll have a fix for this ready sometime this week.
Hey there!
Sorry this took so long, but this issue should be resolved as of v0.6.4.1.
Let me know if you have any other questions/issues.
Thanks,
Joshua