Last working config?

[ntinti]

Whats the last working config on debian This one ? ####################################### set_core_regex='cp-6.0$' set_online_regex='collabora/collabora-online-4-0-4$' lo_src_branch='distro/collabora/cp-6.0' lo_src_tag='cp-6.0-30' #######################################

[joergmschulz]

what did you do to make that work????

[DmDS]

Im now on version 6.4.6, but i cant see anything of the new UI.

change classic to notebookbar in loolwsd.xml

 <user_interface>
      <mode type="string" desc="Controls the user interface style (classic|notebookbar)" default="classic">notebookbar</mode>
    </user_interface>

[Alternativend]

what did you do to make that work????

Basically nothing. I have just uploaded the file under Settings -> LibreOffice Online Personal -> Global Templates

@DmDS Your right, its working. Thanks!

[joergmschulz]

Hmmmm, the template thing doesn't work for me. Still. Can you open/edit such template files online, or will these files get downloaded instead of editing them (as it happens here) ?

[titansmc]

Hi, With the last config working posted here I get:

(anonymous namespace)::Test::test finished in: 0ms
osl_File.cxx:267:Assertion
Test name: osl_FileBase::SystemPath_FileURL::getSystemPathFromFileURL_005
assertion failed
- Expression: (osl::FileBase::E_None == nError) || (nError == osl::FileBase::E_NOENT)
- In deleteTestDirectory function: remove Directory file:///tmp/????'??
                                                                       Makefile:282: recipe for target 'build' failed
make: *** [build] Error 2

Does anyone have an idea of what this mean? I've tried to clean caches, remove compiling directories....

[DmDS]

this config uses collabora online (6.4.0-15) instead of libreoffice online (since September 30, after version 6.4.0-4, for some reason it is not updated). the sidebar is now hidden by default. unfortunately, I still have a problem with opening new documents.

set_name='collabora'
set_core_regex='cp-6.4'
set_online_regex='co-6-4'
lo_src_repo='https://github.com/LibreOffice/core.git'
lo_src_branch='distro/collabora/cp-6.4'
lo_src_commit=''
lo_src_tag='cp-6.4-11'
lo_dir="/opt/libreoffice"
lo_forcebuild=true
lo_non_free_ttf=true
poco_version=$poco_version_latest
poco_forcebuild=false
lool_src_repo="https://github.com/CollaboraOnline/online.git"
lool_src_branch='distro/collabora/co-6-4'
lool_src_tag='cp-6.4.0-15'
lool_dir="/opt/lool"
lool_configure_opts="--disable-werror --with-lokit-path=${lo_dir}/include"
lool_logfile='/var/log/loolwsd.log'
lool_prefix='/usr'
lool_sysconfdir='/etc'
lool_localstatedir='/var'
lool_forcebuild=true
lool_maxcon=200
lool_maxdoc=100
loolwsd_service_name='loolwsd'

[joergmschulz]

Assuming the issue 'opening new documents' is: New documents can't be opened from templates: Does anybody have any idea here? Still, using the 'official' CODE docker files, this works. See https://bugs.documentfoundation.org/show_bug.cgi?id=135536

[husisusi]

Assuming the issue 'opening new documents' is: New documents can't be opened from templates: Does anybody have any idea here? Still, using the 'official' CODE docker files, this works. See https://bugs.documentfoundation.org/show_bug.cgi?id=135536

Could you test it unencrypted? http://? Just testing

[DmDS]

Could you test it unencrypted? http://? Just testing

http is working

[husisusi]

http is working

Interesting!

[joergmschulz]

so a SSL issue - shot in the dark: content security policy?

[husisusi]

unfortunately, I still have a problem with opening new documents.

To be clear, creation of documents from templates or just new document?

[joergmschulz]

in my case: only template documents.

[husisusi]

I am using Collabora OfficeDev 6.2-14 and loolwsd 4.2.4 with the APP version 3.7.8 and it works with ots template format. Update: it works with xltx template too.

[DmDS]

To be clear, creation of documents from templates or just new document?

just new document.

i guess it looks for a template and throws an error. and after commenting out this line the template URL is blank. and creation works. $response['TemplateSource'] = $templateUrl;

[joergmschulz]

Content Security Policy: Die Einstellungen der Seite haben das Laden einer Ressource auf data: blockiert ("media-src"). Content Security Policy: Die Einstellungen der Seite haben das Laden einer Ressource auf eval blockiert ("script-src").

[DmDS]

maybe this has something to do with it

https://gerrit.libreoffice.org/c/core/+/96652

[husisusi]

Content Security Policy: Die Einstellungen der Seite haben das Laden einer Ressource auf data: blockiert ("media-src"). Content Security Policy: Die Einstellungen der Seite haben das Laden einer Ressource auf eval blockiert ("script-src").

Is this nginx, apache or lool log? Are you using the Proxy in the same Server?

[joergmschulz]

That's the browser console log. Changing the officeonline version to an older one removes the issue. Proxy is difficult here, I have nc under docker under traefick for test and under apache for prod, the same behaviour for both. So we don't have a dependency here.

[DmDS]

I have collabora and nextcloud (apache) on separate servers. tried with and without a proxy on both, with and without ssl termination. with self-signed certificates and with let's encrypt. the problem is exactly with templates. if you don't load your templates, there are standard ones in richdocuments / assets. when creating a new document, collabora cannot access these templates and takes an empty document (not a template) from the same richdocuments / assets folder. If you comment out the line that I wrote above, then collabora does not find any templates (because the link to them does not lead anywhere) and immediately creates a new document from an empty file.

[DmDS]

I found a solution! need to add with-webdav=serf to default.cfg

and recompile

[husisusi]

I found a solution! need to add with-webdav=serf to default.cfg

and recompile

@DmDS Thank you! @joergmschulz can you please check this?

[joergmschulz]

Sorry, must revoke: it worked ONCE, but subsequent document creations failed.

recompiled. Believe it or not. @DmDS You are a Hero. It seems to work here.

[DmDS]

I have no problem on multiple devices... did you compile the same versions as before?

[joergmschulz]

Hmmm, could you post your default.cfg? Did you recompile poco as well?

[DmDS]

i did not recompile poco (ver 1.10.1) try to clean cache. js scripts are cached for a very long time until the version hash changes.

#!/bin/bash
distrib_name="LibreOfficeOnline"
soli="/etc/apt/sources.list"
cpu=$(nproc)
log_dir="$PWD/$(date +'%Y%m%d-%H%M')_officeonline-install"
sh_interactive=true
set_name='collabora'
set_core_regex='cp-'
set_online_regex='collabora/collabora-online-4$'
set_version=''
lo_src_repo='https://github.com/LibreOffice/core.git'
lo_src_branch='master'
lo_src_commit=''
lo_src_tag=''
lo_dir="/opt/libreoffice"
lo_forcebuild=false
lo_req_vol=11000
lo_configure_opts=''
lo_mini=true
declare -r lo_mini_opts='disable-dbus, disable-dconf, disable-epm,
disable-evolution2, disable-ext-nlpsolver, disable-ext-wiki-publisher,
disable-firebird-sdbc, disable-gio, disable-gstreamer-1-0,
disable-gtk, disable-gtk3, disable-odk, disable-online-update,
disable-pdfimport, disable-postgresql-sdbc, disable-report-builder, disable-scripting-beanshell,
disable-scripting-javascript, disable-sdremote, disable-sdremote-bluetooth,
enable-extension-integration, enable-mergelibs, enable-python=internal,
enable-release-build, with-external-dict-dir=/usr/share/hunspell,
with-external-hyph-dir=/usr/share/hyphen, with-external-thes-dir=/usr/share/mythes,
with-fonts, with-galleries=no, with-lang=, with-linker-hash-style=both, with-system-dicts,
with-system-zlib, without-branding, without-help, without-java,
without-junit, without-myspell-dicts, without-package-format, without-system-jars,
without-system-jpeg, without-system-libpng, without-system-libxml,
without-system-openssl, without-system-poppler, without-system-postgresql,with-webdav=serf'
lo_non_free_ttf=false
poco_version_latest=$(curl -s https://pocoproject.org/ | awk -F'Latest Release: ' '{printf $2}' | grep -Eo '^[^ ]+.\w')
poco_default_dir="/opt/poco"  # just here for environnment checks
poco_forcebuild=false
poco_req_vol=550
lool_src_repo="https://github.com/LibreOffice/online.git"
lool_src_branch='master'
lool_src_commit=''
lool_src_tag=''
lool_dir="/opt/online"
lool_configure_opts=''
#lool_logfile='/var/log/loolwsd.log'
lool_prefix='/usr'
lool_sysconfdir='/etc'
lool_localstatedir='/var'
lool_forcebuild=false
lool_maxcon=200
lool_maxdoc=100
lool_req_vol=650
loolwsd_service_name='loolwsd'

[DmDS]

hmm... if there are many files in the folder and they do not fit into the window, the file is created, but not opened. if you scroll to the end, the file is created and opened.

update: i'll try to compile with another webdav client - neon

[DmDS]

I think this is a richdocuments bug. the file will be created, but will not open if it is outside the viewport.

can anyone check? open a folder with a lot of files. don't scroll down! create a new file with a name starting with the last letter of alphafit. the file will not open. scroll down to load the entire list. you will find your file. now create a new file with any name. it will open after creation because the list is fully loaded.

[joergmschulz]

just another recompile later (using ... without-system-postgresql,with-webdav=serf') , it seems to work. I don't have your viewport issue yet.

[DmDS]

with-webdav=serf completly solves the problem. there is another problem with opening newly created documents in a folder with a lot of files (100 or more) a new document will not open if it is created outside of the visible file list. i have created an issue https://github.com/nextcloud/richdocuments/issues/1245

temporarily, if you have a lot of files, you can disable lazy loading of the file list. the list may take a little longer to load, but there will be no problem with opening newly created documents.

./apps/files/js/filelist.js line 110
change
var rows = Math.ceil(this.$container.height() / 50); 
to
var rows = Math.ceil(this.$container.height());

[husisusi]

Thanks @DmDS

[husisusi]

I can not reproduce it on nc18.0.10

[husisusi]

I was able to reproduce it on nc 19.0.4 and nc 20.0.1. Version 18.0.10 is not affected. I confirm the bug.

[ryukenji3]

Hi, with the latest config posted here I got the same as @titansmc did in #210 .Does anyone have an idea of this?

[ryukenji3]

Compiled successfully after having had locale set before starting building if you are using the "clean" Ubuntu 18.04. Method is as I mentioned in the #205 .

but, stick to the #196 and #205 , it seems that both of them compiled successfully without having locale set in the "clean" ubuntu base image. (Perhaps this is an additional requirement by 2020.11?)

Anyway, locale set is recommended to prevent the error "Please ensure the file type is supported and not corrupted" error when open file which name is not in English, such as Russian/Japanese/Chinese.

[ryukenji3]

I was able to compiled successfully with the config in Wiki(updated at Nov 15, 2020), as LO:cp-6.4-11 & LOOL:cp-6.4.0-15

But All languages except English are displayed as squares when I started the service and LOOL's style looks really old, then found that LO build as expected in 6.4-11, but LOOL was build as 4.1.0 (git hash: 4b48ee68), not the one set in cfg file.

I got those in log:

Error: cp-6.4.0-15 is not in branch distro/collabora/collabora-online-4. 
Switched to a new branch 'distro/collabora/collabora-online-4'

then I tried to add set_core_regex='cp-6.4' set_online_regex='co-6-4' in the cfg file as @DmDS did, didn't pass the compile for missing some python3 dependencies, and here's the log:

Cloning into '/opt/online'... Checking out files: 100% (3358/3358), done. 
From https://github.com/CollaboraOnline/online.git Switched to a new branch private/michael/distro/collabora/co-6-4
Branch 'private/michael/distro/collabora/co-6-4' set up to track remote branch 'private/michael/distro/collabora/co-6-4' from 'origin'. 
HEAD is now at 6efef7932 Bump package version to 6.4.0-15 

I guess the branch prefixed with private/Michael/ is not what we need for compiling, it might be 'distro/collabora/co-6-4' . Does anyone have an idea of this?

Now I'm trying to git clone the specified branch in advance and see if it is working...

[ryukenji3]

It may be necessary to modify the set_online_regex(default still in 4) in lib/default.cfg or wiki cfg for LOOL: collabora online (6.4.0-15) .

[DmDS]

LibreOffice 6.4-20

CollaboraOnline 6.4.4-1

set_name='collabora'
set_core_regex='cp-6.4'
set_online_regex='^distro/collabora/co-6-4'

#### LibreOffice parameters ###
lo_src_repo='https://github.com/LibreOffice/core.git'
lo_src_branch='^distro/collabora/cp-6.4'
lo_src_commit=''
lo_dir="/opt/libreoffice"
lo_forcebuild=true 
lo_non_free_ttf=true

#### POCO parameters ###
poco_version=$poco_version_latest 
poco_forcebuild=false

#### LibreOffice Online parameters ###
lool_src_repo="https://github.com/CollaboraOnline/online.git"
lool_dir="/opt/lool"
lool_configure_opts="--disable-werror --with-lokit-path=${lo_dir}/include"
lool_logfile='/var/log/loolwsd.log'
lool_prefix='/usr'
lool_sysconfdir='/etc'
lool_localstatedir='/var'
lool_forcebuild=true
lool_maxcon=200
lool_maxdoc=100
loolwsd_service_name='loolwsd' 

[titansmc]

@ryukenji3 Hi, I am having issues with node v 8, it says that I need > 10 and if I manually install it, I get conflicts in the packages. Any help?

[ryukenji3]

@titansmc node v8 seems to work fine with LOOL 4.x, but when compiling using LOOL 6.x , node v10 is a must. I made it through by adding:

apt-get install -y python3-polib python3-lxml
npm install -g n
n stable #now node-v14.15.4
PATH="$PATH"  #reload env

[DmDS]

the last config will always use the most recent tag. for now, this will be version 6.4.4-3.

[ryukenji3]

@DmDS Thanks! I compiled successfully with your config , came out the right LOOL & LO version, but still got the problem that All languages except English are displayed as squares. Am I missing any dependencies? kindly your assistance.

[DmDS]

All languages except English are displayed as squares. Am I missing any dependencies? kindly your assistance.

try to install your locale and and set it as default

sudo dpkg-reconfigure locales

[ryukenji3]

try to install your locale and and set it as default

sudo dpkg-reconfigure locales

Thanks , but it didn't help with setting my locale to default and even reboot the machine. I built this on azure's vm, which is pretty "clean" system (Ubuntu 18.04.5 LTS) I suppose, I only install the node and python3-polib python3-lxml ,also the locale setting before the compile.

[titansmc]

it didn't help in my case neither. Brand new Ubuntu 18.04 with updated version of node (v14) and still get the same error. https://github.com/husisusi/officeonlin-install.sh/issues/210

[DmDS]

Thanks , but it didn't help...

hmm.. maybe this will help

sudo apt-get install ttf-mscorefonts-installer
sudo dpkg-reconfigure fontconfig-config

and also

sudo apt ttf-ubuntu-font-family

or chage lo_non_free_ttf to false and recompile

[titansmc]

unfortunately it didn't help...

[quenenni]

I successfully compiled Lool with recent @DmDS config params (thank for them).

For me, and lots of other users, it works beautifully. Unfortunately, we received complaints from users from various clouds about the new version having big problems in the way the documents are displayed. Characters above each others, the page not at the right size, .. Enough complaints that we decided to revert back to the old version for everyone.

It's possible that the problems are more for Mac users, but we have not yet found if it's only them. EDIT: it happened also on an Ubuntu and a Windows, tested on a FF, Chome and IE Edge.

Can it be a cache problem? (browser caches are more and more aggressive) Anyone noticing the same problems?

[joergmschulz]

no - can't confirm having seen this.

[titansmc]

I successfully compiled Lool with recent @DmDS config params (thank for them).

For me, and lots of other users, it works beautifully. Unfortunately, we received complaints from users from various clouds about the new version having big problems in the way the documents are displayed. Characters above each others, the page not at the right size, .. Enough complaints that we decided to revert back to the old version for everyone.

It's possible that the problems are more for Mac users, but we have not yet found if it's only them. EDIT: it happened also on an Ubuntu and a Windows, tested on a FF, Chome and IE Edge.

Can it be a cache problem? (browser caches are more and more aggressive) Anyone noticing the same problems?

can you post the snippet that worked for you, please?