[Trac] Re: Genshi UnicodeEncodeError error while rendering template (unknown template location)
On Monday, August 20, 2018 at 2:39:41 PM UTC-7, RjOllos wrote: > > > > On Monday, August 20, 2018 at 2:34:58 PM UTC-7, mamamia888 wrote: >> >> Sorry, it's still the same select >> newvalue from ticket_change where ticket=101 and field='comment' and >> newvalue like '%> >> Not sure some ticket/wiki works with "> 11683. >> > > You might be able to get around this issue by using Genshi 0.6. I'd try > that. I've been using Genshi 0.6 on several sites and there are no issues. > > Or just upgrade to Trac 1.0.2 or later, rather than patching your > installation. > > - Ryan > You could also try the newly-released Genshi 0.7.1. - Ryan -- 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 trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Email notification for custom field
On 04.09.2018 10:03, Yves Pausch wrote: Tiny change: I had to add a 'field_set = set()' Still an issue: The person mentioned in 'tester' is now notified as expected when the ticket changes. But for the case we change the tester value initially or later on, also the new value has to be informed. I imagine adding the current value of 'tester' would do the job, but how to access that value? Thanks for your help. Yes, that's working. I changed the section in matches() the following way: # Harvest previous field values field_set = set() if 'fields' in event.changes and self.field_name in event.changes['fields']: field_set.update(to_set(event.changes['fields'][self.field_name]['old'])) # collect the new tester(s) field_set.update(to_set(event.changes['fields'][self.field_name]['new'])) # potentially also collect the new tester(s) I think the user_set was also supposed to be field_set. I adjusted https://trac.edgewall.org/wiki/CookBook/Notification/Subscriptions#Subscribeviacustomticketfield -- 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 trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] poor positioning in the ticket view in the modify part
On Tue, Sep 4, 2018 at 1:11 PM Harold Alcalde Solarte wrote: > > So how do you resolve this issue? We have not. The stray fields are just that way. I would like to solve it... -- Roger Oberholtzer -- 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 trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: Error: The current storage engine is MyISAM.
On Tue, Sep 4, 2018 at 12:29 PM RjOllos wrote: > > > > On Tuesday, September 4, 2018 at 3:24:36 AM UTC, RjOllos wrote: >> >> I don't see a way to set a persistent default storage engine for each >> database/schema. However, rather than requiring the MySQL instance default >> storage engine to be set (in the system-wide my.cnf configuration), we could >> possibly have a trac.ini configuration option to specify the storage engine >> and explicitly set the default for the session before creating the tables, >> or use the ENGINE option when creating tables: >> https://dev.mysql.com/doc/refman/8.0/en/storage-engine-setting.html > > > The proposed option would be [trac] mysql_storage_engine, or [mysql] > storage_engine. Trac requires that both default_storage_engine and default_tmp_storage_engine are InnoDB. MySQLConnector.to_sql() respecting the option for storage engine sounds good but we're directly using "CREATE TEMPORARY TABLE ..." in trac/upgrades/*.py without the to_sql() method. The "CREATE TEMPORARY TABLE ..." uses storage engine configured in the default_tmp_storage_engine. -- Jun Omae (大前 潤) -- 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 trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] poor positioning in the ticket view in the modify part
So how do you resolve this issue? El mar., 4 sept. 2018 13:07, Roger Oberholtzer escribió: > On Tue, Sep 4, 2018 at 1:04 PM Harold Alcalde Solarte > wrote: > > > > I will try to find another plugin with the same benefits because > DynamicFields and trac seems thatc they dont work well together. > > For us it is just the custom fields that cause the layout issues. > > -- > Roger Oberholtzer > > -- > 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 trac-users+unsubscr...@googlegroups.com. > To post to this group, send email to trac-users@googlegroups.com. > Visit this group at https://groups.google.com/group/trac-users. > For more options, visit https://groups.google.com/d/optout. > -- 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 trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] poor positioning in the ticket view in the modify part
On Tue, Sep 4, 2018 at 1:04 PM Harold Alcalde Solarte wrote: > > I will try to find another plugin with the same benefits because > DynamicFields and trac seems thatc they dont work well together. For us it is just the custom fields that cause the layout issues. -- Roger Oberholtzer -- 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 trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] poor positioning in the ticket view in the modify part
I will try to find another plugin with the same benefits because DynamicFields and trac seems thatc they dont work well together. El martes, 4 de septiembre de 2018, 10:35:11 (UTC+2), Roger Oberholtzer escribió: > > On Tue, Sep 4, 2018 at 10:00 AM Harold Alcalde Solarte > > wrote: > > > > I currently use trac 1.2.2 and the following plugins: > > TicketImport 0.9.0, TracDynamicFields 2.2.0dev, TracSubTicketsPlugin > 0.5.4dev , TracWorkflowAdmin 0.12.0.4,TracWysiwyg 0.12.0.7,TracXMLRPC > 1.1.7dev. > > > > > > My problem occurs when I go to see a ticket and in the part of modifying > the ticket, the fields are disordered. I have tried to put the fields in > different order, change the size of the columns and the rows, but I can not > get it to fit. I do not know exactly how it works .cols and .rows in the > ticket-custom. > > I attach my ticket-custom and a pic of the wrong layout. > > I have had the same thing for many releases. I have also tried what > you tried, to no effect. We have just decided it is a Trac > idiosyncrasy, and smile. It does seem that custom fields lead to this > confusion in the layout. I don't know if it is Trac itself, or a > toolkit it uses to generate the HTML. > > > -- > Roger Oberholtzer > -- 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 trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
[Trac] Re: poor positioning in the ticket view in the modify part
It seems that the problem is the DynamicFields plugin, but I also need it for the visualization of the fields according to the type of ticket. I will try to find another plugin that offers the benefits of DynamicFields. I will try to use TiminAndEstimationPlugin. Thank you. Haroldo. El martes, 4 de septiembre de 2018, 11:17:19 (UTC+2), Pavel Celba escribió: > > Did you try to disable the TracDynamicFields plugin? Is the output OK > when you display all fields? We are using many custom fields and all > textareas are always displayed on separate row, other fields are displayed > in pairs on one row. We are using TiminAndEstimationPlugin which rearranges > some fields in edit mode w/o problems. > > Pavel > > > Dne úterý 4. září 2018 10:00:46 UTC+2 Harold Alcalde Solarte napsal(a): >> >> I currently use trac 1.2.2 and the following plugins: >> TicketImport 0.9.0, TracDynamicFields 2.2.0dev, TracSubTicketsPlugin >> 0.5.4dev , TracWorkflowAdmin 0.12.0.4,TracWysiwyg 0.12.0.7,TracXMLRPC >> 1.1.7dev. >> >> >> My problem occurs when I go to see a ticket and in the part of modifying >> the ticket, the fields are disordered. I have tried to put the fields in >> different order, change the size of the columns and the rows, but I can not >> get it to fit. I do not know exactly how it works .cols and .rows in the >> ticket-custom. >> I attach my ticket-custom and a pic of the wrong layout. >> >> Thank you. >> >> >> >> -- 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 trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
[Trac] Re: poor positioning in the ticket view in the modify part
Did you try to disable the TracDynamicFields plugin? Is the output OK when you display all fields? We are using many custom fields and all textareas are always displayed on separate row, other fields are displayed in pairs on one row. We are using TiminAndEstimationPlugin which rearranges some fields in edit mode w/o problems. Pavel Dne úterý 4. září 2018 10:00:46 UTC+2 Harold Alcalde Solarte napsal(a): > > I currently use trac 1.2.2 and the following plugins: > TicketImport 0.9.0, TracDynamicFields 2.2.0dev, TracSubTicketsPlugin > 0.5.4dev , TracWorkflowAdmin 0.12.0.4,TracWysiwyg 0.12.0.7,TracXMLRPC > 1.1.7dev. > > > My problem occurs when I go to see a ticket and in the part of modifying > the ticket, the fields are disordered. I have tried to put the fields in > different order, change the size of the columns and the rows, but I can not > get it to fit. I do not know exactly how it works .cols and .rows in the > ticket-custom. > I attach my ticket-custom and a pic of the wrong layout. > > Thank you. > > > > -- 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 trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] poor positioning in the ticket view in the modify part
On Tue, Sep 4, 2018 at 10:00 AM Harold Alcalde Solarte wrote: > > I currently use trac 1.2.2 and the following plugins: > TicketImport 0.9.0, TracDynamicFields 2.2.0dev, TracSubTicketsPlugin 0.5.4dev > , TracWorkflowAdmin 0.12.0.4,TracWysiwyg 0.12.0.7,TracXMLRPC 1.1.7dev. > > > My problem occurs when I go to see a ticket and in the part of modifying the > ticket, the fields are disordered. I have tried to put the fields in > different order, change the size of the columns and the rows, but I can not > get it to fit. I do not know exactly how it works .cols and .rows in the > ticket-custom. > I attach my ticket-custom and a pic of the wrong layout. I have had the same thing for many releases. I have also tried what you tried, to no effect. We have just decided it is a Trac idiosyncrasy, and smile. It does seem that custom fields lead to this confusion in the layout. I don't know if it is Trac itself, or a toolkit it uses to generate the HTML. -- Roger Oberholtzer -- 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 trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
[Trac] agilo_link table has data for which tables
Hello Guys, I am working on merging two Trac databases. I resolved most the conflict data but I still have an issue with agilo_link table. I added offset to most tables and tickets my questions is this table define any relationship between others tables? if so, can you please let me know which tables. Thanks, -- 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 trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Email notification for custom field
On Tuesday, September 4, 2018 at 9:39:53 AM UTC+2, Yves Pausch wrote: > > On Monday, September 3, 2018 at 11:00:22 PM UTC+2, Peter Suter wrote: >> >> On 03.09.2018 14:49, Yves Pausch wrote: >> > Hi, I added a custom field 'tester' and want this tester to be >> > notified in the way a CC is notified, when the ticket changes. Is >> > there a way to achieve this using trac 1.2 (+ plugin)? >> > Thanks, Yves. >> >> Hi, >> Yes, try this: >> https://groups.google.com/d/msg/trac-users/xsE0h5VjfLA/F18nUAmKEAAJ >> I now also added this to: >> >> https://trac.edgewall.org/wiki/CookBook/Notification/Subscriptions#Subscribeviacustomticketfield >> >> >> Hope this helps. >> > > Peter, yes, that helped a lot. Thank you very much. > > Tiny change: I had to add a 'field_set = set()' > > Still an issue: The person mentioned in 'tester' is now notified as > expected when the ticket changes. But for the case we change the tester > value initially or later on, also the new value has to be informed. I > imagine adding the current value of 'tester' would do the job, but how to > access that value? > > Thanks for your help. > Yes, that's working. I changed the section in matches() the following way: # Harvest previous field values field_set = set() if 'fields' in event.changes and self.field_name in event.changes['fields']: field_set.update(to_set(event.changes['fields'][self.field_name]['old'])) # collect the new tester(s) field_set.update(to_set(event.changes['fields'][self.field_name]['new'])) # potentially also collect the new tester(s) For other readers: To enable default subscription I had to add the following to trac.ini: [notification-subscriber] always_notify_tester = TesterCustomFieldSubscriber Thanks again, Peter -- 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 trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
[Trac] poor positioning in the ticket view in the modify part
I currently use trac 1.2.2 and the following plugins: TicketImport 0.9.0, TracDynamicFields 2.2.0dev, TracSubTicketsPlugin 0.5.4dev , TracWorkflowAdmin 0.12.0.4,TracWysiwyg 0.12.0.7,TracXMLRPC 1.1.7dev. My problem occurs when I go to see a ticket and in the part of modifying the ticket, the fields are disordered. I have tried to put the fields in different order, change the size of the columns and the rows, but I can not get it to fit. I do not know exactly how it works .cols and .rows in the ticket-custom. I attach my ticket-custom and a pic of the wrong layout. Thank you. -- 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 trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout. [ticket-custom] affected_items = textarea affected_items.cols = 72 affected_items.format = plain affected_items.label = Affected Items affected_items.order = 1 affected_items.rows= 20 affected_items.show_when_type = pr|incidence affected_items.value = changeset_tag = text changeset_tag.cols = 72 changeset_tag.format = plain changeset_tag.label = Changeset_TAG changeset_tag.order = 2 changeset_tag.rows = 5 changeset_tag.show_when_type = verification|gate changeset_tag.value = clasificacion_seguridad = text clasificacion_seguridad.cols = 72 clasificacion_seguridad.format = plain clasificacion_seguridad.label = SECURITY CLASSIFICATION clasificacion_seguridad.order = 3 clasificacion_seguridad.value = TECNOBIT CONFIDENCIAL clasification_seguridad.show_when_type = task|verification|cluster|pr|incidence|gate custom_description = textarea custom_description.cols = 36 custom_description.format = wiki custom_description.label = Custom Description custom_description.order = 4 custom_description.rows = 20 custom_description.show_when_type = pr|task|verification|incidence|cluster|gate custom_description.value = Description of the task, change, problem, action, MoM, etc. For templates see WIKI dated = text dated.format = plain dated.label = Dated dated.order = 5 dated.show_when_type = gate|verification dated.value = detection_info = textarea detection_info.cols = 144 detection_info.format = wiki detection_info.label = Detection Info detection_info.order = 6 detection_info.rows = 10 detection_info.show_when_type = pr|incidence detection_info.value = Tester, date, Test Case, etc. due_date = text due_date.format = plain due_date.label = Due_Date due_date.options = due_date.order = 7 due_date.show_when_type = task due_date.value = esfuerzo = text esfuerzo.cols = 72 esfuerzo.format = plain esfuerzo.hide_always = true esfuerzo.label = Esfuerzo esfuerzo.options = esfuerzo.order = 8 esfuerzo.value = esfuerzo_restante = text esfuerzo_restante.format = plain esfuerzo_restante.hide_always = true esfuerzo_restante.label = Porcentaje_Avance esfuerzo_restante.options = esfuerzo_restante.order = 9 esfuerzo_restante.value = estimatedhours = text estimatedhours.format = plain estimatedhours.label = Estimated Number of Hours estimatedhours.order = 10 estimatedhours.show_when_type = task estimatedhours.value = 0 fault_type = select fault_type.label = Fault Type fault_type.options = product|documentation|process|tools|COTS fault_type.order = 11 fault_type.show_when_type = pr fault_type.value = functionality = select functionality.label = Functionality functionality.options = N/A|Func1|Func2|Func3 functionality.order = 12 functionality.show_when_type = pr functionality.value = generar_tickets = textarea generar_tickets.cols = 36 generar_tickets.format = wiki generar_tickets.label = Generar tickets generar_tickets.order = 13 generar_tickets.rows = 20 generar_tickets.show_when_type = cluster generar_tickets.value = hours = text hours.format = plain hours.label = Add Hours to Ticket hours.order = 14 hours.show_when_type = task hours.value = id_html = text id_html.format = plain id_html.label = ID_html id_html.options = id_html.order = 15 id_html.hide_always = true id_html.value = initial_date = text initial_date.format = plain initial_date.label = Start_Date initial_date.options = initial_date.order = 16 initial_date.value = internal = checkbox internal.label = Internal internal.options = internal.order = 17 internal.show_when_type = pr|incidence internal.value = 0 mitigation = textarea mitigation.cols = 144 mitigation.format = plain mitigation.label = Mitigation mitigation.options = mitigation.order = 18 mitigation.rows = 36 mitigation.show_when_type = pr mitigation.value = nonsatisfied_reqs = textarea nonsatisfied_reqs.cols = 72 nonsatisfied_reqs.format = wiki nonsatisfied_reqs.label = Non-satisfied Reqs nonsatisfied_reqs.options = nonsatisfied_reqs.order = 19 nonsatisfied_reqs.rows = 10 nonsatisfied_reqs.show_when_type = pr
Re: [Trac] Email notification for custom field
On Monday, September 3, 2018 at 11:00:22 PM UTC+2, Peter Suter wrote: > > On 03.09.2018 14:49, Yves Pausch wrote: > > Hi, I added a custom field 'tester' and want this tester to be > > notified in the way a CC is notified, when the ticket changes. Is > > there a way to achieve this using trac 1.2 (+ plugin)? > > Thanks, Yves. > > Hi, > Yes, try this: > https://groups.google.com/d/msg/trac-users/xsE0h5VjfLA/F18nUAmKEAAJ > I now also added this to: > > https://trac.edgewall.org/wiki/CookBook/Notification/Subscriptions#Subscribeviacustomticketfield > > > Hope this helps. > Peter, yes, that helped a lot. Thank you very much. Tiny change: I had to add a 'field_set = set()' Still an issue: The person mentioned in 'tester' is now notified as expected when the ticket changes. But for the case we change the tester value initially or later on, also the new value has to be informed. I imagine adding the current value of 'tester' would do the job, but how to access that value? Thanks for your help. Regards, Yves. -- 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 trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
