Report: Issues where Peter hasn't had the last word
All reports| Creation date | Sections | Submitted by | Urgency |
Type |
#0223 CMFMember
hi,
I am trying to install CMFMember Product to my instance which is running on zope2.8.4 and plone2.1 and archetypes 1.2.4(final). while installing am getting this error, please help me out am a new bee to this , any solution / FIX will be appreciated
Transcript
2005-11-15 10:47:25
failed:
Traceback (most recent call last):
File "D:\first-instance\Products\CMFQuickInstallerTool\QuickInstallerTool.py", line 311, in installProduct
res=install(portal)
File "D:\Zope-2.8.4-final\lib\python\Products\ExternalMethod\ExternalMethod.py", line 225, in __call__
try: return f(*args, **kw)
File "D:\first-instance\Products\CMFMember\Extensions\Install.py", line 170, in install
installControlTool(self, out)
File "D:\first-instance\Products\CMFMember\Extensions\Install.py", line 73, in installControlTool
if 'cmfmember' not in cp.getGroupIds(): cp.groups.append(ControlTool.group)
AttributeError: 'tuple' object has no attribute 'append'
Thanks & Regards,
Tanveer
3 years and 1 month and 3 weeks old
#0800 Intermittent Site Error
I am having trouble with an intermittent site error message. The error goes away when I restart zope, and it have even gone away when I go to another page or in another browser. I can't seem to reproduce it, other than leaving the window open for a while and coming back to it and clicking on any link.
I am working from svn, updated just today to rev300 I think? I am running the cookiecrumbler addin. I have 2 ITPs running under the one root, the first is helpdesk, the second is bbbs. The latter is an addin of the former (so I can see tickets on both from the helpdesk one).
Below is the error message and below that my zope info. Let me know what logs you need.:
Site Error
An error was encountered while publishing this resource.
KeyError
Sorry, a site error occurred.
Traceback (innermost last):
* Module ZPublisher.Publish, line 202, in publish_module_standard
* Module ZPublisher.Publish, line 150, in publish
* Module Zope2.App.startup, line 221, in zpublisher_exception_hook
* Module ZPublisher.Publish, line 119, in publish
* Module ZPublisher.mapply, line 88, in mapply
* Module ZPublisher.Publish, line 42, in call_object
* Module Shared.DC.Scripts.Bindings, line 313, in __call__
* Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
* Module Products.CheckoutableTemplates.CTFiles, line 336, in _exec
* Module Products.PageTemplates.PageTemplateFile, line 129, in _exec
* Module Products.PageTemplates.PageTemplate, line 89, in pt_render
* Module zope.pagetemplate.pagetemplate, line 117, in pt_render
* Module zope.tal.talinterpreter, line 271, in __call__
* Module zope.tal.talinterpreter, line 346, in interpret
* Module zope.tal.talinterpreter, line 891, in do_useMacro
* Module zope.tal.talinterpreter, line 346, in interpret
* Module zope.tal.talinterpreter, line 536, in do_optTag_tal
* Module zope.tal.talinterpreter, line 521, in do_optTag
* Module zope.tal.talinterpreter, line 516, in no_tag
* Module zope.tal.talinterpreter, line 346, in interpret
* Module zope.tal.talinterpreter, line 534, in do_optTag_tal
* Module zope.tal.talinterpreter, line 516, in no_tag
* Module zope.tal.talinterpreter, line 346, in interpret
* Module zope.tal.talinterpreter, line 623, in do_insertText_tal
* Module Products.PageTemplates.Expressions, line 228, in evaluateText
* Module zope.tales.tales, line 696, in evaluate
URL: StandardHeader
Line 23, Column 0
Expression: <PathExpr standard:'here/testAutoLogin'>
Names:
{'container': <IssueTracker at /bbbs>,
'context': <IssueTracker at /bbbs>,
'default': <object object at 0xb7dfd528>,
'here': <IssueTracker at /bbbs>,
'loop': {},
'nothing': None,
'options': {'args': ()},
'repeat': <Products.PageTemplates.Expressions.SafeMapping object at 0xb707d0ec>,
'request': <HTTPRequest, URL=http://helpdesk.mydomain.com:81/bbbs/index_html>,
'root': <Application at >,
'template': <_CTPageTemplateFile at /bbbs/index_html>,
'user': <IssueUser 'jp'>}
* Module zope.tales.expressions, line 217, in __call__
* Module Products.PageTemplates.Expressions, line 161, in _eval
* Module Products.PageTemplates.Expressions, line 123, in render
* Module Products.IssueTrackerProduct.IssueTracker, line 10912, in testAutoLogin
* Module Products.IssueTrackerProduct.IssueTracker, line 5282, in set_session
* Module ZPublisher.HTTPRequest, line 1239, in __getattr__
* Module ZPublisher.HTTPRequest, line 1188, in get
* Module Products.Sessions.SessionDataManager, line 95, in getSessionData
* Module Products.Sessions.SessionDataManager, line 182, in _getSessionDataObject
* Module Products.Transience.Transience, line 837, in new_or_existing
* Module Products.Transience.Transience, line 449, in __setitem__
KeyError: 1226370960 (Also, the following error occurred while attempting to render the standard error message, please see the event log for full details: 1226370960)
Troubleshooting Suggestions
* The URL may be incorrect.
* The parameters passed to this resource may be incorrect.
* A resource that this resource relies on may be encountering an error.
For more detailed information about the error, please refer to the error log.
If the error persists please contact the site maintainer. Thank you for your patience.
And my zope info:
Zope Version (Zope 2.10.5-final, python 2.4.5, linux2) Python Version 2.4.5 (#0002, Jul 31 2008, 18:51:48) [GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] System Platform linux2 SOFTWARE_HOME /usr/lib/zope2.10/lib/python ZOPE_HOME /usr/lib/zope2.10 INSTANCE_HOME /var/lib/zope2.10/instance/sandbox CLIENT_HOME /var/lib/zope2.10/instance/sandbox/var Network Services ZServer.HTTPServer.zhttp_server (Port: 81)
1 month and 3 weeks and 6 days old
Just an update, it seems like it is cookie or session related. If I get the error message, I can retype the url (go to root) and the page will come up fine. If I click on the same ticket I was viewing it looks fine.
Update again. As soon as the pop3 connector created a ticket or an update I got the site error. It affects both IT instances, but the actual zope instance is unaffected. Any ideas?
A recent change in IssueTrackerProduct allows to see the history of changes to an issue. However, changes to custom fields that should only be viewable by some roles are displayed to all.
Jack
2 months and 3 weeks old
An error occured when I tried to...
Submit first issue
--------------------------------------------------
Error type: NoACLAdderError
Error value: No ACL user object found
Traceback (innermost last):
Module ZPublisher.Publish, line 119, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish, line 42, in call_object
Module Products.IssueTrackerProduct.IssueTracker, line 3622, in SubmitIssue
Module Products.IssueTrackerProduct.IssueTracker, line 3776, in createIssueObject
NoACLAdderError: No ACL user object found
4 months and 3 weeks and 4 days old
Don't install the issuetracker inside a Plone instance. It's a known bug that I need to find time to work on.
I installed in the Zope instance created with Plone Unified Installer, but not in a Plone instance. When I ran the unit tests directly from the Zope instance there were no errors.
I added IssueTracker from the Zope 'Add' box and without ever starting the Plone site from within Zope.
If you are willing, and can share with me any clues, I'd be willing to give this some time. Otherwise I'll need to move on.
I noticed that rss feeds are visible, even if the desk is set to disallow anonymous access.
Is there any way to secure it?
I labeled this as a bug, I hope that isn't mislabeled. If it is, sorry. I also set it as high because I can't go live until I know how to secure it. Forgive the urgency.
11 months and 11 days old
Sorry I forgot the platform information:
Zope Version
(Zope 2.10.3-final, python 2.4.4, linux2) (installed from apt repository)
IT Version: 0.8.3
That's odd. I thought I had taken care of that.
How did you "disallow anonymous access"? Using the big option in the setup?
Yes, and to test I just created a new IT under /sample/sample with the following choices:
stage:
- software/applications develpment 2. defaults 3. defaults 4. defaults 5. defaults 6. defaults (creation date) 7. defaults (don't really know what a notifyable is yet) 8. defaults (none added) 9. defaults 10. (01-02-2008 06:56) and clever date= yes 11. defaults Went straight to /sample/sample/manage_ManagementUsers and hit the big disallow button.
opened /sample/sample/rss.xml in IE (I use firefox) and it displayed, went to the root of that IT and cancelled login prompt and tried a few links, all access denied, but I can still see the rss.xml.
Thanks for looking. I was quite surprised when I saw it. I grepped the product/IssueTracker dir and found a couple files with reference to rss.xml. IssueTracker.py and StandardHeader.zpt.
The former seems to have what looks to me like a declaration to check permissions first. But I seriously know nothing about python.
04159: security.declarePublic(rss.xml)
04199: """ return RSS XML 1.0 """
04210: rss_url = root.absolute_url()+/rss.xml
04309: """ return RSS XML """
12304: setattr(IssueTracker, rss.xml, IssueTracker.RSS10)
Fixed and unit test written to confirm it. I've checked it in to the SVN trunk (if that means anything to you).
Indeed it does, I will find the checkout instructions. A question though, is the rest of the SVN trunk stable enough for production?
It works. And is pretty painless. Thank you very much.
#0214 Adding custom fields
Is it possible to add custom fields to an issue? We are looking to add fields such as organisation who raised issue to allow better monitoring and reporting.
3 years and 2 months and 2 weeks old
You can add customer fields by pressing a button
No there is no such function. The reason for that is that it's very hard to do from a programming point of view. Getting it to work just roughly isn't hard but to really nail it right is hard. So far I haven't seen any uniformity in what extra fields people ask for but if there was I'd be able to program it into the core and make it part of the Advanced Properties as an option.
Your best bet is to either write a monkey patch in combination with using CheckoutableTemplates.
What is the use of Field Addition in CUSTOM Tab in PROPERTIES??
How about a generic couple of fields, disabled by default. Something where you could label them as you like and turn them on. I would think that would satisfy the need more fields crowd while keeping the programming uniformity. What do you think?
btw, awesome project!
After enabling the "Show Confidential Issue" option, users are unable to view issues marked as confidential which they created. The issues do not show up in the lists (list issues or complete list), but they do show up in recent items but when they are click nothing comes up.
Some background info: I modified the page templates to mark issues as confidential by default as explained here: http://www.issuetrackerproduct.com/Real/0278/ Is it possible that something has changed since this solution was given that would break viewing now?
1 year and 3 months old
I've tested the "Show Confidential Issue" option with a clean product (I did not modify the page temple) and noticed the same problem: users cannot view their own private issues, but managers can.
To prove it, try adding an issue here on this issuetracker and tick the Confidential checkbox and you should be able to see it.
Will be part of the next release. In SVN version already.
I've switched to the SVN version. But confidential issues don't seem to work at all. I created 2 users and made them Issue Tracker User and they can see each other's issues.
I can't reproduce that. I set up a site with two IssueTracker Users and the second one couldn't see the others issue. However, if you know the direct URL to the issue perhaps it's possible.
I've setup two trackers with the svn version and had the same issue (private issues are not private). I'll email you the details to one of the sites.
#0291 ACL_Adder
When saving an issue it shows me a page with error:
System error
The IssueTrackerProduct encountered a system error that was unexpected. The errors were:
Error type: NoACLAdder
Error value: No ACL user object found
How is your user account set up? What kind of user folder do you use that you are logged in to when you're adding the user.
On holiday from today but I'll be able to help you when I get back in 2 weeks. In the meantime, please provide as much info about your authentication setup as possible. Thanks for the bug report.
As reported to Peter, I also have this problem. I'm running IssueTracker 0.72 under Plone 2.5, with Tracker instance in the root of the Plone instance.
Info:
IssueTracker 0.72
Plone 2.5,
Zope (Zope 2.9.3-, python 2.4.3, win32),
Python 2.4.3 (#0069, Mar 29 2006, 17:35:34) [MSC v.1310 32 bit (Intel)],
PIL 1.1.5
I am also experiencing the same issue. I have the issuetrackerproduct installed in my plone root folder. Plone is authenicating successfully via a ActiveDirectory Multi Plugin in a Pluggable Auth Service acl_users folder. I have no user folder in the issuetrackerproduct.
Info:
IssueTracker 0.72
Plone 2.5
Zope 2.9.4
python 2.4.3
gentoo w/ 2.6.16 linux kernel (gentoo hardened sources)
Thank you for any help you can provide.
Hi Peter,
I was logged in as Admin for zope when I created the issuetracker. I created the users in acl_users under my issuetracker.
Hat schon jemand 'ne Loesung fuer das Problem? Habe den IssueTracker heute erst entdeckt und installiert, aber leider mit dem gleichen Fehler. Mein System laeuft unter Fedora 5, ansonsten die gleiche Konstellation wie schon beschrieben.
After installing cookie crumblerISTP, it works - :) Nice login page.
Thanks Peter.
I can not get this to work. How did you make it work by installing cookie crumbler?
we have two servers both running ZOPE
1. www.abc.com
2. www.xyz.com
i have 100 Tracker instances running on www.abc.com which i want to move to www.xyz.com
a. WITH ALL DATA
b. updated links
We tried it manually and following are the steps to do it manually
1. I went into www.abc.com ,
2. i selected a tracker,
3. clicked import/export and
4. saved that tracker as a zexp file
5. Then I uploaded this ZEXP file to www.xyz.com (under /var/lib/zope/import folder)
6. then i logged in as Admin in www.xyz.com and imported the ZEXP file
NOTE: i tried to move the .fs file but it did not work, also .fs files are quite large and difficult to manage.
SOLUTION REQUIRED For Following
Do we have Scripts for exporting instances of Trackers ?
Do we have scripts for importing the tracker insataances?
if i can get such scripts it will be helpful to automate this process.
Thanks in Advance
Mahesh
2 years and 3 months and 11 days old
No import/export scripts specifically for IssueTrackerProduct. You seem to have successfully used Zope's own export/import.
What's really the problem?
Number of TRackers is the real problem, there are more than 150 trackers and doing this manually wud take lot of time.
So i wanted to create a Cron Job (on server 1 abc.com) for exporting all the trackers to ZEXP format (which can be done at midnight) and then next day i will create another Cron job for importing all the trackers on server 2 (www.xyz.com)
this way lot of time and manual work wud not be required.
Does Zope itself has some scrips or commands ??
I recently got a problem with spam. It seems that some robot or person is entering large lists of html links into Follow-ups on issues. So far I dealt with it by erasing the follow-ups and sending a friendly email to the address entered on the follow-up requesting that they kindly stop.
These follow-ups generate messages sent to all those involved in the targeted issue. A kind of backdoor spam which I think will discourage people from entering their email with the issue.
Does anyone have ideas on how to suppress this kind of abuse of IssueTracker?
Thanks!
2 years and 6 months and 13 days old
There is a solution. I just haven't documented it properly yet because I'm still evaluating it. The issuetracker has a ad-hoc builtin spam blocker. What you have to do is to define what words or character expressions mean spam. Like the word "viagra" or combinations words like "viagra" AND "medicine".
I'll let you play with it and you can let me know if it works. Go to the Management tab inside the ZMI of your issuetracker instance. Notice the "Spam protection" sub tab and see if it makes sense. I can email you the list that I use here on real.issuetrackerproduct.com
Thanks for this! I forgot to get back to you and say that this works pretty well and is quite easy to setup and manage. Unfortunately every so often spam isn't filtered because it doesn't include one of the keywords. Once this happens, one gets a little avalanche of spam which is dammed up by adding new keywords. I am therefore really excited to see that you have incorporated pattern-recognition into 0.7.3!
#0297 Email Format
How to change the email format what is been sent to the users.Currently when a issue is been added the email
<-------------------Email----------------------------->
Subject: Tracker : new issue
Body:
Nish (nish_at_gmail_._com) has entered an issue in eMend and wanted you to know about it, with the following title:
This is a test issue regarding the updation of the issue
The issue can be found at
http://xyz/tracker/TC0009
Nish wrote:
test
-
Tracker <http://xyz/tracker>
<----------------------------------------------------->
How can this email format be changed... Can u tell me which file has to be edited as there is only one file called
SendInboundEmailConfirm_script.py which is not working.. any ideas...
Regards,
Nish
2 years and 5 months and 3 weeks old
There isn't an easy way to change the email format. You're better off looking into writing a little monkey patch.
One more problem is i have two trackers both on different m/c . can u tell me how can i edit the issue.py and issue.pyc file ... I dont know python much but i just want to change the subject in the issue.py file. how can the file be edited... and ideas...or suggestions..
Hi, we are using issue tracker. It is working very fine till now. But now a days, after filing an issue, the "submitted by" is being "no name or email". Infact this is ocurring very arbitrarly and iam unable to understand the reason.
2 years and 8 months and 2 weeks old
How are you logging in? Into a regular Zope ACL user folder or an IssueTracker User Folder?
What version are you using? If CVS, can you upload the CHANGES.txt file here. There have been changes surrounding the catching of names and emails somewhat recently I think. I'm keen to help you help me solve this one.
Does this only happen on issues and not on followups?
well thanks for the quick reply.
1. We don't have any specific login mechanism. we disabled annonymous access to Issue Tracker And allowed only people who log into plone.
2. Issue tracker version is the latest,IssueTrackerProduct-0.7.1.
Plone version: 2.1.2. Zope version: 2.8.5-final.
3. Iam not maintaining any zope acl-users. Its only users created in plone would be accessing apps like issuetracker.
4.We are not maintaining any CVS server.
5. "No name or email" is occuring for both issues and their followups.
Hope this would be clear.
I am experiencing the same issue. I am using Zope 2.9.2 and IssueTracker 0.7.1. I have this issue when a logged in user adds and issue. The Add Issue page shows the user name <username> in the User: portion of the window, but I do not see the user id in the form variables anywhere.
I'm not sure if this is related or another issue, but I will mention it here in case it is related. As I was experimenting with IssueTracker if I created an issue prior to logging in, and entered a dummy name and email for the issue, then after logging in, I would still see the user name that I created as a dummy instead of my user name. Hope this helps.
Steve,
No, if you're logged in as some sort of ACL user, the form won't have a hidden variable. It can distinguise that you're logged in in the saving method too. It's more secure that way.
If you create an issue as "dummy" and then log in after, of course the issue you created before you logged in is still going to be "dummy". That's not a mistake. That's like it should and ought to be.
Or... am I not understanding your description.
Ramy, can you do me a favor? On the issues that were saved but now says "Submitted by: No name or email" can you log in with /manage and look at the properties of that issue (or followup) and see what it says in the acl_adder, fromname and email?
In the properties of issue,following things appears
acl_adder: /insight/acl_users,radha
fromname, email are empty.
Thanks Ramy. That's interesting. What kind of object is /insight/acl_users? Is it a Issue Tracker User Folder, a plain zope User Folder or something else? Is the user "radha" still defined in there?
My next conclusion very much depends on what kind of user folder it is. If the user has a fullname and email (ie. it's a Issue Tracker User Folder) then it should not just save the acl_users link to the acl_adder property but also save the fullname and email to the issue as "backup properties" in case the acl user disappears.
well, the "acl_users" is a plain zope folder. For ur convinience, iam also attaching the acl_users window.
It's been fixed. I was able to reproduce it and fix it accurately. It was a stupid misstake.
The only problem now is that since SourceForge's CVS server is dead you can't upgrade my latest changes. I'll get back to you on that later.
We also ge this problem in new versions. What we observe is that there is no relation between the from user/email id and the logged in user.
from user and email id are stored in cookie in browser. If I clear/delete all cookies in browser and post followup (after user login) I still get the "submitted by" is being "no name or email".
More important aspect is that after deleting cookies, if I login with my username/password for zope/plone acl-users and then goto issue tracker, click on add folloup. it will show me form where I can enter any submitted by name or email (irrespective of my username). And this will set the bookie that will be used always. So even if i login and post folloup, it will show submitted by someone whose name is there is the cookie.
Due to this we are not able to track who actually posted the issue.
I think submitted by username(of logged in user) must be shown even if name and email is shown form the cookie.
Ideally I think that issue tracker should use username, email and name as stored in acl user folder of plone if plone users are used in issue tracker. Else cookie form may be used.
Unable to have access to T&M request package. Logged in but access denied.
2 years and 11 months and 4 days old
Sorry for the confusion, I have 80 users on my system - it was just a matter of time before one gets creative after forgetting their password. Please ignore this request.
FYI The Issue Tracker is being used as a Test & Measurement Help Desk which tracks production problems on out manufacturing site. Hence the T&M Request.
Thanks for your continued service.
An error occured when I tried to open Properties in ZMI for my IssueTrackerProduct instance. This was after successfully configuring using the Wizard at installation.
IssueTrackerProduct version 0.6.13 CVS
--------------------------------------------------
Error type: Document Template Parse Error
Error value: unexpected end tag, for tag </dtml-let>, on line 1053 of manage_editIssueTrackerPropertiesForm<p>
Traceback (innermost last):
Module ZPublisher.Publish, line 113, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish, line 40, in call_object
Module Shared.DC.Scripts.Bindings, line 311, in __call__
Module Shared.DC.Scripts.Bindings, line 348, in _bindAndExec
Module Products.CheckoutableTemplates.CTFiles, line 265, in _exec
Module App.special_dtml, line 113, in _exec
Module App.special_dtml, line 47, in _cook_check
- __traceback_info__: /usr/local/zope/instance/Products/IssueTrackerProduct/dtml/editIssueTrackerPropertiesForm.dtml
Module DocumentTemplate.DT_String, line 342, in cook
Module DocumentTemplate.DT_String, line 172, in parse
Module DocumentTemplate.DT_String, line 221, in parse_block
Module DocumentTemplate.DT_String, line 260, in parse_close
Module DocumentTemplate.DT_String, line 253, in parse_close
Module DocumentTemplate.DT_String, line 60, in parse_error
Document Template Parse Error: unexpected end tag, for tag </dtml-let>, on line 1053 of manage_editIssueTrackerPropertiesForm<p>
3 years and 1 month and 2 weeks old
Right you are! I'm clumsy and will fix this after my breakfast and cycling to my office.
Fixed. I've put it in CVS but since sf.net is the slowest CVS in the known universe I've uploaded a copy of the latest editIssueTrackerPropertiesForm here.
Excellent! Thanks, and Happy Holidays!
Have option to allow Description field to be exported to CSV or just export all of the time.
1 month and 3 days old
I asked about this before but never got an answer. Hope we get one.
Eric, I did reply to your email. Also replied about sending a patch rather than svn write access.
Peter, was this request implemented in a patch that I could get? Thanks.
Peter, Didn't think changing it in the List Issues of issue tracker would also change it in the csv export. Doh.
Figured it was two separate things I would've had to do.
Pat, the place to start looking is in IssueTracker.py
Search for CSVExport and the function after that does the csv header
An error occured when I tried to preview a issue, because the Alias of Notifyable have a non ASCII character. There is any solution? Thanks, Manuel
--------------------------------------------------
Error type: UnicodeDecodeError
Error value: 'ascii' codec can't decode byte 0xf3 in position 6: ordinal not in range(128)
Traceback (innermost last):
Module ZPublisher.Publish, line 119, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish, line 42, in call_object
Module Products.IssueTrackerProduct.IssueTracker, line 11708, in AddIssue
Module Shared.DC.Scripts.Bindings, line 313, in __call__
Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
Module Products.PageTemplates.PageTemplateFile, line 129, in _exec
Module Products.PageTemplates.PageTemplate, line 89, in pt_render
Module zope.pagetemplate.pagetemplate, line 117, in pt_render
Module zope.tal.talinterpreter, line 271, in __call__
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 891, in do_useMacro
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 536, in do_optTag_tal
Module zope.tal.talinterpreter, line 521, in do_optTag
Module zope.tal.talinterpreter, line 516, in no_tag
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 949, in do_defineSlot
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 855, in do_condition
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 534, in do_optTag_tal
Module zope.tal.talinterpreter, line 516, in no_tag
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 745, in do_insertStructure_tal
Module Products.PageTemplates.Expressions, line 221, in evaluateStructure
Module zope.tales.tales, line 696, in evaluate
- URL: AddIssueTemplate
- Line 43, Column 0
- Expression: <PathExpr standard:'here/preview_issue'>
- Names:
{'container': <IssueTracker at /helpdesk>,
'context': <IssueTracker at /helpdesk>,
'default': <object object at 0x2b11e9be5200>,
'here': <IssueTracker at /helpdesk>,
'loop': {},
'nothing': None,
'options': {'args': (<IssueTracker at /helpdesk>,
<HTTPRequest, URL=http://91.121.85.79:9001/helpdesk/AddIssue>),
'draft_saved': True},
'repeat': <Products.PageTemplates.Expressions.SafeMapping object at 0x2b11ec173560>,
'request': <HTTPRequest, URL=http://91.121.85.79:9001/helpdesk/AddIssue>,
'root': <Application at >,
'template': <PageTemplateFile at /helpdesk/AddIssueTemplate>,
'user': <PropertiedUser 'admin'>}
Module zope.tales.expressions, line 217, in __call__
Module Products.PageTemplates.Expressions, line 161, in _eval
Module Products.PageTemplates.Expressions, line 111, in render
Module Products.PageTemplates.ZRPythonExpr, line 79, in call_with_ns
Module Shared.DC.Scripts.Bindings, line 327, in __render_with_namespace__
Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
Module Products.PageTemplates.PageTemplateFile, line 129, in _exec
Module Products.PageTemplates.PageTemplate, line 89, in pt_render
Module zope.pagetemplate.pagetemplate, line 117, in pt_render
Module zope.tal.talinterpreter, line 271, in __call__
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 586, in do_setLocal_tal
Module zope.tales.tales, line 696, in evaluate
- URL: preview_issue
- Line 99, Column 0
- Expression: <PythonExpr here.Always2Notify(format='merged', requireemail=1, include_assignee=1)>
- Names:
{'container': <IssueTracker at /helpdesk>,
'context': <IssueTracker at /helpdesk>,
'default': <object object at 0x2b11e9be5200>,
'here': <IssueTracker at /helpdesk>,
'loop': {},
'nothing': None,
'options': {'args': ()},
'repeat': <Products.PageTemplates.Expressions.SafeMapping object at 0x2b11ec1889e0>,
'request': <HTTPRequest, URL=http://91.121.85.79:9001/helpdesk/AddIssue>,
'root': <Application at >,
'template': <PageTemplateFile at /helpdesk/preview_issue>,
'user': <PropertiedUser 'admin'>}
Module Products.PageTemplates.ZRPythonExpr, line 49, in __call__
- __traceback_info__: here.Always2Notify(format='merged', requireemail=1, include_assignee=1)
Module PythonExpr, line 1, in <expression>
Module Products.IssueTrackerProduct.IssueTracker, line 5871, in Always2Notify
Module Products.IssueTrackerProduct.IssueTracker, line 6101, in ShowNameEmail
Module Products.IssueTrackerProduct.Utils, line 445, in html_entity_fixer
UnicodeDecodeError: 'ascii' codec can't decode byte 0xf3 in position 6: ordinal not in range(128)
1 month and 3 weeks and 6 days old
An error occured when I tried to create a test issue with non ASCII characters. There is any solution? Thanks, Manuel
--------------------------------------------------
Error type: UnicodeDecodeError
Error value: 'ascii' codec can't decode byte 0xf3 in position 6: ordinal not in range(128)
Traceback (innermost last):
Module ZPublisher.Publish, line 119, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish, line 42, in call_object
Module Products.IssueTrackerProduct.IssueTracker, line 11708, in AddIssue
Module Shared.DC.Scripts.Bindings, line 313, in __call__
Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
Module Products.PageTemplates.PageTemplateFile, line 129, in _exec
Module Products.PageTemplates.PageTemplate, line 89, in pt_render
Module zope.pagetemplate.pagetemplate, line 117, in pt_render
Module zope.tal.talinterpreter, line 271, in __call__
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 891, in do_useMacro
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 536, in do_optTag_tal
Module zope.tal.talinterpreter, line 521, in do_optTag
Module zope.tal.talinterpreter, line 516, in no_tag
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 949, in do_defineSlot
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 855, in do_condition
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 534, in do_optTag_tal
Module zope.tal.talinterpreter, line 516, in no_tag
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 745, in do_insertStructure_tal
Module Products.PageTemplates.Expressions, line 221, in evaluateStructure
Module zope.tales.tales, line 696, in evaluate
- URL: AddIssueTemplate
- Line 43, Column 0
- Expression: <PathExpr standard:'here/preview_issue'>
- Names:
{'container': <IssueTracker at /helpdesk>,
'context': <IssueTracker at /helpdesk>,
'default': <object object at 0x2b11e9be5200>,
'here': <IssueTracker at /helpdesk>,
'loop': {},
'nothing': None,
'options': {'args': (<IssueTracker at /helpdesk>,
<HTTPRequest, URL=http://91.121.85.79:9001/helpdesk/AddIssue>),
'draft_saved': True},
'repeat': <Products.PageTemplates.Expressions.SafeMapping object at 0x2b11f3955e18>,
'request': <HTTPRequest, URL=http://91.121.85.79:9001/helpdesk/AddIssue>,
'root': <Application at >,
'template': <PageTemplateFile at /helpdesk/AddIssueTemplate>,
'user': <PropertiedUser 'admin'>}
Module zope.tales.expressions, line 217, in __call__
Module Products.PageTemplates.Expressions, line 161, in _eval
Module Products.PageTemplates.Expressions, line 111, in render
Module Products.PageTemplates.ZRPythonExpr, line 79, in call_with_ns
Module Shared.DC.Scripts.Bindings, line 327, in __render_with_namespace__
Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
Module Products.PageTemplates.PageTemplateFile, line 129, in _exec
Module Products.PageTemplates.PageTemplate, line 89, in pt_render
Module zope.pagetemplate.pagetemplate, line 117, in pt_render
Module zope.tal.talinterpreter, line 271, in __call__
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 586, in do_setLocal_tal
Module zope.tales.tales, line 696, in evaluate
- URL: preview_issue
- Line 99, Column 0
- Expression: <PythonExpr here.Always2Notify(format='merged', requireemail=1, include_assignee=1)>
- Names:
{'container': <IssueTracker at /helpdesk>,
'context': <IssueTracker at /helpdesk>,
'default': <object object at 0x2b11e9be5200>,
'here': <IssueTracker at /helpdesk>,
'loop': {},
'nothing': None,
'options': {'args': ()},
'repeat': <Products.PageTemplates.Expressions.SafeMapping object at 0x2b11f396c518>,
'request': <HTTPRequest, URL=http://91.121.85.79:9001/helpdesk/AddIssue>,
'root': <Application at >,
'template': <PageTemplateFile at /helpdesk/preview_issue>,
'user': <PropertiedUser 'admin'>}
Module Products.PageTemplates.ZRPythonExpr, line 49, in __call__
- __traceback_info__: here.Always2Notify(format='merged', requireemail=1, include_assignee=1)
Module PythonExpr, line 1, in <expression>
Module Products.IssueTrackerProduct.IssueTracker, line 5871, in Always2Notify
Module Products.IssueTrackerProduct.IssueTracker, line 6101, in ShowNameEmail
Module Products.IssueTrackerProduct.Utils, line 445, in html_entity_fixer
UnicodeDecodeError: 'ascii' codec can't decode byte 0xf3 in position 6: ordinal not in range(128)
1 month and 3 weeks and 6 days old
#0796 Export to CSV
The CSV export link in the "List Issues" section does not work correctly when using the "do not show" option. For example, when selecting "Hide completed issues", the CSV file contains completed issues only. So it seems the CSV export always applies filters in the "show only" mode
2 months and 1 day old
#0795 Error adding an issue
An error occured when I tried to...
--------------------------------------------------
Error type: NoACLAdderError
Error value: No ACL user object found
Traceback (innermost last):
Module ZPublisher.Publish, line 119, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish, line 42, in call_object
Module Products.IssueTrackerProduct.IssueTracker, line 3622, in SubmitIssue
Module Products.IssueTrackerProduct.IssueTracker, line 3776, in createIssueObject
NoACLAdderError: No ACL user object found
2 months and 1 day old
#0787 error
An error occured when I tried to...Update everything.
Same error when trying to add filter for 1 person, other it works.
--------------------------------------------------
Error type: UnicodeDecodeError
Error value: 'ascii' codec can't decode byte 0xef in position 10: ordinal not in range(128)
<p>Traceback (innermost last):
<ul>
<li> Module ZPublisher.Publish, line 101, in publish</li>
<li> Module ZPublisher.mapply, line 88, in mapply</li>
<li> Module ZPublisher.Publish, line 39, in call_object</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 1779, in UpdateEverything</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 5564, in UpdateFilterValuerCatalog</li>
<li> Module Products.IssueTrackerProduct.IssueTracker, line 13113, in index_object</li>
<li> Module Products.ZCatalog.ZCatalog, line 528, in catalog_object</li>
<li> Module Products.ZCatalog.Catalog, line 381, in catalogObject</li>
<li> Module Products.PluginIndexes.common.UnIndex, line 252, in index_object</li>
<li> Module Products.PluginIndexes.common.UnIndex, line 282, in _index_object</li>
<li> Module Products.PluginIndexes.common.UnIndex, line 229, in insertForwardIndexEntry</li>
</ul>UnicodeDecodeError: 'ascii' codec can't decode byte 0xef in position 10: ordinal not in range(128)
</p>
2 months and 3 weeks old
Based on similar issues reported in this tracker (you can use the search function with part of the error message, such as "'ascii' codec can't decode byte"), it seems that you may have to look into which version of Zope you're using and change accordingly. Mine is 2.10.5-final, I think 2.11 works too.
Jack
What version of Zope and what version of IssueTrackerProduct?
>You're currently using the latest version.
Your installed version: 0.10.2
Zope Version
(Zope 2.7.8-final, python 2.3.5, win32)
Python Version
2.3.5 (#0062, Feb 8 2005, 16:23:02) [MSC v.1200 32 bit (Intel)]
System Platform
win32