custom form fields

[deltaforce]

I am using s2member plugin on my site, and want to use nano support as well.
But it is making a mess of the custom fields from s2member. Is there any way to fix this?

https://foodbooking.uk/submit-ticket/

[mayeenulislam]

I am using s2member plugin on my site, and want to use nano support as well.
But it is making a mess of the custom fields from s2member. Is there any way to fix this?

Actually we don't have any solution putting custom <div> around the s2member custom fields. You have to reach them for putting custom wrapper around the custom fields, so that you can design 'em however necessary.

Local Remedy

What we can suggest most, is: you can put the following code in your theme's functions.php. This code will remove the custom fields added by the s2Member plugin from the NanoSupport Submit Ticket page.

/**
 * Remove s2Member Custom Fields from NanoSupport
 * @link https://wordpress.stackexchange.com/a/240930/22728
 */
function my_custom_remove_s2member_custom_fields()
{
        $ns_general_settings = get_option( 'nanosupport_settings' );
	if (is_page($ns_general_settings['submit_page'])) {
		remove_action('register_form', array('c_ws_plugin__s2member_custom_reg_fields', 'custom_registration_fields'), 10);
	}
}

add_action('register_form', 'my_custom_remove_s2member_custom_fields', 9);

[deltaforce]

ok I have some alternative, if you can tell me how to achieve these.

1. HIDE tickets unless user is logged, then I can force registration via S2member first.
2. DISABLE tickets and only use knowledgebase, then I will use external ticket system.

[mayeenulislam]

HIDE tickets unless user is logged, then I can force registration via S2member first.

You can disable embedded login/registration from NanoSupport Settings. Then you can use any registration system you want. Default feature: only logged in users can see tickets as NanoSupport tickets are by core private.

DISABLE tickets and only use knowledgebase, then I will use external ticket system.

Uhun, Ticketing is the base feature of NanoSupport. You can enable/disable Knowledgebase, but can't disable ticketing system.

[deltaforce]

On Mon, 26 Aug 2019 at 03:44, Mayeenul Islam ***@***.***> wrote: HIDE tickets unless user is logged, then I can force registration via S2member first. You can disable embedded login/registration from NanoSupport Settings. Then you can use any registration system you want. Default feature: only logged in users can see tickets as NanoSupport tickets are by core private .

the problem with this is that user can still submit ticket, but it simply fails because they are not logged in, which is confusing.

…

DISABLE tickets and only use knowledgebase, then I will use external ticket system. *Uhun*, Ticketing is the base feature of NanoSupport. You can enable/disable Knowledgebase, but can't disable ticketing system. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#84>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAJ3VUDSXOR4OUJGF2IOCRTQGM7QPANCNFSM4IPHX5ZA> .

-- Russ Michaels IT Jedi Master phone: 01843 808480 <441843808480> website: michaels.me.uk email: russ@michaels.me.uk <https://www.facebook.com/russmichaelsconsulting/> <https://twitter.com/russmichaels> <https://www.linkedin.com/in/russmichaels/> [image: skype:russmichaels?chat] IMPORTANT: The contents of this email and any attachments are confidential. It is strictly forbidden to share any part of this message with any sith lord or member of the galactic empire, without a written consent of a member of the Jedi Order. If you received this message by mistake, please use the force to let me know or contact your local Jedi Council representative.

[mayeenulislam]

Understood your point. I think I understood what to do to resolve this.
I'll take a look into the whole submit ticket thing again, to resolve the issues associated with it, hopefully on the next release or after next release, inshALLAH.

[deltaforce]

Ideally, it should be 2 options.

1. create ticket and register at the same time, as you have it now.
2. only allow ticket submission if logged in. if they try to submit a ticket, it should tell them to login or register first, and provide links to do so.