Error previewing findings

[SolomonSklash]

I am getting the following error page when I click the "Preview" icon on a finding :

You don't have a Finding Template (did you delete the default one?) -_- ... If you're an admin go to here to add one.

To reproduce:

• Create a new report
• Click "Add Finding from Templates"
• Pick any finding and click the "Preview" icon.
• This throws error message above.
• Go back from the error page and check any finding and click "Add".
• Click the "Preview" icon
• This throws error message above.

Additionally, I am constantly getting Haml::TempleEngine: Option :encode_html is invalid in the console.

When installing serpico, via serpico_1.3.0_amd64.deb, I picked yes when it asked "Would you like to initialize the database with templated findings? (Y/n)"

I am running serpico in a Debian container on Proxmox. I've removed and reinstalled a few times and it has not resolved the issue.

[BuffaloWill]

@bellma101 it looks the finding template didn't initialize properly, I will look into that as a bug as this looks like a regression. To fix manually go to Admin > List Report Templates and click on the Edit button for "Default Finding". For "Choose File" select 'Serpico Finding.docx' that ships with Serpico in the "templates/" directory or download it here "https://github.com/SerpicoProject/Serpico/blob/master/templates/Serpico%20-%20Finding.docx". Make sure you enable the "Finding Template" checkbox_. The issue should be fixed after this.

As to the "encode_html" error, it is harmless but something that is an open issue to fix (#441).

[SolomonSklash]

Thanks for the quick response. Unfortunately, your steps for fixing the issue didn't work for me. I re-downloaded the docx and rebooted the VM and restarted Serpico, but no luck.

[SolomonSklash]

I tried deleting the existing Default Finding and recreating it with the docx and it is now working.

[chppppp]

This issue is a show stopper for me. I cannot get Serpico working at all.

Edit: taking the docx above and adding it as a new template under a new name then using that template name in a report works. The issue seems to be just with the default template on a default install.