Ticket #13786 (new Bug)
plone.org/products: issues can't be created
Reported by: | frisi | Owned by: | plone-website@… |
---|---|---|---|
Priority: | critical | Milestone: | 4.x |
Component: | Website | Version: | 4.4 |
Keywords: | plone.org | Cc: |
Description
when creating a new issue in one of the plonesoftwarecenter issues trackers of the products on plone.org/products i get a site error
tried here http://plone.org/products/linguaplone/issues and on a package i own: http://plone.org/products/collective.viewlet.links/issues
Change History
comment:1 Changed 2 years ago by frisi
- Owner set to plone-website@…
- Priority changed from minor to critical
- Component changed from Unknown to Website
comment:3 Changed 2 years ago by frisi
is this move happening as we type and therefore i get an error message?
if not, we should at least show a statusmessage on all issue tracker views so that users and also product owners get this information.
comment:4 Changed 2 years ago by aclark
+1 to showing a status message, maybe Maurits knows how we can do this easily
comment:5 Changed 2 years ago by frisi
who is responsible for activating issues on https://github.com/plone/Products.LinguaPlone and migrating existing issues from http://plone.org/products/linguaplone/issues/?
comment:7 Changed 2 years ago by frisi
@aclark according to pypi this is hannosch, mj, tesdal, gotcha, esteele, davisagli, toutpt
having a look at the issue tracker (last ticket from may 2013, no reply) it seems nobody really feels responsible.
comment:8 Changed 2 years ago by maurits
I have just created two issues without problem:
http://plone.org/products/poi/issues/267
http://plone.org/products/linguaplone/issues/290
I have Manager rights on the tracker of Poi itself, but not on the LinguaPlone issue tracker, so adding that last issue should have triggered an error.
Does anyone have a traceback?
comment:9 Changed 2 years ago by frisi
i still get an error when adding an issue to the linguaplone tracker:
error number 1383151383.110.86045295172. (sorry, no permission to see the traceback)
comment:10 Changed 2 years ago by maurits
Can anyone with permission to see that traceback paste it here?
Or grant me Manager or Site Admin rights on the Plone site root.
Maybe also check if any upgrade steps still need to be run for Poi, in case that got missed during the last upgrade.
comment:11 Changed 2 years ago by aclark
It seems the traceback expired, but I ran the upgrade steps so maybe that helped. Frisi: please try again and paste another traceback ID if you get one. Maurits: I added you to the Site Administrators group, but I'm not sure if that will actually do anything. Let me know if that works or does nothing.
comment:12 Changed 2 years ago by maurits
Alex: thanks. I do not notice any new powers. I see no edit bars on extra pages and cannot access @@overview-controlpanel.
comment:13 Changed 2 years ago by frisi
i still get an error. this time: 1383219821.830.927699767186
comment:14 Changed 2 years ago by aclark
And I still can't find your error in the error log, even immediately after it occured.
Maurits, I gave you "Owner" on the Plone site until we can figure out a better way. https://www.dropbox.com/s/v5w84pb1g7asgli/Screenshot%202013-11-03%2007.44.52.png
comment:15 Changed 2 years ago by maurits
Not finding the error may be because the error occurs on one zeoclient and you are connected to a different zeoclient. When sticky sessions are on, you will always end up on the same zeoclient...
Owner sounds great, I can access the ZMI, but I can do nothing interesting. Apparently Owner is overrated...
comment:16 Changed 2 years ago by aclark
OK try again, this time I made you a "Manager" which is the same role my "aclark" user has: https://www.dropbox.com/s/9pgjhcrb8p5ekkp/Screenshot%202013-11-05%2004.26.32.png
comment:17 Changed 2 years ago by frisi
@maurits: can you access this traceback now: 1383644006.090.736550249076. ? otherwhise we should ask somebody with filesystem access who can have a look at the instance.log
comment:18 Changed 2 years ago by aclark
2013-11-05T09:33:26 ERROR Zope.SiteErrorLog 1383644006.090.736550249076 http://plone.org/products/linguaplone/issues/portal_factory/PoiIssue/poiissue.2013-11- 05.0053942444/base_edit Traceback (innermost last): Module ZPublisher.Publish, line 138, in publish Module ZPublisher.mapply, line 77, in mapply Module ZPublisher.Publish, line 48, in call_object Module Products.CMFPlone.FactoryTool, line 473, in __call__ Module ZPublisher.mapply, line 77, in mapply Module ZPublisher.Publish, line 48, in call_object Module Products.CMFFormController.FSControllerPageTemplate, line 91, in __call__ Module Products.CMFFormController.BaseControllerPageTemplate, line 31, in _call Module Shared.DC.Scripts.Bindings, line 322, in __call__ Module Shared.DC.Scripts.Bindings, line 359, in _bindAndExec Module Products.CMFCore.FSPageTemplate, line 237, in _exec Module Products.CMFCore.FSPageTemplate, line 177, in pt_render Module Products.PageTemplates.PageTemplate, line 79, in pt_render Module zope.pagetemplate.pagetemplate, line 132, in pt_render - Warning: Macro expansion failed - Warning: <type 'exceptions.KeyError'>: 'macro' Module zope.pagetemplate.pagetemplate, line 240, in __call__ Module zope.tal.talinterpreter, line 271, in __call__ Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 858, in do_defineMacro Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 533, in do_optTag_tal Module zope.tal.talinterpreter, line 518, in do_optTag Module zope.tal.talinterpreter, line 513, in no_tag Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 888, in do_useMacro Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 533, in do_optTag_tal Module zope.tal.talinterpreter, line 518, in do_optTag Module zope.tal.talinterpreter, line 513, in no_tag Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 954, in do_defineSlot Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 533, in do_optTag_tal Module zope.tal.talinterpreter, line 518, in do_optTag Module zope.tal.talinterpreter, line 513, in no_tag Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 858, in do_defineMacro Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 954, in do_defineSlot Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 533, in do_optTag_tal Module zope.tal.talinterpreter, line 518, in do_optTag Module zope.tal.talinterpreter, line 513, in no_tag Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 946, in do_defineSlot Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 533, in do_optTag_tal Module zope.tal.talinterpreter, line 518, in do_optTag Module zope.tal.talinterpreter, line 513, in no_tag Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 858, in do_defineMacro Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 533, in do_optTag_tal Module zope.tal.talinterpreter, line 518, in do_optTag Module zope.tal.talinterpreter, line 513, in no_tag Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 888, in do_useMacro Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 852, in do_condition Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 954, in do_defineSlot Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 533, in do_optTag_tal Module zope.tal.talinterpreter, line 518, in do_optTag Module zope.tal.talinterpreter, line 513, in no_tag Module zope.tal.talinterpreter, line 343, in interpret
…
Module zope.tal.talinterpreter, line 518, in do_optTag Module zope.tal.talinterpreter, line 513, in no_tag Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 888, in do_useMacro Module zope.tal.talinterpreter, line 343, in interpret Module zope.tal.talinterpreter, line 533, in do_optTag_tal Module zope.tal.talinterpreter, line 518, in do_optTag Module zope.tal.talinterpreter, line 513, in no_tag Module zope.tal.talinterpreter, line 343, in interpret METALError: macro nesting limit (100) exceeded by u'support/macros/wysiwygEditorBox'
comment:19 Changed 2 years ago by maurits
I've got the power! Thanks, Alex. :-)
Frisi, I see what the problem is: you have selected Kupu as editor. Then it fails. If you switch to TinyMCE or 'Use site default' it should work. So that is the workaround.
I would expect that you encounter other errors too, like simply not being able to edit pages. This seems to work though.
The strange thing is that none of the Poi issue fields use html by default: the only options are plain text or intelligent text, unless you change this via a monkey patch. The Poi code does directly call support/macros/wysiwygEditorBox but that is only when showing or editing responses. with a text/html mimetype, and that is not the case here. I will check if I can reproduce this locally and if anything can be done in the Poi code or maybe in some other code used on plone.org.
comment:20 Changed 2 years ago by frisi
thanks for the hint maurits - now i can add tickets again ;-)
i'm sure also other users still have kupu enabled and so suffer from the same problem.
we should add an upgrade step for the next plone.org update that resets the visual editor to tiny for all users and disable kupu completely since it's not working at all.
comment:21 Changed 2 years ago by maurits
For updating the visual editor of all users, I would recommend collective.setdefaulteditor. Add it to the eggs, rerun buildout, and use the form at @@set-default-editor.
comment:22 Changed 2 years ago by aclark
OK, I'll do that
comment:23 Changed 2 years ago by maurits
For the record, I tried to reproduce this locally but failed. What might happen is that wysiwyg_support.pt is loaded, which tries to load here/kupu/wysiwyg_support, which falls back to the same wysiwyg_support.pt, because the kupu directory is there in portal_skins but is empty. I briefly tried removing that, but this had no effect so I reverted it. But it is probably something like that.
as this seems to affect all products on plone.org i set the priority to critical