Re: [Trac] new ticket error

[Steffen Hoffmann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 20.04.2013 03:05, Mark Maciolek wrote:
> new installation of version trac 1.0
> when creating new ticket if I assign owner get this in the logs
>
> 2013-04-19 20:48:39,952 Trac[main] ERROR: Internal Server Error:
> Traceback (most recent call last):
...
> OperationalError: near ",": syntax error
>
> If I leave it set to <default> no error
>
> How do I go about determining what is wrong in my trac.ini flie?

Deactivate TracJsGanttPlugin [1] and re-try, because it seems like a
plugin issue. From a short look at it I've just seen, that it could do
better when giving SQL arguments, because the current style doesn't
protect i.e. against SQL injections.

I bet with PostgreSQL you could get a more helpful error, but maybe the
current plugin maintainer knows even better. Btw, I appreciate you
asking here before throwing out tickets at Trac and Trac plugins.

Steffen Hoffmann


[1] http://trac-hacks.org/wiki/TracJsGanttPlugin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlFzMfwACgkQ31DJeiZFuHelIwCffhw926z8niY9OpsAG5QDp1vq
OuoAoISodexhrXeze2m0bWQ2Vd4k0EDA
=iETp
-----END PGP SIGNATURE-----

[RjOllos]

On Saturday, April 20, 2013 5:25:34 PM UTC-7, hasienda wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 20.04.2013 03:05, Mark Maciolek wrote:
> new installation of version trac 1.0
> when creating new ticket if I assign owner get this in the logs
>
> 2013-04-19 20:48:39,952 Trac[main] ERROR: Internal Server Error:
> Traceback (most recent call last):
...
> OperationalError: near ",": syntax error
>
> If I leave it set to <default> no error
>
> How do I go about determining what is wrong in my trac.ini flie?

Deactivate TracJsGanttPlugin [1] and re-try, because it seems like a
plugin issue. From a short look at it I've just seen, that it could do
better when giving SQL arguments, because the current style doesn't
protect i.e. against SQL injections.

That looks like a pretty major issue with the plugin, and cross-DB compatibility issues are also common when the database API isn't utilized correctly, so it could very well directly be the cause of the issue that Mark is seeing.

I went ahead and made a ticket for the issue: https://trac-hacks.org/ticket/11027

Mark, please post your trac.ini sections for [trac-jsgantt] and [TracPM] so that we can better test the fix with your exact configuration.