3.1 & 3.2 Extensions Database 3.1 / 3.2 ⇒ Support Ticket

[jan_2017]

Hello.

Sorry i'm not an expert.
Yes i see many changes.

Could you say in any simple words what the main changes? I'm a beginner

Thx

[ Post made via Android ]

[dmzx]

Hello.

Sorry i'm not an expert.
Yes i see many changes.

Could you say in any simple words what the main changes? I'm a beginner

Thx

[ Post made via Android ]

Sure

Added fix for posting twice when no subject was entert.
Changed language files
Added copyright footer

[jan_2017]

Hello.

Sorry i'm not an expert.
Yes i see many changes.

Could you say in any simple words what the main changes? I'm a beginner

Thx

[ Post made via Android ]

Sure

Added fix for posting twice when no subject was entert.
Changed language files
Added copyright footer

Oh yeah .... thx for this fix. That was one problem!

[ Post made via Android ]

[meis2m]

How can set an perfix for each ticket?

[Kirill]

-

[rammstein]

Good evening to the whole team

I have a small question it would be possible to incur a drop-down list in your extension if so how can one do?

Thank you a lot

[aLaCaZeM]

Can't find support ticket in the administration panel ....? I can't find it in the general forum settings or extensions. Where should it be? Please help me

[Potku]

Useful EXT!

It was already asked on the first page, but the reply wasn't simple enough for me.

We would like to use this EXT to help people find a martial arts hobby for them. For that, we would only need simple answers. Multiple choices and long text fields would be unnecessary.

Where should we look to modify this? :)

[amorino]

Hello
Many thanks for all your efforts
Does this extention work with PHPBB 3.3.10 ?
Many thanks

[Dead Man]

Hello
Many thanks for all your efforts
Does this extention work with PHPBB 3.3.10 ?
Many thanks

Works with 3.3.12
But like with the Form Creator extension not sure if its same issue on previous PHPBB versions,
Their is glitches with the Preview buttons for the text field.
I had to do some edits to get it to work a bit more properly for the Form Creator extension.

For this extension if you fill out the information and hit preview button than the information stays on the tables and in the text field the information is generated as well. So when one hits submit all the information is basically posted double if the user does not delete everything from the Default text field.

So for mine I disabled the preview and Draft buttons and added the RESET button.
This way people cannot hit preview and get the issue of double posting the information.

This is the file I Edit
\styles\ThemName\template\posting_editor.html

Find This may be a partial find and not the whole line

Code: Select all

<!-- IF S_HAS_DRAFTS --><input type="submit" accesskey="d" tabindex="8" name="load" value="{L_LOAD_DRAFT}" class="button2" onclick="load_draft = true;" />&nbsp; <!-- ENDIF -->
			<!-- IF S_SAVE_ALLOWED --><input type="submit" accesskey="k" tabindex="7" name="save" value="{L_SAVE_DRAFT}" class="button2" />&nbsp; <!-- ENDIF -->
			<input type="submit" tabindex="5" name="preview" value="{L_PREVIEW}" class="button1"<!-- IF not S_PRIVMSGS --> onclick="document.getElementById('postform').action += '#preview';"<!-- ENDIF --> />&nbsp;
			<input type="submit" accesskey="s" tabindex="6" name="post" value="{L_SUBMIT}" class="button1 default-submit-action" />&nbsp;

Replace with Replace the preceding lines with the following

Code: Select all

{% if not SUPPORT_STS %}
			{% if S_HAS_DRAFTS %}<input type="submit" accesskey="d" tabindex="8" name="load" value="{{ lang('LOAD_DRAFT') }}" class="button2" onclick="load_draft = true;" />&nbsp; {% endif %}
			{% if S_SAVE_ALLOWED %}<input type="submit" accesskey="k" tabindex="7" name="save" value="{{ lang('SAVE_DRAFT') }}" class="button2" />&nbsp; {% endif %}
			<input type="submit" tabindex="5" name="preview" value="{{ lang('PREVIEW') }}" class="button1"{% if not S_PRIVMSGS %} onclick="document.getElementById('postform').action += '#preview';"{% endif %} />&nbsp;
			{% endif %}
			<input type="reset" name="reset" value="{{ lang('RESET') }}" class="button2" />
			<input type="submit" accesskey="s" tabindex="6" name="post" value="{{ lang('SUBMIT') }}" class="button1 default-submit-action" />&nbsp;

If you dont want the reset button delete this line

Code: Select all

<input type="reset" name="reset" value="{{ lang('RESET') }}" class="button2" />

[rudesmen]

I confirm, it works on 3.3.12
Unfortunately, with a minor inconvenience, as Dead Man mentions above.
Before sending a post, I like to check what it looks like using the preview button.
I am grateful for this MOD.

[rudesmen]

1. I'm trying to adapt the MOD for my forum. So I need text fields. Editing the posting_editor_subject_after file is not enough because after sending the message, the result is different than expected. I guess the changes need to be made in the listener.php. Is that all?


2. And the second question is how to add one of the additional fields to the topic title?
Example I have a title field: ABC
Additional field from Support Ticket: DEF
I would like the thread title to be ABC DEF after sending the message.

[rudesmen]

To delete

[Dead Man]

1. I'm trying to adapt the MOD for my forum. So I need text fields. Editing the posting_editor_subject_after file is not enough because after sending the message, the result is different than expected. I guess the changes need to be made in the listener.php. Is that all?


2. And the second question is how to add one of the additional fields to the topic title?
Example I have a title field: ABC
Additional field from Support Ticket: DEF
I would like the thread title to be ABC DEF after sending the message.

What do you mean you need text fields? Like you need additional ones? There is already text fields with it. If you’re not using all of them just change the wording to your liking.

For the second one you can try maybe using one of the attributes extensions. The attribute extension
I have would look like this to give you an idea

[rudesmen]

Yes, extra. I need a few of them. And the rest have other attributes like "not required" or are checkboxes. After the changes in the posting_editor_subject_after, I can already get the expected effect of how the form should look, but after sending the message, answers from checkboxes appear. I came to the conclusion that changes still need to be made in listener.php. I need to add new text boxes and few od them delete. I haven't figured it out yet.