From: [email protected] [mailto:[email protected]] On 
Behalf Of RjOllos
Sent: Monday, April 07, 2014 7:55 PM
To: [email protected]
Subject: Re: [Trac] The ticket field 'owner' is invalid



On Monday, April 7, 2014 10:43:39 AM UTC-7, CP wrote:


From: [email protected]<javascript:> 
[mailto:[email protected]<javascript:>] On Behalf Of RjOllos
Sent: Monday, April 07, 2014 1:25 AM
To: [email protected]<javascript:>
Subject: Re: [Trac] The ticket field 'owner' is invalid

On Wednesday, April 2, 2014 4:05:36 PM UTC-7, CP wrote:

________________________________
From: [email protected]<mailto:[email protected]> 
[[email protected]] on behalf of RjOllos [[email protected]]
Sent: Wednesday, April 02, 2014 5:01 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [Trac] The ticket field 'owner' is invalid
On Wednesday, April 2, 2014 7:25:09 AM UTC-7, CP wrote:
From: Patterson, Candace
Sent: Wednesday, March 12, 2014 11:05 AM
To: [email protected]<http://UrlBlockedError.aspx>
Subject: RE: [Trac] The ticket field 'owner' is invalid


On Tuesday, March 11, 2014 7:07:43 PM UTC-7, RjOllos wrote:
On Tuesday, March 11, 2014 3:58:01 PM UTC-7, CP wrote:
When trying to assign the owner field, I received this error:

Warning: The ticket field 'owner' is invalid: Access denied to modifying owner

I also used an account with TRAC_ADMIN privileges, and I received the same 
error when trying to assign the owner.

I then restarted Python/Trac, and that fixed the problem.  This has happened on 
multiple occasions, but sometimes it works okay.  My only thought is that maybe 
my plugins are conflicting, and maybe restarting allows them to be loaded in a 
different order???


Here is some additional information that may or may not be relevant.  I am 
using Trac 0.12.  I am running two instances of Trac on the same server, and I 
don't know if that is a problem.

The first instance ("Trac 1") uses these plugins:

AdvancedTicketWorkflowPlugin-0.11dev-py2.7
BlackMagicTicketTweaks-0.11r1-py2.7
CondFieldsGenshiPlugin-0.2-py2.7
GroupTicketFields-0.0.1dev-py2.7
ticket_clone.py
TicketValidator-0.1-py2.7
trac_WorkflowNotificationPlugin-0.4-py2.7
TracAnnouncer-0.11.1-py2.7
TracCustomFieldAdmin-0.2.8-py2.7
TracDynamicFields-1.2.3-py2.7
TracTicketValidator-0.1-py2.7

The second Trac instance ("Trac 2") uses all of the above plugins plus the 
following:

TracAccountManager-0.4.3-py2.7
TracDateField-2.0.0dev-py2.7
TracVirtualTicketPermissions-1.0.0-py2.7

I looked at the log file of Trac 1, and noticed that Trac 1 is checking user's 
permissions against the permissions that are only in Trac 2.

Also, in Trac 2, I am using the BlackMagic plugin to set owner.permission and 
owner.ondenial, but I am not doing this in Trac 1 (where I am having the 
problem).

Any help or suggestions will be much appreciated!

Thanks,
Candace Patterson


The warning/error is raised by an ITicketManipulator:
http://trac.edgewall.org/browser/branches/1.0-stable/trac/ticket/web_ui.py?marks=1291-1293&rev=12500#L1286
Specifically, the BlackMagicTicketTweaksPlugin:
http://trac-hacks.org/browser/blackmagictickettweaksplugin/0.12/blackmagic/blackmagic.py?marks=268-269&rev=13685#L257

I think the issue is that BlackMagicTicketTweaks is not thread-safe:
http://trac-hacks.org/browser/blackmagictickettweaksplugin/0.12/blackmagic/blackmagic.py?marks=43-48&rev=13685#L26

I'm looking at whether this can be easily fixed.


Here is a ticket in which osimons has already documented the problem:
http://trac-hacks.org/ticket/7872#comment:3

I pushed an untested fix. Could you please give it a try and report back?
http://trac-hacks.org/changeset/13734

There may still be a problem with the blockedTickets and extra_permissions 
attributes, but it will likely be much less severe and you may not even notice.
----------------------------------------------

Thanks so much!  I loaded the BlackMagic 11.2 plugin that you modified, and so 
far it appears to work properly.  I will continue to monitor it for errors, but 
currently the log file isn’t showing any permission validations against the 
Trac2-only permissions.  So, I think that is a good sign.  I will report back 
if the problem returns.  Thanks again!

Candace


Update April 2, 2014:

I have noticed that my new BlackMagic 11.2 plugin isn’t loading/importing 
properly.  Below are the errors from the log file.  By the way, I loaded my old 
plugin 11.1 (the one with the permission problems), and it loads properly.  Any 
suggestions?

Thanks a lot,
Candace

Trac[loader] DEBUG: Loading blackmagic from 
d:\tracracrs\plugins\blackmagictickettweaks-0.11.2-py2.7.egg
Trac[loader] ERROR: Skipping "blackmagic = blackmagic":
Traceback (most recent call last):
  File "C:\Python27\lib\site-packages\trac\loader.py", line 68, in _load_eggs
    entry.load(require=True)
  File "C:\Python27\lib\site-packages\pkg_resources.py", line 1954, in load
    entry = __import__(self.module_name, globals(),globals(), ['__name__'])
ImportError: No module named blackmagic
It was working for a while and then stopped working?

The plugin version wasn't bumped for a while, so you could be running one of 
several versions:
http://trac-hacks.org/log/blackmagictickettweaksplugin/0.11
The version was bumped to 0.11r1 was @7886. Everything since then looks pretty 
harmless though.

I suggest installing from the 0.12 branch, but it looks like there may be no 
differences between the two branches.
http://trac-hacks.org/log/blackmagictickettweaksplugin/0.12

I will do some more investigation this evening.

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

Okay, thanks.  No, it never did work, and I just realized that yesterday.  I 
assumed it was working because I no longer got errors relating to the 
permissions.  I was using Trac yesterday and noticed that all the fields were 
available for modification by anyone instead of only the people with the proper 
permissions.  And I also noticed that the tips weren't showing up.  So, I 
checked the log file and realized that the new plugin never did load properly.  
I went back to March 12 (when I installed the new plugin), and that's when I 
started getting the errors listed above.

I used the Changeset 13734 (from your link above) to install the 11.2 update.  
How can I tell what 11.1 version I had previously?

Unfortunately, as far as I know there isn't a way to know what version you had 
previously, since the egg isn't tagged with the SVN revision number. We would 
have to compare the source code.

I'm not able to reproduce. What command did you use to build the egg?

Could you try the 0.12 branch before we dig any deeper?


I tried the 0.12 and received the same errors in the log file.

I used this command for installing the plugin:
C:\Downloads\changeset_13734\blackmagictickettweaksplugin\0.11> python setup.py 
install

My original BlackMagic plugin was loaded on July 23, 2012.  I found the zip 
file that I originally downloaded, and it is tagged as version 11760.  I just 
now added your latest changes (from March 11, 2014) to this original 
blackmagic.py file (11760),  and it appears to have worked!  The permission 
checks and tips are now working on the tickets, and the log file indicates that 
the plugin is loading successfully and that the permissions are being checked 
against the correct instance of the Trac environment.

Does this make sense that such an old version of the plugin would work better 
than a newer one?  Any idea why I can use only an older version?  Will I 
eventually need the additional code that is in the current version?   Thanks!

I don't see any changes between r11760 and r13817 that I could imagine to cause 
any issues:
http://trac-hacks.org/log/blackmagictickettweaksplugin

You could try installing each revision of the plugin, and if you find the 
revision in which it fails, that will give us something to focus on.


I installed 8 revisions (12824,12864,12948,13281,13282,13685,13734,13817), and 
all of them worked.  This includes the one you modified on March 11, 2014.  I 
must have done something wrong during installation that caused the plugin not 
to load.  ???  I don’t know what I would have done incorrectly.  Anyway, it 
appears that your fix works.  Just an error on my part somehow.  Sorry for the 
trouble.  And thanks so much for your help!

--
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]<mailto:[email protected]>.
To post to this group, send email to 
[email protected]<mailto:[email protected]>.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.




The information contained in this email message, including any attachments, is
for the sole use of the intended recipients(s) and may contain confidential and
privileged information.  Any unauthorized review, use, disclosure or 
distribution
is prohibited.  If you are not the intended recipient and have received this
communication in error, please contact the sender by reply e-mail and destroy 
all
copies of the original message.

-- 
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