Wiki

User Tools

  • Logged in as: anonymous (anonymous)
  • Log Out

Site Tools

Trace:
mantisbt:plugins:emailreporting

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
mantisbt:plugins:emailreporting [2018/06/05 17:57] – [MantisBT Configuration options] SL-Gundammantisbt:plugins:emailreporting [2018/06/05 18:06] – [MantisBT Configuration options] SL-Gundam
Line 102: Line 102:
 It's possible to run into database query errors if you've incorrectly setup some maximum size settings in PHP, and MantisBT It's possible to run into database query errors if you've incorrectly setup some maximum size settings in PHP, and MantisBT
  
-EmailReporting and MantisBT uses the following to decide what the maximum attachment size is that should be supported (MySQL variable is not used for this decision)+EmailReporting and MantisBT use the following to decide what the maximum attachment size is that should be supported (MySQL variable is not used for this decision)
  
 ^ Where    ^ Configuration option     ^ Help information                                                ^ ^ Where    ^ Configuration option     ^ Help information                                                ^
Line 114: Line 114:
 As for the MantisBT $g_max_file_size. That one is very important if you've setup EmailReporting to save attachments in the database instead of on the disk. MySQL/MariaDB for example also have limits on the amount of data that is allowed in one insert statement which could generate an error (see max_allowed_packet above). If max_allowed_packet is set too low, this could result in the error [[https://dev.mysql.com/doc/refman/8.0/en/gone-away.html|"MySQL server has gone away"]]. As for the MantisBT $g_max_file_size. That one is very important if you've setup EmailReporting to save attachments in the database instead of on the disk. MySQL/MariaDB for example also have limits on the amount of data that is allowed in one insert statement which could generate an error (see max_allowed_packet above). If max_allowed_packet is set too low, this could result in the error [[https://dev.mysql.com/doc/refman/8.0/en/gone-away.html|"MySQL server has gone away"]].
  
-Make sure you set $g_max_file_size to a slightly lower value then your server setup supports (alternatively increase the other mentioned values to be higher then $g_max_file_size). If you need to handle big attachments, make sure MantisBT stores them on the disk, not in the database.+Make sure you set $g_max_file_size to a slightly lower value then your server setup supports (alternatively increase the other mentioned values to be higher then $g_max_file_size and adjust any not mentioned requirements for your setup to handle the increased size). If you need to handle big attachments, make sure MantisBT stores them on the disk, not in the database.
  
 === "From" address for MantisBT Notification emails === === "From" address for MantisBT Notification emails ===
mantisbt/plugins/emailreporting.txt · Last modified: 2022/10/23 09:12 by SL-Gundam
CC Attribution-Noncommercial-Share Alike 4.0 International Driven by DokuWiki