Undefined Behavior for Custom Formatted xlsx linked Spreadsheet

Aberta
#3,804 1 comentário 1 reação 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
javascript
Domínio
backend, data

Direção de pesquisa

Start by examining the spreadsheet response export and row-append entry points; the issue does not name files or tests. Reproduce with a formatted, linked XLSX file containing an added column, then submit a response after upgrading from Forms 5.2.4 to 5.4.1. Done means existing spreadsheet contents and formatting remain intact and the new answer is appended as a row.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

0. Needs triage bug needs info

Please use the 👍 reaction to show that you are affected by the same issue. Please don't comment if you have no relevant information to add!

Describe the bug
On upgrade to newer version of nextcloud when the linked spreadsheet is formatted via the nextcloud office or a local microsoft excel app, the whole table is wiped.
After that unlink and relink it to a new spreadsheet then formatting it as desired, no new row is going to be added.

To Reproduce
Steps to reproduce the behavior:

one quick note: consider that we are using complex English-Persian language to fill out forms.

  1. Create a form from an older version - forms-v5.2.4.tar.gz
  2. Fill out the form with a couple of answers.
  3. Link the responses to a xlsx spreadsheet.
  4. Format the spreadsheet using your desired excel application.
  5. Add new column at the end as well.
  6. Save and sync the spreadsheet.
  7. Upgrade the forms to version 5.4.1
  8. Add a new response
  9. You should that the entire form is wiped out except the title.
  10. If you try and relink it to an entire file then formatting it as desired, no new row is going to be added

Expected behavior New answers should be saved at the end of the sheets.

Screenshots
Unfortunately a screenshot of a wiped clean spreadsheet is not going to be helpful.

Nextcloud (please complete the following information):

  • Nextcloud-Version: 33.0.10
  • Forms-Version: 5.2.4 upgraded to 5.4.1

Desktop (please complete the following information):

  • OS: Linux Server -- Windows, iOS, Android clients.
  • Browser Any
  • Version [e.g. 22]

Smartphone (please complete the following information):

  • Device:
  • OS:
  • Browser
  • Version

Browser log
After re-exporting to spreadsheet for multiple times:

index.mjs:44 [WARN] viewer: Some mimes were ignored because they are not enabled in the server previews config Object
log @ index.mjs:44
index.mjs:47 [ERROR] viewer: The following mime is already registered Object
log @ index.mjs:47
search.js:22 Initializing unified search plugin-filters from talk
NotificationsApp.vue:455 Notifications permissions denied
NotificationsApp.vue:230 Has notify_push enabled, slowing polling to 15 minutes
NotificationsApp.vue:412 Polling interval updated to 900000
NotificationsApp.vue:279 Started background fetcher as session_keepalive is enabled
NotificationsApp.vue:368 Got notification data, restoring default polling interval.
index.mjs:44 [WARN] @nextcloud/vue: Found no locale to load. Object
log @ index.mjs:44

Additional context
Everything was fine in the last version.

Linguagem predominante
JavaScript
Estrelas
385
Forks
133
Merge médio
7h 54min
PRs com merge (30d)
157

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de nextcloud/forms

Todas as issues de nextcloud/forms

Issues semelhantes

Mais issues de JavaScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.