On Mon, Oct 12, 2009 at 11:03 AM, Roger Oberholtzer
<[email protected]> wrote:
>
> On Mon, 2009-10-12 at 09:39 -0500, Olemis Lang wrote:
>> On Sun, Oct 11, 2009 at 12:51 PM, Roger Oberholtzer
>> <[email protected]> wrote:
>> > On Fri, 2009-10-09 at 09:58 -0500, Olemis Lang wrote:
>> >
>> >> I thought I had removed that dependency since version 1.2.1 . Let me
>> >> see ... yes it shouldn't have done that. I don use Babel any more
>> >>
>> >> Please, could you try to install Babel and try again ?
>> >
>> > I added Babel. I did not see any error. I restarted Apache, but I do not
>> > see any reference to Babel in the log. This includes the message about
>> > it not being found.
>>
>> There's something weird in there.
>>
>>   - Firstly the following line indicates that plugin is loaded but also
>>     that it did not load any GViz provider (i.e. data sources ;o)
>>     Are they enabled ?
>>
>> {{{
>> 2009-10-11 19:31:13,036 Trac[api] DEBUG: IG: Providers cache ({},)
>> }}}
>>
>> In my test environment the log looks like this
>>
>> {{{
>> 2009-08-10 13:36:59,580 Trac[api] DEBUG: IG: Providers cache
>> ({'/gviz/ticket/fields': <tracgviz.ticket.GVizTicketFields object at
>> 0x8f5da0c>, '/gviz/wiki/index': <tracgviz.wiki.GVizWikiPages object at
>
> ...
>
>> So you're definitely missing a lot of things, everything indeed  :-/
>
> Is there no additional debug I can enable in TracGViz?
>

Well all debug goes to trac.log through Trac logging API, but if
components are not loaded then there's nothing to log ... what I don't
understand is why is it happening ...

> I wonder about these lines in my log:
>
>  Skipping "trac.mimeview.txtl = trac.mimeview.txtl [textile]":
>        ("DistributionNotFound: textile>=2.0" not found)
>
> Could this result in something missing that makes TracGViz unhappy?

Nop, they're irrelevant. I know them very well , I didn't include a
data source for mime types main because of that ;o)

[...]
>
>> {{{
>> [components]
>> tracgviz.* = enabled
>> }}}
>
> In the Admin interface, there is only one item offered in TracGViz,
> whcih is "TracGVizSystem", which I have set to enabled. Also, my
> trac.ini does contain:
>
> {{{
> [components]
> tracgviz.* = enabled
> }}}
>

Well, I believe you ...

>
> I think all my other plugins are working. I will check again just to be
> sure. I think (95% certainty) that it is only TracGViz that is hesitant
> to start. And yet it offers no complaint. Such a polite plugin.
>

Ahhhhh !!!   politeness of the plugin is a genetic side-effect ;o)

Please try this one ... :

in tracgviz/__init__.py file you'll find code like the one shown
below. Please remove the comment before `raise` statement, and try
again.

Since you get nothing but TracGVizSystem then that means that
`XmlRpcPlugin` is missing and also that you skipped that part when you
installed the plugin (and that's documented [1]_ ;o)

Is this the case ?

{{{
#!python

try:
    from api import TracGVizSystem
    from rpc import *
    from stdhash import *
    from proto import GViz_0_5
    from stdfmt import GVizJsonEncoder, GVizHtmlEncoder, GVizCSVEncoder
    from extfmt import *
    from ticket import *
    from wiki import *
    from search import *
    from timeline import *
    from vcs import *
    from ig import *
    msg = 'Ok'
except Exception, exc:
#    raise
    msg = "IG: Exception %s raised: '%s'" % (exc.__class__.__name__, str(exc))
}}}

How could I forget that one ? would you all help me with my funeral ?

.. [1] Trac integration with Google Visualization API
        
(https://opensvn.csie.org/traccgi/swlcu/wiki/En/Devel/TracGViz#Dependencies)

-- 
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article:

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to