Brand new project can not be used for new tickets without environment reload

[anonymous]

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,

[Cinc-th]

Some observations:

If I set

[logging]
log_type = stderr

all is just fine.

With

[logging]
log_type = error

I can see the problem on ticket preview. Note that log_type = error is not a valid setting.

With

[logging]
log_type = file

I don't see a problem and a log file is created.

Note that I don't have any log_level set and running Trac using tracd.

With

[logging]
log_level = ERROR
log_type = file

I can't see any problem.

Do you have the correct settings in your trac.ini?

[falkb]

[logging]
log_file = trac.log
log_format = ......snip......
log_level = WARNING
log_type = file

[falkb]

but I'm not the ticket creator! Just want to let you know my settings :)

[Cinc-th]

Ok, after diving into Trac looking where the check is done I suspect I'm hunting a ghost here. The author didn't trigger the problem by enabling some special kind of logging.

AFAICS the problem is with not properly adding the new project as a new option to the in memory list of known projects (that's a select custom field with defined options). Tweaking the logging causes a reload of the environment and thus the list is rebuild.

So changing the logging after test to WARN or DEBUG makes the problem magically go away.

[Cinc-th]

In 14973:

Make sure cached value for project.options of ticket-custom field project is up to date by saving config data after changing.

Fixes #12524

[Cinc-th]

By saving the config data the environment is automatically reloaded. ATM I see no way to update the internal ticket-custom data without reloading the environment.