The zimlet-jitsi-meet is currently part of Zimbra 9 NE - here it is for FOSS

https://github.com/beezim-oss/zimlet-jitsi-meet

SuiteCRM Auto Import of Emails not working

As per this thread - https://github.com/salesagility/SuiteCRM/pull/7459 - a problem with the email charset (apparently specifically with Office 365 emails?) cause auto import of emails to fail.

Relevant hooks and scripts are:

function::pollMonitoredInboxesAOP

function::pollMonitoredInboxes

include/Imap/ImapHandler.php

modules/InboundEmail/InboundEmail.php

modules/InboundEmail/AOPInboundEmail.php

This issue appears to be that a null charset result on querying the email stops processing of inbound emails.

The solution I chose (mentioned elsewhere0 was to change the deafualt value of the charset parameter passed to the imap search script:

Change ln 795 from:

public function search($criteria, $options = SE_FREE, $charset = NULL)

to:

public function search($criteria, $options = SE_FREE, $charset = 'US-ASCII')

Automatically relate inbound email to contacts - Suitecrm

For some reason SugarCRM and SuiteCRM do not automatically relate inbound emails to a contact.

Others have outlined the problem like this:

https://community.sugarcrm.com/thread/20195 - Inbound email auto import doesn't relate to contact

The result is that automatically imported emails show under the history tab of a contact based on a dynamic match of the email address - but the email record is not marked as related to the contact.

This means that if the email address of the contact changes, you will lose the email history connection.

On examining the modules/InboundEmail/InboundEmail.php script, I found that the relate functionality is disabled by default:

Line 5157:

                ///////////////////////////////////////////////////////////////////
                ////    LINK APPROPRIATE BEANS TO NEWLY SAVED EMAIL
                ////    $contactAddr = $this->handleLinking($email);
                ////    END LINK APPROPRIATE BEANS TO NEWLY SAVED EMAIL
                ///////////////////////////////////////////////////////////////////

line 5442:

                ///////////////////////////////////////////////////////////////////
                ////    LINK APPROPRIATE BEANS TO NEWLY SAVED EMAIL
                ////$contactAddress = $this->handleLinking($email);
                ////    END LINK APPROPRIATE BEANS TO NEWLY SAVED EMAIL
                ///////////////////////////////////////////////////////////////////


Remove the commenting on the handleLinking function to enable.

Batch convert office documents

This took me a while from a few different sources. I need to convert all Powerpoint 95 docs in a directory and subdirectories - putting the converted file in the same folder as the source. My final Windows 10 CMD command: for \R %f in (*.ppt) do echo "C:\Program Files\LibreOffice 5\program\soffice.exe" --convert-to pptx:"Impress MS PowerPoint 2007 XML" --outdir "%~dpf." "%f" & timeout 60 This uses LibreOffice.

Zimbra won't install on Debian testing

When attempting to install or upgrade Zimbra on Debian testing you will get a message regarding an incompatible platform (DEBIANUNKNOWN).

Change to your install directory (installdircetory/packages):

Repeat for each Zimbra Debian package

dpkg-deb -R package tempdir

In tempdir/DEBIAN/control change

Version: 7.1.3_GA_3346.DEBIAN5
to
Version: 7.1.3GA3346.DEBIANUNKNOWN

dpkg-deb -b tempdir package

(dpkg-deb will complain about the underscores, so remove them)

rm -R tempdir/*

After doing this for each package:

./install.sh --platform-override

Koha z39.50 MARC record import fails

Koha is a fantastic open source product. Huge libraries run on it.

We suddenly (possibly after an upgrade) started getting first this error:

All arguments must be MARC::Field objects at /usr/share/koha/intranet/cgi-​bin/cataloguing/addbiblio.pl line 151

And then suddenly this one:

Can't call method "add_subfields" on an undefined value at /usr/___/cataloguing/addbiblio.pl line 142

This was resolved after days of hell by finding the solution to the second error here:

Resolve the error by changing the "z3950NormalizeAuthor z3950AuthorAuthFields" setting under the Cataloguing Tab, and Record Structure section to "don't copy".

Wordpress database error

This one did my head in for a while.

After a Wordpress reinstall I could not get the new installtion to connect to a database on a remote server. The error message from the "wp-config.php" file was:

Error Establishing a Database Connection

Everything in the file seemed correct. Wordpress was unable to write the file and had asked me to paste the configuration into the wp-config.php file after creating it.

So I eventually deleted this and modified a copy of the "wp-config-sample.php" file.

Presto! It worked. I believe the issue may have been the encoding of the copy and pasted configuration.