Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

custom form fields #84

Open
deltaforce opened this issue Aug 25, 2019 · 6 comments
Open

custom form fields #84

deltaforce opened this issue Aug 25, 2019 · 6 comments
Assignees
Labels
limitation current process has a little lacks of this plugin conflict conflicting with another plugin is detected

Comments

@deltaforce
Copy link

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
Copy link
Owner

mayeenulislam commented Aug 25, 2019

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

@mayeenulislam mayeenulislam added the plugin conflict conflicting with another plugin is detected label Aug 25, 2019
@deltaforce
Copy link
Author

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
Copy link
Owner

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
Copy link
Author

deltaforce commented Aug 26, 2019 via email

@mayeenulislam
Copy link
Owner

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.

@mayeenulislam mayeenulislam reopened this Aug 26, 2019
@mayeenulislam mayeenulislam added the limitation current process has a little lacks of this label Aug 26, 2019
@mayeenulislam mayeenulislam self-assigned this Aug 26, 2019
@deltaforce
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
limitation current process has a little lacks of this plugin conflict conflicting with another plugin is detected
Projects
None yet
Development

No branches or pull requests

2 participants