Re: 404 issue1 not found

Hello John,




Am 20.09.2016 um 03:21 schrieb John P. Rouillard:
> Hi Martin:
>
> In message <[email protected]>,
> Martin Thomas Swaton writes:
>> Thanks John!
>> the hint with the trailing / was exactly what I needed.
>>
>> the old version and implementation with mod_python needed:
>>
>> # roundup requires a slash after tracker name - add it if missing
>> #RedirectMatch permanent ^/([^/]+)$ /$1/
>> and also had no problems with the trailing slash that is added by the
>> browser automatically, when there is no filename at the end of the url.
>>
>> e.g. issue1 gets a slash by the browser, issue.1 won't.
>>
>> So I added:
>>
>> RedirectMatch permanent ^/(.*)/$ /$1
>>
>> and everything is working. Maybe someone could add the information about
>> the trailing / to the documentation how to set up roundup with wsgi.
> Could you suggest where that should go and some example text?


the documentation at
http://www.roundup-tracker.org/docs/installation.html
has a part for wsgi - I guess here would be a good place. But anyway, 
the instructions how to set roundup up with wsgi in the documentation 
seem not correct or at least not the simplest way.
In my earlier message I put the "one" line that is needed in the apache 
config, the documentation states, that you have to start a wsgi server 
with make server, which seems not to be correct.
I would suggest to just give the simple example with the oneliner and 
the three lines for the .wsgi file so everybody can simply set that up, 
if needed.

>> By the way, how would I set the language for the webinterface with
>> mod_wsgi? With mod_python I could set that in the vhost.conf as python
>> option. Where would I do that now with mod_wsgi?
> I thought roundup would use the language header in the http request.
>
> Then again I have never had to use it in any language but
> English. However I think there is a language setting in the tracker
> section of the config.ini file.
>
> The code says:
>
>          (NullableOption, "language", "",
>              "Default locale name for this tracker.\n"
>              "If this option is not set, the language is determined\n"
>              "by OS environment variable LANGUAGE, LC_ALL, LC_MESSAGES,\n"
>              "or LANG, in that order of preference."),
>
> so I assume any valid LC_ALL value would work.

yes, you are right, in the config this can also be set. But with 
mod_python and it's  setup you where able to have different domains 
pointing to the same roundup instance and per domain set the language. 
This is not possible if you set it in the config.
I do not need it right now, just noticed, that I am no more able to do 
it like before :-)
Maybe someone has an idea how to reimpliment that in future.

>> Thanks for your great and quick response,
> Glad it worked out for you.
>
> It sounds like you are upgrading/converting an existing roundup.
>
> If you don't mind my asking what are you using it for?

your welcome, yes 'i installed a new version on a centos7 server and use 
my old template and detectors. Beside removing the anypy.set_ includes I 
did not have to make changes - the 1.5.0 setup also works with 1.5.1.
I use it as an company support system. i just added auto assignment on a 
Mail reply of a support member and auto assignment per tag if the tag is 
found in the subject.

Have a nice week too!

martin


> Have a great week.
>
> --
> 				-- rouilj
> John Rouillard
> ===========================================================================
> My employers don't acknowledge my existence much less my opinions.
>


------------------------------------------------------------------------------