Web appOpen in Telegram
LLibreSign

LibreSign

@LibreSign · group · Tech · indexed since 2026-07-25
258members
4 211messages in the index
V
Iniciando agora uma chamada para falar de fundos de financiamento de projetos livres.
A
Boa noite galera! Agradeço o convite para participar do grupo. Como coloquei na issue que fiz lá no repositório, conheci o projeto após uma breve apresentação do BBSIA (Banco Brasileiro de Soluções em IA) pelo TCE-SP aqui na cidade de São Jose dos Campos, onde tivemos o convite para cadastrar um projeto nosso no banco - que trata de patrimônio público. Espero poder aprender e contribuir aqui com vocês. E mais uma vez, parabéns pelo projeto!
  1. V
    Fala ae! Boa tarde! Se desejar, podemos parear em uma chamada de vídeo aqui no grupo para ver a issue que abriu.
Whole thread · 2 replies →
A
Ah, perdão, não me apresentei - me chamo André Maia, no github estou como maia-andre, e sou servidor público da prefeitura de São Jose dos Campos. Minha área de formação é logística e dados. Hoje estou empenhado no setor de licitações e inovações tecnológicas. Desenvolvo por curiosidade e entusiasmo.
Whole thread · 1 reply →
R
Hi everyone, I am running: Nextcloud: 34.0.3 LibreSign: 14.1.0 PHP: [8.3.6] Linux server I am having an issue with the LibreSign signing workflow. Previously, the workflow I expected/used was: Upload PDF ↓ Add signer ↓ Next ↓ Open PDF ↓ Drag/place the signature field on the PDF ↓ Send But currently the workflow is: Upload PDF ↓ Add signer ↓ Signature Request / Request ↓ Open file The signature-positioning step is no longer appearing before sending the request. I upgraded Nextcloud from 31.0.7 to 34.0.3, but the workflow remained the same. LibreSign is still 14.1.0. My question Is this the expected workflow for LibreSign 14.1.0, or was there a previous LibreSign version that used the workflow with the PDF signature-placement step before sending? If the old workflow is still supported, how can I restore it? I would prefer not to modify the JavaScript manually unless there is a documented fix. Any help identifying the LibreSign version, configuration, or code responsible for this workflow would be greatly appreciated. Thanks.
  1. V
    Hi! The signature-positioning step still exists in 14.1.0, it's the "Setup signature positions" button in the LibreSign sidebar. It only shows up when the signature stamp feature is available (either a signature background image or a non-empty signature text template).
Whole thread · 1 reply →
  1. R
    === signature_background_type === deleted === signature_text_template === ==== libresign.config.sign-elements.is-available=== "sign-elements": { "is-available": false, "can-create-signature": true, "full-signature-width": 400, "full-signature-height": 200, "signature-width": 400, "signature-height": 200
Whole thread · 1 reply →
V
Two more things that would help: 1. Which LibreSign version were you on when the "Next → place signature on PDF → Send" flow worked? That wording matches LibreSign 11.x, so I'd like to confirm whether you upgraded LibreSign as well, or only Nextcloud. 2. In the sidebar, do you see the "Request signatures" button but no "Setup signature positions" button? If is-available comes back as false, restoring the default signature background or the signature text template in the admin settings brings the positioning step back, no JavaScript changes needed.
  1. R
    Photo
    click to show
    1-i was on Next Cloud 31.0.7 and libresign 11.0.6 after installed it one or 2 days i found the next button was replacement with request signature. Upgrade the next cloud to 34.0.3 and remove libresign 11.0.6 and installed it from hub next cloud app store version 14.0.3 and the problem still exist.
Whole thread · 1 reply →
Whole thread · 2 replies →
V
On your server, the signature background is set to deleted and the signature text template is empty. LibreSign 14 hides the signature position step when both are missing. That is why the button is not there.
V
You can fix it in the interface, no commands needed: Go to Administration settings → LibreSign Open the "Signature stamp" section Under "Background image", click the "Reset to default" button Then reload the page. The "Setup signature positions" button should appear again, above "Request signatures".
V
We also think our rule is too strict here, because your can-create-signature is still true, which means your signers can draw a signature. We are fixing that on our side, so this will work by default in a future version.
V
Your report actually helped us find a real bug, so thanks for the details. We are fixing it.
V
I'm the main maintainer of LibreSign and CTO at @LibreCodeCoop, a small cooperative based in Brazil. We also offer paid support and custom development for companies, in case you ever need it, fell free to contact us.
V
Link
click to show
Hoje vou trabalhar em 2 frentes: - Hardering de WordPress - Preparar ambiente de desenvolvimento para Nextcloud / LibreSign para usar Nginx proxy, dica do @eusousu Quem desejar chegar junto, só entrar na chamada de vídeo e dar um oi para interagir.

An open public feed from the search index ChatCrawler — “Google for public Telegram”; refreshed as the venue is crawled. Times are UTC.

Public content only, official Telegram API. About · FAQ · What we do not do · Remove a page · Catalog · Search · How we count