Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fatal Error #223

Open
SylvainLegrand opened this issue May 3, 2023 · 3 comments
Open

Fatal Error #223

SylvainLegrand opened this issue May 3, 2023 · 3 comments

Comments

@SylvainLegrand
Copy link

Nextcloud 26.0.1
Ubuntu 18.04.6
PHP 8.1

Log error PHP :
[03-May-2023 11:47:57 Europe/Paris] PHP Fatal error: Uncaught TypeError: implode(): Argument #1 ($pieces) must be of type array, string given in /mnt/web/nextcloud/apps/richdocumentscode/proxy.php:395
Stack trace:
#0 /mnt/web/nextcloud/apps/richdocumentscode/proxy.php(395): implode(' ', NULL)
#1 {main}
thrown in /mnt/web/nextcloud/apps/richdocumentscode/proxy.php on line 395

@joshtrichards
Copy link
Contributor

@SylvainLegrand What steps, precisely, lead to this error?

@SylvainLegrand
Copy link
Author

Nothing in particular, I just try to open some documents.

@phormix
Copy link

phormix commented Feb 22, 2024

I'm seeing a similar issue, using the Collabora version built into the current NextCloud snap version (27.1.6snap1)

Essentially, the first time an ODT document is created, any content saved will be lost. This includes when manually choosing to save, which gets the graphical feedback that it has succeeded. Once the document is closed and opened, it will be blank and there is no historical copy with data.

If I create the ODT, save, close, and then re-open then all subsequent saves seem to work as expected.
Perhaps there's some issue that doesn't properly associate a reference/ID to the newly created file?

I also note that @SylvainLegrand is referencing something in /mnt. Is your nextcloud+collabora instance using external storage (network or USB etc) of some sort? Maybe it's related to a mounted storage volume (which my instance similarly uses).

I'll also add that I am using Debian (rather than Ubuntu) as my base, and that I also saw this when using a Docker container which is actually one of the reason I decided to see if the Snap behaved better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants