AprilSylph
commented
1 year ago Hmm, I guess Tumblr added something that Outbox doesn't understand. Ideally we should ignore such content and not render it, rather than crashing. Thanks for the report.
Your saved items are safe (even if they can't be displayed right now) and Outbox will continue saving items as long as you keep the extension enabled.
If you're comfortable using the browser console, you should be able use this command to dump your data manually from the (crashed) Outbox page:
JSON.stringify(await browser.storage.local.get(), null, 2);This will output the same format that usually gets saved to a backup.
From there, if you comb through each item (they're keyed by timestamp, so printed oldest-first) and find an item with a content block with an attribution property which itself has a type that isn't "post", "link", "blog" or "app", you could delete that item from your outbox and it should render again after a refresh:
// e.g. if the problem item's key is "1636578098748"
browser.storage.local.remove('1636578098748');(There may be multiple problem items, so you'd have to search for all items with that attribution type and repeat as necessary.)
However, the problem would recur if another item with the same attribution type was saved.
I have no idea what it would be, though
cchase503
marcustyphoon
Platform
macOS 13.3.1
Browser
Chrome 114
Addon version
1.0.3
Details
Outbox is completely blank with this message: "TypeError: attributionRenderers[attribution.type] is not a function". I did completely clear my cache recently, does this mean it's impossible to get my old messages back without having saved a backup? How do I get it working again?