TicketMoverPlugin Help

69 views
Skip to first unread message

Ahmed M.

unread,
Dec 9, 2015, 9:49:55 PM12/9/15
to Trac Users
I am using trac 1.0.9 [Python 2.7, mysql 5.7.9 and Apache 2.4] and I have two environments and I want to be able to move tickets from one environment to another. I followed the instructions to install the ticketmoverplugin [https://trac-hacks.org/wiki/TicketMoverPlugin] and that's where I am stuck! I don't know how to configure it to show a drop-down menu with the available projects or similar. 
I need help making it work but I have no idea where to start.

Thank you so much!

RjOllos

unread,
Dec 10, 2015, 1:15:57 AM12/10/15
to Trac Users
The instructions on the page you cited describe how to install and configure the plugin. Did you enable the Components and configure the permission needed to move a ticket?

You might be at the stage where you just need to determine that the plugin is installed and loading correctly. For that, I suggest looking closely at the "Is the plugin enabled" and "Check the log files" troubleshooting steps:


- Ryan

Ahmed M.

unread,
Dec 10, 2015, 10:01:42 AM12/10/15
to Trac Users
Thanks Ryan,

I did all the checks on the troubleshooting page and everything went fine except for one thing:
the ticketmoverplugin has two dependencies: ticketsidebarproviderplugin and TracSqlHelperScript. 
ticketmoverplugin and ticketsidebarproviderplugin are showing in my admin GUI page as plugins - TracSqlHelperScript is NOT!? I treated TracSqlHelperScript as a plugin and put the egg in the plugins directory - it this the problem I have? Does 'script' make it different from 'plugin'? 

Thanks again,
Ahmed

RjOllos

unread,
Dec 10, 2015, 5:48:08 PM12/10/15
to Trac Users


On Thursday, December 10, 2015 at 7:01:42 AM UTC-8, Ahmed M. wrote:
Thanks Ryan,

I did all the checks on the troubleshooting page and everything went fine except for one thing:
the ticketmoverplugin has two dependencies: ticketsidebarproviderplugin and TracSqlHelperScript. 
ticketmoverplugin and ticketsidebarproviderplugin are showing in my admin GUI page as plugins - TracSqlHelperScript is NOT!? I treated TracSqlHelperScript as a plugin and put the egg in the plugins directory - it this the problem I have? Does 'script' make it different from 'plugin'? 

Thanks again,
Ahmed

I removed the dependency on SQLHelperScript, see #12608 (1). Would you kindly install the latest version and retest? 

There is an issues with moving attachments (2). I'll fix it within a few days.

- Ryan

Ahmed M.

unread,
Dec 10, 2015, 10:34:19 PM12/10/15
to Trac Users
I tried it with no luck, sorry. I wish I know enough to help with the debugging. here is the GUI view of what I have. I assume that there isn't anything else I need to do to make it work. I have three 'projects' in the same c:\trac folder - I did the troubleshooting steps you provided. Any debugging advice you can give me?

Thanks for all your help,

Ahmed

RjOllos

unread,
Dec 10, 2015, 10:48:16 PM12/10/15
to Trac Users


On Thursday, December 10, 2015 at 7:34:19 PM UTC-8, Ahmed M. wrote:
I tried it with no luck, sorry. I wish I know enough to help with the debugging. here is the GUI view of what I have. I assume that there isn't anything else I need to do to make it work. I have three 'projects' in the same c:\trac folder - I did the troubleshooting steps you provided. Any debugging advice you can give me?

Nothing else should be required. If you are logged in and able to view the Plugin Admin Panel then you must have TRAC_ADMIN, so it couldn't be a permission issue. I would take a closer look at the logs, for any messages related to TicketMoverPlugin.

I tested on Mac OSX rather than Windows, but if there is an issue specifically on Windows then I assume we'll find something in the logs.

- Ryan

Ahmed M.

unread,
Dec 11, 2015, 8:02:35 AM12/11/15
to Trac Users
Thanks Ryan,
I 'll try to find out what's going on and I will let you know if I find anything. 
I checked the logs and the only message I get when I restart the environment is:
2015-12-10 22:31:14,677 Trac[api] WARNING: Unable to find repository '(default)' for synchronization
Do you think that has anything to do with the issue in hand? 

Thanks again,
Ahmed

RjOllos

unread,
Dec 11, 2015, 4:16:20 PM12/11/15
to Trac Users
On Friday, December 11, 2015 at 5:02:35 AM UTC-8, Ahmed M. wrote:
Thanks Ryan,
I 'll try to find out what's going on and I will let you know if I find anything. 
I checked the logs and the only message I get when I restart the environment is:
2015-12-10 22:31:14,677 Trac[api] WARNING: Unable to find repository '(default)' for synchronization
Do you think that has anything to do with the issue in hand? 

That issue is unrelated. You likely have an entry in your [repositories] section or [trac] repository_dir option that has an invalid path. However, there could be other reasons.

Have you been able to browse your configured repositories?

- Ryan

Ahmed M.

unread,
Dec 11, 2015, 5:17:32 PM12/11/15
to Trac Users
I actually don't have any configured repositories. I am not there yet - still perfecting my trac environment.

RjOllos

unread,
Dec 12, 2015, 6:47:45 PM12/12/15
to Trac Users


On Thursday, December 10, 2015 at 7:34:19 PM UTC-8, Ahmed M. wrote:
I tried it with no luck, sorry. I wish I know enough to help with the debugging. here is the GUI view of what I have. I assume that there isn't anything else I need to do to make it work. I have three 'projects' in the same c:\trac folder - I did the troubleshooting steps you provided. Any debugging advice you can give me?

If you are running with Apache you need to run the "deploy" step again. I recommend running the command every time you install or update a plugin.


- Ryan

Ahmed M.

unread,
Dec 14, 2015, 2:52:38 PM12/14/15
to Trac Users
Still no luck.
The ticketsidebarprovider plugin comes with a 'hello world' test and that works; I can see the Hello World sidebar. As for the ticketmover plugin, still nothing.
Is there anything I can do to debug this? may be if you can give me a few things to test\check I can do that and send them over to you.

By the way, the trac projects I have are located in C:\trac\swtrac, C:\trac\hwtrac and C:\trac\chtrac. How do one of those know about the other? I guess my question is about how the plugin really works to move one ticket to another database. 


thanks,

Ryan Ollos

unread,
Dec 14, 2015, 3:12:01 PM12/14/15
to Trac Users
On Mon, Dec 14, 2015 at 11:52 AM, Ahmed M. <sab...@gmail.com> wrote:
Still no luck.
The ticketsidebarprovider plugin comes with a 'hello world' test and that works; I can see the Hello World sidebar. As for the ticketmover plugin, still nothing.
Is there anything I can do to debug this? may be if you can give me a few things to test\check I can do that and send them over to you.

If there's a problem with the plugin we'll almost certainly see an error in the logs. Otherwise, it's probably an installation issue.
 
By the way, the trac projects I have are located in C:\trac\swtrac, C:\trac\hwtrac and C:\trac\chtrac. How do one of those know about the other? I guess my question is about how the plugin really works to move one ticket to another database. 

The plugin knows about all of the Trac projects because they have the same parent directory:

You can see from the code that trac.env_paths or trac.env_parent_dir needs to be set in the environment. This depends on Apache and the cgi or fcgi script being correctly configured. If you are using the cgi or fcgi script created by TracAdmin deploy you shouldn't need to worry about it.

Are you using mod_python or mod_wsgi? If using mod_wsgi, have you set TRAC_ENV_PARENT_DIR?

If using mod_python, have you set TracEnvParentDir?

Also, please make sure to post below the text you are replying to so that it's completely unambiguous which comments are replying to. Thanks!

- Ryan

Ahmed M.

unread,
Dec 15, 2015, 12:02:02 AM12/15/15
to Trac Users, ryan.j...@gmail.com
please seen my comments below.


On Monday, December 14, 2015 at 3:12:01 PM UTC-5, RjOllos wrote:
On Mon, Dec 14, 2015 at 11:52 AM, Ahmed M. <sab...@gmail.com> wrote:
Still no luck.
The ticketsidebarprovider plugin comes with a 'hello world' test and that works; I can see the Hello World sidebar. As for the ticketmover plugin, still nothing.
Is there anything I can do to debug this? may be if you can give me a few things to test\check I can do that and send them over to you.

If there's a problem with the plugin we'll almost certainly see an error in the logs. Otherwise, it's probably an installation issue. 
 
By the way, the trac projects I have are located in C:\trac\swtrac, C:\trac\hwtrac and C:\trac\chtrac. How do one of those know about the other? I guess my question is about how the plugin really works to move one ticket to another database. 

The plugin knows about all of the Trac projects because they have the same parent directory:

You can see from the code that trac.env_paths or trac.env_parent_dir needs to be set in the environment. This depends on Apache and the cgi or fcgi script being correctly configured. If you are using the cgi or fcgi script created by TracAdmin deploy you shouldn't need to worry about it.

Are you using mod_python or mod_wsgi? If using mod_wsgi, have you set TRAC_ENV_PARENT_DIR?
Thanks, that's what I was missing. I didn't set up the trac environment variable in my wsgi file becasue i was using the one that is generated during the deploy operation. I simplified the wsgi file to: 
{{{
import sys
sys.stdout = sys.stderr
import os
os.environ['TRAC_ENV_PARENT_DIR'] = 'C:\\trac'
os.environ['PYTHON_EGG_CACHE'] = 'C:\\trac\\egg_cache'
import trac.web.main
application = trac.web.main.dispatch_request
}}}

Now the ticket mover works BUT I see an error after I login (see attached).
My Apache config has this for each of my trac projects:
{{{
# point to where the wsgi script is 
WSGIScriptAlias /swtrac C:/trac/swtrac/cgi-bin/trac.wsgi
# Tell Apache that this is an ok directory to use ... 
<Directory C:/trac/swtrac/cgi-bin>
    WSGIApplicationGroup %{GLOBAL}
    <IfModule mod_authz_core.c>
        Require all granted
    </IfModule>
</Directory>
}}}


If using mod_python, have you set TracEnvParentDir?

Also, please make sure to post below the text you are replying to so that it's completely unambiguous which comments are replying to. Thanks!
Roger That! 

- Ryan
error.PNG

RjOllos

unread,
Dec 15, 2015, 12:21:22 AM12/15/15
to Trac Users, ryan.j...@gmail.com


On Monday, December 14, 2015 at 9:02:02 PM UTC-8, Ahmed M. wrote:
please seen my comments below.

On Monday, December 14, 2015 at 3:12:01 PM UTC-5, RjOllos wrote:
On Mon, Dec 14, 2015 at 11:52 AM, Ahmed M. <sab...@gmail.com> wrote:
Still no luck.
The ticketsidebarprovider plugin comes with a 'hello world' test and that works; I can see the Hello World sidebar. As for the ticketmover plugin, still nothing.
Is there anything I can do to debug this? may be if you can give me a few things to test\check I can do that and send them over to you.

If there's a problem with the plugin we'll almost certainly see an error in the logs. Otherwise, it's probably an installation issue. 
 
By the way, the trac projects I have are located in C:\trac\swtrac, C:\trac\hwtrac and C:\trac\chtrac. How do one of those know about the other? I guess my question is about how the plugin really works to move one ticket to another database. 

The plugin knows about all of the Trac projects because they have the same parent directory:

You can see from the code that trac.env_paths or trac.env_parent_dir needs to be set in the environment. This depends on Apache and the cgi or fcgi script being correctly configured. If you are using the cgi or fcgi script created by TracAdmin deploy you shouldn't need to worry about it.

Are you using mod_python or mod_wsgi? If using mod_wsgi, have you set TRAC_ENV_PARENT_DIR?
Thanks, that's what I was missing. I didn't set up the trac environment variable in my wsgi file becasue i was using the one that is generated during the deploy operation.

Thanks, I added a note to the TicketMoverPlugin page about that:
 
I simplified the wsgi file to: 
{{{
import sys
sys.stdout = sys.stderr
import os
os.environ['TRAC_ENV_PARENT_DIR'] = 'C:\\trac'
os.environ['PYTHON_EGG_CACHE'] = 'C:\\trac\\egg_cache'
import trac.web.main
application = trac.web.main.dispatch_request
}}}

Now the ticket mover works BUT I see an error after I login (see attached).
My Apache config has this for each of my trac projects:
{{{
# point to where the wsgi script is 
WSGIScriptAlias /swtrac C:/trac/swtrac/cgi-bin/trac.wsgi
# Tell Apache that this is an ok directory to use ... 
<Directory C:/trac/swtrac/cgi-bin>
    WSGIApplicationGroup %{GLOBAL}
    <IfModule mod_authz_core.c>
        Require all granted
    </IfModule>
</Directory>
}}}


I think you can fix that by creating a file in C:\trac name ".tracignore" with content:

egg_cache

Or, you can renamed egg_cache to .egg_cache

Ahmed M.

unread,
Dec 15, 2015, 11:31:26 AM12/15/15
to Trac Users, ryan.j...@gmail.com
See my comments below:
After some investigation, I found that the issue was that in my Apache config, it seemed to me that it didn't know where to go after accepting a login request. It was looking for /login page which doesn't exist. I created one wsgi script for all sites and updated my Apache config with this:
{{{
# point to where the wsgi script is 
WSGIScriptAlias /trac C:/trac_stuff/wsgi/trac.wsgi

# Tell Apache that this is an ok directory to use ... 
<Directory C:/trac_stuff/wsgi>
    WSGIApplicationGroup %{GLOBAL}
    <IfModule mod_authz_core.c>
        Require all granted
    </IfModule>
</Directory>
}}}
It works just fine now - THANK YOU SO MUCH. I hope others can benefit from this.
I am now working on customizing it - I want to remove the deletion checkbox - deletion is not allowed. Any help is appreciated. 

Ryan Ollos

unread,
Dec 15, 2015, 12:30:08 PM12/15/15
to Ahmed M., Trac Users


On Tue, Dec 15, 2015 at 8:31 AM, Ahmed M. <sab...@gmail.com> wrote:
After some investigation, I found that the issue was that in my Apache config, it seemed to me that it didn't know where to go after accepting a login request. It was looking for /login page which doesn't exist. I created one wsgi script for all sites and updated my Apache config with this:
{{{
# point to where the wsgi script is 
WSGIScriptAlias /trac C:/trac_stuff/wsgi/trac.wsgi

# Tell Apache that this is an ok directory to use ... 
<Directory C:/trac_stuff/wsgi>
    WSGIApplicationGroup %{GLOBAL}
    <IfModule mod_authz_core.c>
        Require all granted
    </IfModule>
</Directory>
}}}
It works just fine now - THANK YOU SO MUCH. I hope others can benefit from this.
I am now working on customizing it - I want to remove the deletion checkbox - deletion is not allowed. Any help is appreciated. 

It should be easy enough to just remove the checkbox from the template.

If you want to propose a patch for the plugin, one possibility would be to have separate options for the ticket move permission and the ticket delete permission.

- Ryan

Ahmed M.

unread,
Dec 15, 2015, 2:30:50 PM12/15/15
to Trac Users, sab...@gmail.com, ryan.j...@gmail.com


On Tuesday, December 15, 2015 at 12:30:08 PM UTC-5, RjOllos wrote:


On Tue, Dec 15, 2015 at 8:31 AM, Ahmed M. <sab...@gmail.com> wrote:
After some investigation, I found that the issue was that in my Apache config, it seemed to me that it didn't know where to go after accepting a login request. It was looking for /login page which doesn't exist. I created one wsgi script for all sites and updated my Apache config with this:
{{{
# point to where the wsgi script is 
WSGIScriptAlias /trac C:/trac_stuff/wsgi/trac.wsgi

# Tell Apache that this is an ok directory to use ... 
<Directory C:/trac_stuff/wsgi>
    WSGIApplicationGroup %{GLOBAL}
    <IfModule mod_authz_core.c>
        Require all granted
    </IfModule>
</Directory>
}}}
It works just fine now - THANK YOU SO MUCH. I hope others can benefit from this.
I am now working on customizing it - I want to remove the deletion checkbox - deletion is not allowed. Any help is appreciated. 

It should be easy enough to just remove the checkbox from the template.
That's exactly what I did, works great! 

If you want to propose a patch for the plugin, one possibility would be to have separate options for the ticket move permission and the ticket delete permission.

- Ryan

I would actually love to do that. I am quite new to python\trac programming but I will give it a shot.  I have other ideas that I would like to implement as well. Is there a resource I can go to to get a crash course on trac plugin programming? 

Thanks,
Ahmed

Ryan Ollos

unread,
Dec 15, 2015, 3:24:31 PM12/15/15
to Ahmed M., Trac Users
On Tue, Dec 15, 2015 at 11:30 AM, Ahmed M. <sab...@gmail.com> wrote:
I would actually love to do that. I am quite new to python\trac programming but I will give it a shot.  I have other ideas that I would like to implement as well. Is there a resource I can go to to get a crash course on trac plugin programming? 

There are a bunch of resources here:

Specifically, you may want to start here:

Feel free to follow-up and let us know any difficulties you encounter. The intro documentation could probably be improved, so it's useful to hear about any difficulties encountered.

Also, just take a crack at making a patch and you should get some feedback on the ticket or list.

- Ryan


Ahmed M.

unread,
Dec 15, 2015, 5:49:58 PM12/15/15
to Trac Users, sab...@gmail.com, ryan.j...@gmail.com
Thank you so much. I will give it a try and I will update this post with relevant information (or create a new one)

Thanks Ryan,
Ahmed

Ahmed M.

unread,
Dec 15, 2015, 6:16:58 PM12/15/15
to Trac Users, sab...@gmail.com, ryan.j...@gmail.com
One thing I could use some help on is customizing the box that has the ticket mover button and combo box. ticketmover-sidebar.html doesn't have any references to a css style sheet. there is a style sheet in "C:\trac\hwtrac\htdocs\common\css\ticket-sidebar.css" but changing that doesn't make any difference. Any thoughts on that? 

Ahmed

Ryan Ollos

unread,
Dec 15, 2015, 6:29:42 PM12/15/15
to Ahmed M., Trac Users
On Tue, Dec 15, 2015 at 3:16 PM, Ahmed M. <sab...@gmail.com> wrote:
One thing I could use some help on is customizing the box that has the ticket mover button and combo box. ticketmover-sidebar.html doesn't have any references to a css style sheet. there is a style sheet in "C:\trac\hwtrac\htdocs\common\css\ticket-sidebar.css" but changing that doesn't make any difference. Any thoughts on that? 

Ahmed

The outer div has class "sidebar", so you could add rules to a custom stylesheet.

If needed, you could add classes to the ticket mover sidebar elements and submit a patch:

- Ryan
 

Ahmed M.

unread,
Dec 17, 2015, 9:49:31 AM12/17/15
to Trac Users, sab...@gmail.com, ryan.j...@gmail.com


On Tuesday, December 15, 2015 at 6:29:42 PM UTC-5, RjOllos wrote:


On Tue, Dec 15, 2015 at 3:16 PM, Ahmed M. <sab...@gmail.com> wrote:
One thing I could use some help on is customizing the box that has the ticket mover button and combo box. ticketmover-sidebar.html doesn't have any references to a css style sheet. there is a style sheet in "C:\trac\hwtrac\htdocs\common\css\ticket-sidebar.css" but changing that doesn't make any difference. Any thoughts on that? 

Ahmed

The outer div has class "sidebar", so you could add rules to a custom stylesheet.
I tried that but didn't have any luck. I still need to do some reading on that. I tried adding the css style inline with the html code in the template and it worked just fine 

If needed, you could add classes to the ticket mover sidebar elements and submit a patch:
That could be my learning exercise. I still need to do some practice on that. I will keep you posted

- Ryan
 
 I have one question though, how do I prevent the drop-down menu from showing the current project? I tried to move a ticket to the same project and it worked - is there a way I can remove the current project from the list?

RjOllos

unread,
Dec 17, 2015, 3:53:20 PM12/17/15
to Trac Users, sab...@gmail.com, ryan.j...@gmail.com


On Thursday, December 17, 2015 at 6:49:31 AM UTC-8, Ahmed M. wrote:


On Tuesday, December 15, 2015 at 6:29:42 PM UTC-5, RjOllos wrote:


On Tue, Dec 15, 2015 at 3:16 PM, Ahmed M. <sab...@gmail.com> wrote:
One thing I could use some help on is customizing the box that has the ticket mover button and combo box. ticketmover-sidebar.html doesn't have any references to a css style sheet. there is a style sheet in "C:\trac\hwtrac\htdocs\common\css\ticket-sidebar.css" but changing that doesn't make any difference. Any thoughts on that? 

Ahmed

The outer div has class "sidebar", so you could add rules to a custom stylesheet.
I tried that but didn't have any luck. I still need to do some reading on that. I tried adding the css style inline with the html code in the template and it worked just fine 

Simplified steps that should work:
1. Add the site.html given in [1] to your environment (or a shared) templates directory.
2. Create an empty style.css in your environment (or a shared) htdocs directory.
3. Refresh static resources [2].
4. Restart web server.

You should then be able to navigate to any page on your site, see a link to style.css in the HTML source code, and open the style.css file. If that works, then you can repeat by editing style.css and refreshing static resources.

 
 I have one question though, how do I prevent the drop-down menu from showing the current project? I tried to move a ticket to the same project and it worked - is there a way I can remove the current project from the list?

I assume you are running the latest version of ticket mover, or at least [15109] committed on 2015-12-10. The program logic should prevent the current project from being added to the list:
and that seems to work according to testing I've done on Mac OSX. So I'm unsure what could be different in your case, but I imagine it must have something to do with the path representation on Windows.

Maybe we need to use normpath [1] in the comparison, since it's already used for env_path [2]:

env_path != os.path.normpath(self.env.path)

Ahmed M.

unread,
Dec 21, 2015, 3:43:17 PM12/21/15
to Trac Users, sab...@gmail.com, ryan.j...@gmail.com
I found that I wasn't using the [15109] so I downloaded it, created the egg, replaced the one in my plugins directory but I don't see the ticket mover side bar anymore?!! Last time I had this problem the issue was in my wsgi file and that was fixed before. I re-deployed both of my trac sites and the mover side bar isn't showing up. Also no relevant messages in the log file. I followed the troubleshooting steps you mentioned to me in a previous message.
 
My plugins directory is c:/trac_stuff/plugins and my two trac sites are c:/trac/swtrac and c:/trac/hwtrac. I am completely puzzled with this.

Any other troubleshooting idea you can give me? 

Thanks in advance ...

Ahmed M.

unread,
Dec 21, 2015, 8:56:19 PM12/21/15
to Trac Users, sab...@gmail.com, ryan.j...@gmail.com
Here is something I tried and I can't find an explanation for. I downloaded [15128] in stead of [15109] and it worked! I am going to do a diff and see what are the differences. I just thought I 'd update you.
Also, I added the 'os.path.normpath' to 
{{{
 if env_path !=  os.path.normpath(self.env.path):
}}}
but it didn't help.

Any suggestions where to look? 

Thanks,

RjOllos

unread,
Dec 21, 2015, 9:27:22 PM12/21/15
to Trac Users, sab...@gmail.com, ryan.j...@gmail.com


On Monday, December 21, 2015 at 5:56:19 PM UTC-8, Ahmed M. wrote:
Here is something I tried and I can't find an explanation for. I downloaded [15128] in stead of [15109] and it worked!

That's strange, there should be no difference in behavior  between those two versions.
 
I am going to do a diff and see what are the differences. I just thought I 'd update you.
Also, I added the 'os.path.normpath' to 
{{{
 if env_path !=  os.path.normpath(self.env.path):
}}}
but it didn't help.

Any suggestions where to look? 

You could log the env_path values to see if we can spot an issue:
self.log.debug("TicketMoverPlugin: env_path = %s, self.env.path = %s", env_path, self.env.path)
 

Ahmed M.

unread,
Dec 21, 2015, 11:51:59 PM12/21/15
to Trac Users, sab...@gmail.com, ryan.j...@gmail.com
see my comments below


On Monday, December 21, 2015 at 9:27:22 PM UTC-5, RjOllos wrote:


On Monday, December 21, 2015 at 5:56:19 PM UTC-8, Ahmed M. wrote:
Here is something I tried and I can't find an explanation for. I downloaded [15128] in stead of [15109] and it worked!

That's strange, there should be no difference in behavior  between those two versions. 
That's what I thought! I did a diff and there is no major differences that I can find.  
 
I am going to do a diff and see what are the differences. I just thought I 'd update you.
Also, I added the 'os.path.normpath' to 
{{{
 if env_path !=  os.path.normpath(self.env.path):
}}}
but it didn't help.

Any suggestions where to look? 

You could log the env_path values to see if we can spot an issue:
self.log.debug("TicketMoverPlugin: env_path = %s, self.env.path = %s", env_path, self.env.path)
I added the debugging message and at first glance I couldn't see any difference. I gave it a closer look and discovered that the comparison yields: env_path = C:\trac\swtrac, self.env.path = c:\trac\swtrac, the comparison was case sensitive. the first one has an upper case C while the other one has a lowers case c. updated my wsgi file and used lower case in all of my references and it worked.
This was a good learning exercise for me. Thank you so much!
 

RjOllos

unread,
Dec 21, 2015, 11:59:42 PM12/21/15
to Trac Users, sab...@gmail.com, ryan.j...@gmail.com
Good find! I'll modify the code to call os.path.normcase on both sides of the operator.

- Ryan

RjOllos

unread,
Dec 22, 2015, 12:20:21 AM12/22/15
to Trac Users, sab...@gmail.com, ryan.j...@gmail.com
Reply all
Reply to author
Forward
0 new messages