On Tuesday, March 11, 2014 8:31:19 PM UTC-5, RjOllos wrote:
>
> On Tuesday, March 11, 2014 6:20:33 PM UTC-7, ONeal Freeman wrote:
>>
>>
>>
>> On Tuesday, March 11, 2014 8:10:34 PM UTC-5, RjOllos wrote:
>>>
>>> On Tuesday, March 11, 2014 5:55:29 PM UTC-7, ONeal Freeman wrote:
>>>>
>>>>
>>>>
>>>> On Tuesday, March 11, 2014 7:51:32 PM UTC-5, RjOllos wrote:
>>>>>
>>>>> On Tuesday, March 11, 2014 5:07:25 PM UTC-7, ONeal Freeman wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tuesday, March 11, 2014 3:16:22 PM UTC-5, RjOllos wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tuesday, March 11, 2014 11:01:20 AM UTC-7, ONeal Freeman wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tuesday, March 11, 2014 11:54:43 AM UTC-5, RjOllos wrote:
>>>>>>>>>
>>>>>>>>> On Tuesday, March 11, 2014 9:21:29 AM UTC-7, ONeal Freeman wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tuesday, March 11, 2014 10:14:10 AM UTC-5, RjOllos wrote:
>>>>>>>>>>>
>>>>>>>>>>> On Tuesday, March 11, 2014 7:49:22 AM UTC-7, ONeal Freeman wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Tuesday, March 11, 2014 9:34:38 AM UTC-5, RjOllos wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tuesday, March 11, 2014 7:25:48 AM UTC-7, ONeal Freeman 
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tuesday, March 11, 2014 9:03:49 AM UTC-5, RjOllos wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tuesday, March 11, 2014 6:21:23 AM UTC-7, ONeal Freeman 
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Monday, March 10, 2014 5:40:27 PM UTC-5, hasienda wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> -----BEGIN PGP SIGNED MESSAGE----- 
>>>>>>>>>>>>>>>>> Hash: SHA1 
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On 10.03.2014 23:01, ONeal Freeman wrote: 
>>>>>>>>>>>>>>>>> > On Monday, March 10, 2014 4:11:38 PM UTC-5, hasienda 
>>>>>>>>>>>>>>>>> wrote: 
>>>>>>>>>>>>>>>>> >> On 10.03.2014 21:51, RjOllos wrote: 
>>>>>>>>>>>>>>>>> >>> Perhaps we need to see take a look at the full log 
>>>>>>>>>>>>>>>>> file at DEBUG 
>>>>>>>>>>>>>>>>> >>> level, 
>>>>>>>>>>>>>>>>> >>> for a session that spans restarting the web server to 
>>>>>>>>>>>>>>>>> navigating 
>>>>>>>>>>>>>>>>> >>> to the 
>>>>>>>>>>>>>>>>> >>> /newticket page. 
>>>>>>>>>>>>>>>>> >> 
>>>>>>>>>>>>>>>>> >> Indeed this was/is what I've been thinking too, more 
>>>>>>>>>>>>>>>>> debut logging, 
>>>>>>>>>>>>>>>>> >> please. 
>>>>>>>>>>>>>>>>> > 
>>>>>>>>>>>>>>>>> > So let me see if I understand what you want me to do 
>>>>>>>>>>>>>>>>> with the debug log. 
>>>>>>>>>>>>>>>>> > Start trac and then restart the web server (apache) 
>>>>>>>>>>>>>>>>> without exiting 
>>>>>>>>>>>>>>>>> > trac. Refresh trac and navigate to newticket? 
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Just restart the server, that is providing dynamic Trac 
>>>>>>>>>>>>>>>>> content. 
>>>>>>>>>>>>>>>>> Capture the log from after restart up to the end of the 
>>>>>>>>>>>>>>>>> first request, 
>>>>>>>>>>>>>>>>> that shall target /newticket directly. It will show a full 
>>>>>>>>>>>>>>>>> Trac 
>>>>>>>>>>>>>>>>> environment reload and the request itself. A browser 
>>>>>>>>>>>>>>>>> refresh would only 
>>>>>>>>>>>>>>>>> lengthen the log without providing additional information. 
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Steffen Hoffmann 
>>>>>>>>>>>>>>>>> -----BEGIN PGP SIGNATURE----- 
>>>>>>>>>>>>>>>>> Version: GnuPG v1.4.12 (GNU/Linux) 
>>>>>>>>>>>>>>>>> Comment: Using GnuPG with Icedove - 
>>>>>>>>>>>>>>>>> http://www.enigmail.net/ 
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> iEYEARECAAYFAlMeP1gACgkQ31DJeiZFuHe00gCglbxpHY+CRYFvKPigeKUa2CQK
>>>>>>>>>>>>>>>>>  
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> eYQAoIzHEerdGdDSrxv4JfkZdVeOZ27b 
>>>>>>>>>>>>>>>>> =ogY/ 
>>>>>>>>>>>>>>>>> -----END PGP SIGNATURE----- 
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I have attached my trac.log
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I don't see anything obvious so far. Could you try upgrading 
>>>>>>>>>>>>>>> to TracTicketTemplatePlugin 0.9dev though? It appears you are 
>>>>>>>>>>>>>>> still running 
>>>>>>>>>>>>>>> 0.8.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Now I am going to show your how much I don't know about trac. 
>>>>>>>>>>>>>> I tried using easy_install to download the template version and 
>>>>>>>>>>>>>> couldn't 
>>>>>>>>>>>>>> it. So I downloaded the source and created the egg. The source I 
>>>>>>>>>>>>>> downloaded 
>>>>>>>>>>>>>> and build was under 0.11.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Please point me in the direction to get the latest. 
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> You can upgrade by executing:
>>>>>>>>>>>>> easy_install 
>>>>>>>>>>>>> http://trac-hacks.org/svn/tractickettemplateplugin/0.11/
>>>>>>>>>>>>>
>>>>>>>>>>>>> and then restarting your webserver.
>>>>>>>>>>>>>
>>>>>>>>>>>>> When testing the latest version, it would be best to clear 
>>>>>>>>>>>>> your browser cache and do a hard-refresh of the page (hold down 
>>>>>>>>>>>>> SHIFT while 
>>>>>>>>>>>>> clicking the refresh button).
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Got an error trying to upgrade:    
>>>>>>>>>>>> File 
>>>>>>>>>>>> "c:\bitnami\trac-1.0.1-1\python\lib\setuptools-0.6c11-py2.7.egg\setuptools\command\egg_info.py",
>>>>>>>>>>>>  
>>>>>>>>>>>> line 233, in get_svn_revision
>>>>>>>>>>>> IndexError: list index out of range
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> That's a setuptools + SVN 1.7 issue which can be solved by 
>>>>>>>>>>> upgrading setuptools.
>>>>>>>>>>> http://trac-hacks.org/ticket/10778#comment:4
>>>>>>>>>>>
>>>>>>>>>>> If you don't want to upgrade setuptools, then probably the 
>>>>>>>>>>> easiest way to proceed is:
>>>>>>>>>>>  1. Download an archive of the source: 
>>>>>>>>>>> http://trac-hacks.org/changeset/latest/tractickettemplateplugin?old_path=/&filename=tractickettemplateplugin&format=zip
>>>>>>>>>>>  2. Change to the 0.11 directory and run easy_install  
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Not sure if this will help but attached my about page 
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> It looks like you have the latest setuptools (3.1). Did you 
>>>>>>>>> upgrade just now?
>>>>>>>>>
>>>>>>>>> I think that someone previously suggested the SVN 1.7 issues 
>>>>>>>>> should have been fixed in setuptool 1.2:
>>>>>>>>> https://pypi.python.org/pypi/setuptools/3.1#id18
>>>>>>>>>
>>>>>>>>> Anyway, did you try installing per the steps suggested in my 
>>>>>>>>> previous message? 
>>>>>>>>>
>>>>>>>>
>>>>>>>> After I download and installed templateplugin as per your 
>>>>>>>> instructions  I went back and also upgrade setup tools. 
>>>>>>>>
>>>>>>>
>>>>>>> What was the result? Any change in behavior? 
>>>>>>>
>>>>>>
>>>>>> Unfortunately no change. Console still shows timeout not defined. 
>>>>>>
>>>>>
>>>>> Do you think it's possible that you have an older version of Trac on 
>>>>> your Python search path? It doesn't seem likely since the proper version 
>>>>> of 
>>>>> Trac is displayed on the about page, but we are running out of things to 
>>>>> check.
>>>>>
>>>>
>>>> My trac.pth does contain two lines:
>>>>
>>>> C:\\BitNami\\trac-1.0.1-1\\apps\\trac\\Lib\\site-packages\\Trac-1.0.1-py2.7.egg
>>>>
>>>> C:\\BitNami\\trac-1.0.1-1\\apps\\trac\\Lib\\site-packages\\Trac-1.1.2dev-py2.7.egg
>>>>
>>>
>>>  I think it would be worth trying to remove "Trac-1.1.2dev-py2.7.egg" 
>>> from trac.pth and delete the egg. Restart the web server before testing 
>>> again.
>>>
>>> I removed the line but didn't find the egg. I searched the drive for the 
>> egg but didn't find it. 
>>
>
> Have you tried doing a reinstall of Bitnami yet?
>
> Make sure to backup your Trac environment directory in case something goes 
> wrong in the process. 
>
> If the Trac environment resides outside of C:\BitNami, you could just 
> delete the BitNami directory after uninstalling, just to be sure.
>

I have done exactly as you instructed above once all ready. Yes my trac env 
is outside the bitnami.

Do you think I should try a manual install instead of using bitnami? 

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to