ProjeQtOr Forum - Posts Récents

PROJEQTOR Version V13.0.1 is now the latest stable release

babynus — Fri, 24 Jul 2026 14:48:06 +0000

Patch V13.0.1 sets version V13.0 a stable. You can now benefit of the features that will ease your use of ProjeQtOr. Modern UI

New Modern UI
Possibility to switch back to the Classic UI (default before version 13.0)
Several Kanban improvements
Removal of the legacy UI (prior to version 9.0)

Abacus Management

Finalization of the feature set

Gantt View

Global timeline on parent tasks
Contracted planning: possibility to display sub-tasks on the parent line
Possibility to display any Activity column in the Planning table
Support for hatching in addition to activity colors
Search by ID and name

Project Dashboard

Display projects in a single row
oject detail view

CSO_Arnaud

ARNAUD — Thu, 23 Jul 2026 08:42:31 +0000

Hello everyone, We are experiencing two issues related to report generation (version 12.5.2) and would like to know whether these behaviors are known and if any fixes or workarounds exist. Issue 1: Standard PDF Report Generation Failure Some reports fail to generate when the related ticket was created automatically from an email.After investigation, the problem appears to be linked to embedded images contained in email signatures (LinkedIn icons, Facebook icons, company logos, etc.).The following error is logged: 2026-07-22 16:57:27.368 ***** ERROR ***** ERROR ***** 2026-07-22 16:57:27.368 ***** ERROR ***** on file '/var/www/vhosts/open366.uxp-corp.com/httpdocs/external/html2pdf/src/Html2Pdf.php' at line (1530) 2026-07-22 16:57:27.368 ***** ERROR ***** cause = getimagesize(cid:image002.png@01DD1843.6A6062C0): Failed to open stream: No such file or directory We found that if we manually remove the problematic content from the email body, the PDF can be generated successfully again. We have also observed cases where images extend beyond the PDF page boundaries. Has anyone experienced this issue before? Is there a way to ignore embedded email images during PDF generation? Issue 2: Images Missing in Custom Word Reports The second issue concerns custom reports generated through the Word plugin.The report is generated successfully and no errors appear in the logs, but the images contained in the ticket description and resolution are not included in the generated document.We are using the following tags: Request Description Request Resolution Has anyone encountered this behavior? Are images supposed to be supported with these fields, or is there a specific configuration or template setting required?Any feedback, workaround, or official fix would be greatly appreciated. Thank you.

closed activities still show up

Frank Frank Sobel — Tue, 21 Jul 2026 11:02:06 +0000

Hello, as you can see in the attachment, the closed activities are still visible, event though the switch is off. Projeqtor version is 12.3.3. Best regards, F.

CRON error when reading reply_to

Sylvain Devidal — Mon, 20 Jul 2026 09:54:29 +0000

Hello Babynus, If I remember well, it was 12.1.0 But I'm not sure it's related to the upgrade. We already had some emails not synchronizing before the upgrade, but I didn't noticed the error in the logs. It looks like to be related to the emails themselves: In the mail headers, sometimes the "From:" value is empty. But the "Sender:" is set. IMO the current program reads the "From" value and fails if it's empty (or null). At this time is should try "Sender" and use this value if set properly, or simply reject the mail without error.

Return-Path: 
Received: from abf-zmfront02.aznetwork.priv (LHLO mx5.aznetwork.eu)
 (192.168.49.122) by abf-zmstor01.aznetwork.eu with LMTP; Wed, 15 Jul 2026
 02:21:43 +0200 (CEST)
Received: from localhost (localhost )
	by mx5.aznetwork.eu (Postfix) with ESMTP id 88916E0517;
	Wed, 15 Jul 2026 02:21:43 +0200 (CEST)
X-Spam-Flag: NO
X-Spam-Score: -2.004
X-Spam-Level:
X-Spam-Status: No, score=-2.004 required=6.6 tests=
 autolearn=no autolearn_force=no
Received: from mx5.aznetwork.eu ()
 by localhost (abf-zmfront02.aznetwork.eu ) (amavis, port 10032)
 with ESMTP id 0FnZ1J1he5ii; Wed, 15 Jul 2026 02:21:43 +0200 (CEST)
Received: from localhost (localhost )
	by mx5.aznetwork.eu (Postfix) with ESMTP id 47C84E0544;
	Wed, 15 Jul 2026 02:21:43 +0200 (CEST)
Authentication-Results:mx5.aznetwork.eu; dkim=permerror (bad message/signature format)
X-Virus-Scanned: amavis at abf-zmfront02.aznetwork.priv
Received: from mx5.aznetwork.eu ()
 by localhost (abf-zmfront02.aznetwork.eu ) (amavis, port 10026)
 with ESMTP id i21_zyC6Vgba; Wed, 15 Jul 2026 02:21:43 +0200 (CEST)
Received: from mailrelay2.aznetwork.eu (unknown )
	by mx5.aznetwork.eu (Postfix) with ESMTPS id 29966E0504
	for ; Wed, 15 Jul 2026 02:21:43 +0200 (CEST)
Received: from ****02 (unknown )
	by mailrelay2.aznetwork.eu (Postfix) with ESMTP id 04B003F9;
	Wed, 15 Jul 2026 02:21:43 +0200 (CEST)
From:
Date: Wed, 15 Jul 2026 02:21:42 +0200
Subject: ERREUR AVRILTRT02 - Supervision des traitements
Message-Id: 
Sender: "****@aznetwork.eu" 
To: "****@aznetwork.eu" 
MIME-Version: 1.0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

CSO_Arnaud

ARNAUD — Mon, 20 Jul 2026 09:42:23 +0000

Hello, We would like to know if it is possible, within the default notifications available under Global Settings > Email Sending, to add a placeholder/tag that automatically retrieves the customer name and/or the project name in the email subject or body. more genrally all the possible tag.If so, could you please let us know:

Which tags are available for these fields;
The correct syntax to use;
Where we can find the related documentation.

Thank you in advance for your help.

CRON error when reading reply_to

babynus — Sun, 19 Jul 2026 16:37:06 +0000

From wich version did you migrate ?

Error when updating any ticket field

Rémi Barberi — Wed, 15 Jul 2026 17:14:18 +0000

Hello, we register a new ticket for this issue : Ticket #11815, we working on it and this gonna be available with the subscription as soon a we fixed it, or when the next version is released. Have a great day.

Error when updating any ticket field

Sylvain Devidal — Wed, 15 Jul 2026 14:58:34 +0000

Hello, Do you need more details about this issue? It’s becoming blocking as we can no longer reply to our customers’ tickets or save the qualification. I’m not completely sure, but it seems to be related to the size (or the content) of the Description or Answer fields in the tickets. => Tickets created from emails are almost always affected. => If we paste content from a rich editor such as Microsoft Word into the Answer field, the problem occurs frequently. The Note field doesn’t seem to be impacted, so for now it’s the only place where we can store information in the tickets. The "Note" elements don't look like to be affected by the issue (so we can only use that field to store information in the tickets right now...)

CRON error when reading reply_to

Sylvain Devidal — Thu, 09 Jul 2026 11:33:33 +0000

Hello, Since we upgraded to 13.0.0 we often have this error in the log (and in the ticket mailbox screen too) : 2026-07-09 11:16:46.345 ***** ERROR ***** ERROR ***** 2026-07-09 11:16:46.346 ***** ERROR ***** on file '/var/www/projeqtor.aznetwork.eu/model/ImapMailbox2.php' at line (289) 2026-07-09 11:16:46.346 ***** ERROR ***** cause = Undefined array key "reply_to" 2026-07-09 11:16:46.346 ***** ERROR ***** Undefined array key "reply_to" in ImapMailbox2.php at line 289 2026-07-09 11:16:46.346 ***** ERROR ***** Error while executing CRON script : fix the source issue and manually restart the CRON Process 2026-07-09 11:16:46.346 ***** ERROR ***** EXCEPTION ***** 2026-07-09 11:16:46.346 ***** ERROR ***** on file '/var/www/projeqtor.aznetwork.eu/model/ImapMailbox2.php' at line (289) 2026-07-09 11:16:46.346 ***** ERROR ***** cause = Call to a member function toString() on null 2026-07-09 11:16:46.346 ***** ERROR ***** => #0 /var/www/projeqtor.aznetwork.eu/model/InputMailboxTicket.php (551) -> getMail() 2026-07-09 11:16:46.346 ***** ERROR ***** => #1 /var/www/projeqtor.aznetwork.eu/model/InputMailboxTicket.php (416) -> treatInputMailbox() 2026-07-09 11:16:46.346 ***** ERROR ***** => #2 /var/www/projeqtor.aznetwork.eu/model/Cron.php (1004) -> checkEmailsTicket() 2026-07-09 11:16:46.346 ***** ERROR ***** => #3 /var/www/projeqtor.aznetwork.eu/model/Cron.php (664) -> checkEmails() 2026-07-09 11:16:46.346 ***** ERROR ***** => #4 /var/www/projeqtor.aznetwork.eu/model/Cron.php (468) -> run() 2026-07-09 11:16:46.346 ***** ERROR ***** => #5 /var/www/projeqtor.aznetwork.eu/tool/cronRelaunch.php (30) -> relaunch() 2026-07-09 11:16:46.346 ***** ERROR ***** Call to a member function toString() on null 2026-07-09 11:16:46.346 ***** ERROR ***** Exception while executing CRON script : fix the source issue and manually restart the CRON Process 2026-07-09 11:16:46.346 ***** ERROR ***** === Trace Stack for last error === 2026-07-09 11:16:46.346 ***** ERROR ***** => /var/www/projeqtor.aznetwork.eu/tool/projeqtor.php at line 1638 calling debugPrintTraceStack() 2026-07-09 11:16:46.346 ***** ERROR ***** => calling exceptionHandler() 2026-07-09 11:16:46.346 ***** ERROR ***** === 2026-07-09 11:16:46.410 ***** ERROR ***** CRON abnormally stopped 2026-07-09 11:16:46.410 ***** ERROR ***** === Trace Stack for last error === 2026-07-09 11:16:46.410 ***** ERROR ***** => /var/www/projeqtor.aznetwork.eu/model/Cron.php at line 326 calling debugPrintTraceStack() 2026-07-09 11:16:46.410 ***** ERROR ***** => /var/www/projeqtor.aznetwork.eu/tool/cronRelaunch.php at line 28 calling Cron:abort() 2026-07-09 11:16:46.410 ***** ERROR ***** => calling cronAbort() 2026-07-09 11:16:46.410 ***** ERROR ***** === How to fix it?

Error when updating any ticket field

Sylvain Devidal — Thu, 09 Jul 2026 11:31:09 +0000

Hello, Since we upgraded to 13.0.0, on some tickets (not all) we have an issue when updating any field. Here is the error message found in the log file: 2026-07-09 11:25:52.635 ***** ERROR ***** ERROR ***** 2026-07-09 11:25:52.635 ***** ERROR ***** on file '/var/www/projeqtor.aznetwork.eu/model/IdentificationTags.php' at line (322) 2026-07-09 11:25:52.635 ***** ERROR ***** cause = preg_match_all(): Compilation failed: regular expression is too large at offset 132317 How to fix it? It looks like to become worst over time : initialy I got this error one or two times a day, but now it's almost on all tickets.