Opened 8 years ago

Last modified 7 years ago

#12524 closed defect

Brand new project can not be used for new tickets when logging is set to error — at Version 1

Reported by: anonymous Owned by: falkb
Priority: high Component: SimpleMultiProjectPlugin
Severity: major Keywords:
Cc: Trac Release: 1.0

Description (last modified by Ryan J Ollos)

Hi, this is a really strange behavior I currently can reproduce on my trac 1.0.2 and SimpleMultiProject 0.0.4dev. It seriously took a while to make it reproducible but I finally could figure out that I can not submit a ticket when I select a brand new project for the ticket. I also need to have enabled File logging and have set it to ERROR to trigger this issue.

Steps to reproduce:

  1. Enable File Logging and set it to ERROR (haven't tested with critical).
  2. Create a new Project (name does not matter).
  3. Once you now try to create a new Ticket for the new Project, I'll receive a Warning that the Project "is not a valid value for the project field."

Once the logging is set to WARN, or DEBUG I can create the ticket with the same User-Account and the same content.

Environment:

Running trac with mod_python behind apache 2.4.10, and yes trac has access to the log file (tail -f trac.log will work)....

Thanks,

Change History (1)

comment:1 Changed 8 years ago by Ryan J Ollos

Description: modified (diff)
Note: See TracTickets for help on using tickets.