🤬Troubleshooting

Ruh roh. Let’s see why Quicksubs is derping.

For now, I don’t have a huge amount to put here. Please feel free to submit issues in the Github issues repo, however do be patient if I take my time to respond. I have a day job, and this plugin is free. Quicksubs has relatively rudimentary error handling, and you should only ever encounter two error messages:

Uh oh. It looks like the file you chose was either incorrectly formatted, or the wrong file type.

OR...

Oops. It looks like the template does not have any matching text nodes. Have you named them correctly? Remember to prepend "#" to the layer name.

In these instances I would advise that you follow this checklist:

• Have you named your text layers to correspond to the column headings? Remember to prepend the text layer names with a hash (#). So, for a column heading of "Derp", name your text layer "#Derp". Ya derp.

• What software are you using to create your data? Generally I would stick to something reputable, stable, and fit for purpose. Google Sheets ✅ Looks like you put on your big boy pants! Microsoft Excel ✅ The O.G. Nice work. Apple Numbers ⚠️ Make sure to remove extraneous columns and rows, otherwise you may get a lot of blank/unchanged templates in your export. Microsoft Word ⛔ Tell me you’re old without telling me you’re old. Apple Pages ⛔ Do you also double-click on hyper links?

• How many rows does your CSV have? Theoretically, Quicksubs should happily chug away generating images from a good few hundred rows. I haven’t tested it on more than ~400, so I’d be interested to see how it performs with larger loads. All file processing and image generation happens on your computer, so the process time is dependent on the power of your computer, specifically your RAM.

• Did.... you definitely select a CSV file? It will not work with Excel files (xlsx, xls), or Apple Numbers files, ya dingus 🐒

I’ll need to see what issues users report back to me, and I may update this page in future. Good luck!