poor positioning in the ticket view in the modify part

[Harold Alcalde Solarte]

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.

[Roger Oberholtzer]

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

[Pavel Celba]

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

[Harold Alcalde Solarte]

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.

[Harold Alcalde Solarte]

I will try to find another plugin with the same benefits because DynamicFields and trac seems thatc they dont work well together.

[Roger Oberholtzer]

On Tue, Sep 4, 2018 at 1:04 PM Harold Alcalde Solarte
<haroldalca...@gmail.com> 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

[Harold Alcalde Solarte]

So how do you resolve this issue? 

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

[Roger Oberholtzer]

On Tue, Sep 4, 2018 at 1:11 PM Harold Alcalde Solarte
<haroldalca...@gmail.com> 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

[Pavel Celba]

TimingAndEstimation plugin cannot help in dynamic fields displaying but it can give some ideas how to rearrange the page after some field removal. If you remove some small field then it should not move any textarea into the right column etc. 

You may try the newer plugin version (2.2.0dev is over 2 years old) and/or place the issue here: https://trac-hacks.org/wiki/DynamicFieldsPlugin. Or try to fix it.

Pavel

Dne úterý 4. září 2018 13:02:16 UTC+2 Harold Alcalde Solarte napsal(a):

[RjOllos]

Please post your [ticket-custom] section from trac.ini.

- Ryan

[RjOllos]

Please provide a screen capture and your [ticket-custom] section from trac.ini.

- Ryan

[Harold Alcalde Solarte]

In the header are both

[Harold Alcalde Solarte]

[Jun Omae]

I'm TracWysiwygPlugin's author.

The textarea custom field is normally displayed as fullrow in ticket form, but
TracDynamicFieldsPlugin breaks the fullrow. TracWysiwygPlugin doesn't work well
in textarea with non fullrow.

That's is a TracDynamicFieldsPlugin issue.
Also, I don't have no will to fix TracWysiwygPlugin about the issue.

Please disable TracWysiwygPlugin in your trac.ini.

--
Jun Omae <jun...@gmail.com> (大前 潤)

[Harold Alcalde Solarte]

I still have the same issue. I've disabled TracWysiwygPlugin and the result is the same... I attach the layout of my trac.

[Jun Omae]

On Wed, Oct 3, 2018 at 4:37 PM Harold Alcalde Solarte
<haroldalca...@gmail.com> wrote:
>
> I still have the same issue. I've disabled TracWysiwygPlugin and the result is the same... I attach the layout of my trac.

Investigating layout.js, TracDynamicFieldsPlugin with textarea custom
fields is absolutely broken when the fields have rules to hide.
I think the textarea fields, the rules or the plugin should be removed.

[Jun Omae]

Created patch for layout.js. Could you please try the patch?

[Harold Alcalde Solarte]

On the one hand the modification part is now seen correctly, but on the other hand when the ticket is created, no field that I have added in the custom-ticket is seen.

I have tested with the latest version of the DynamicField and adding your patch and I have also tested with DynamicFieldPlugin Release version 2.1.0. My ticket-custom is the same one that I put at the beginning.

I attach a pic of the ticket view after create it.

[Jun Omae]

On Thu, Oct 4, 2018 at 5:34 PM Harold Alcalde Solarte
<haroldalca...@gmail.com> wrote:
>
> On the one hand the modification part is now seen correctly, but on the other hand when the ticket is created, no field that I have added in the custom-ticket is seen.
>
> I have tested with the latest version of the DynamicField and adding your patch and I have also tested with DynamicFieldPlugin Release version 2.1.0. My ticket-custom is the same one that I put at the beginning.
> I attach a pic of the ticket view after create it.

It seems that the wrong layout of ticket view is introduced in
https://trac-hacks.org/changeset/15095.
Revised the patch: dynamicfieldsplugin-v2.diff
Please try and feedback.

[Harold Alcalde Solarte]

Sorry for the delay.

At the time of making the patch it gives me an error.

[Jun Omae]

On Mon, Oct 8, 2018 at 4:14 PM Harold Alcalde Solarte
<haroldalca...@gmail.com> wrote:
>
> Sorry for the delay.
>
> At the time of making the patch it gives me an error.

I don't catch any errors. Please apply the patch to clean and latest trunk.

$ svn co https://trac-hacks.org/svn/dynamicfieldsplugin/trunk
/tmp/dynamicfieldsplugin
A /tmp/dynamicfieldsplugin/dynfields
A /tmp/dynamicfieldsplugin/dynfields/htdocs
A /tmp/dynamicfieldsplugin/dynfields/templates
A /tmp/dynamicfieldsplugin/dynfields/tests
A /tmp/dynamicfieldsplugin/dynfields/locale
A /tmp/dynamicfieldsplugin/dynfields/locale/de
A /tmp/dynamicfieldsplugin/dynfields/locale/de/LC_MESSAGES
A /tmp/dynamicfieldsplugin/dynfields/locale/ja
A /tmp/dynamicfieldsplugin/dynfields/locale/ja/LC_MESSAGES
A /tmp/dynamicfieldsplugin/dynfields/compat.py
A /tmp/dynamicfieldsplugin/dynfields/__init__.py
A /tmp/dynamicfieldsplugin/dynfields/htdocs/dynfields.js
A /tmp/dynamicfieldsplugin/dynfields/htdocs/rules.js
A /tmp/dynamicfieldsplugin/dynfields/htdocs/layout.js
A /tmp/dynamicfieldsplugin/dynfields/htdocs/layout.css
A /tmp/dynamicfieldsplugin/dynfields/options.py
A /tmp/dynamicfieldsplugin/dynfields/rules.py
A /tmp/dynamicfieldsplugin/dynfields/templates/prefs_panel.html
A /tmp/dynamicfieldsplugin/dynfields/tests/options.py
A /tmp/dynamicfieldsplugin/dynfields/tests/__init__.py
A /tmp/dynamicfieldsplugin/dynfields/web_ui.py
A /tmp/dynamicfieldsplugin/dynfields/locale/de/LC_MESSAGES/dynfields.po
A /tmp/dynamicfieldsplugin/dynfields/locale/messages.pot
A /tmp/dynamicfieldsplugin/dynfields/locale/ja/LC_MESSAGES/dynfields.po
A /tmp/dynamicfieldsplugin/dynfields/locale/.placeholder
A /tmp/dynamicfieldsplugin/setup.cfg
A /tmp/dynamicfieldsplugin/setup.py
A /tmp/dynamicfieldsplugin/COPYING
U /tmp/dynamicfieldsplugin
Checked out revision 17290.
$ cd /tmp/dynamicfieldsplugin
$ sha1sum -b /tmp/dynamicfieldsplugin-v2.diff
11b3b6d0d411b4a81026698808e49cca7d19ec2e */tmp/dynamicfieldsplugin-v2.diff
$ patch -p1 < /tmp/dynamicfieldsplugin-v2.diff
patching file dynfields/htdocs/layout.js
patching file dynfields/htdocs/rules.js
$ echo $?
0

[Harold Alcalde Solarte]

it's works right. Thank you.