Selecting the right header template with XL NextMove WooCommerce Thank You Page plug-in

Support
#1

Not sure if this question is best addressed to Theme.co or to XL but here goes.

I am using XL’s “NextMove WooCommerce Thank You Page” plug-in with my web site. On the thank you page creator it has the option to select a template. In that dropdown menu to select the template, it shows the typical template structures such as “blank - no container, header, footer”.

What I would like to do is select a template that includes the new header I have designed. However, regardless of which template configuration I select, I inevitably get the old header structure.

Can you help explain to me how I can create templates that use my own custom headers? If you need screenshots or access to my site to further investigate the issue, please let me know.

#2

Hi @christianatforpac,

I checked your licenses page and found out that you use the Pro theme. So you used the header builder to add a header. Now you want to assign the header built by the header builder to a page which is generated by a 3rd party plugin.

So please consider that you are on a wrong path thinking about the templates. You need to find a way to assign the header to the specific page.

Please check the documentation below to know how to assign a Header to a specific page via code:

Now in the code suggested in the documentation above we used some conditional tags to find out if the current page is the page in question which you need. You need to contact the 3rd party plugin developer and give them the documentation above and ask them to fill in the proper conditional tag which works for their generated page.

Thank you.

#3

Thanks for your esponse.

I’m struggling with this. The link you provided shows me a snippet that basically says “if this page comes up then use this header”. The code is:

add_filter('cs_match_header_assignment', 'custom_search_header');
function custom_search_header($match) {
	if (is_404()) {
		$match = 1234; // the post ID for your header
	}
	return $match;
}

I presume 1234 should be changed to “90” in the case of my header. But I am also unclear about how to identify the page in question as it appears generated by the Thank You plug-in. Can you help clarify how I would do this?

#4

Hello There,

You may use something like this code:

add_filter('cs_match_header_assignment', 'custom_thankyou_header');
function custom_thankyou_header($match) {
	if (is_page(123) ) {
		$match = 90; // the post ID for your header
	}
	return $match;
}

90 is the custom header ID and 123 is the page ID which is generated or displaying the thank you plugin. To know how to find or locate the page ID, please check this out: https://theme.co/apex/forum/t/setup-how-to-locate-post-ids/59

Hope this helps.

#5

Wonderful! It worked. Thanks so much.

If I can ask one additional question… how would I change the PHP code to work for a footer?

#6

Hello There,

You can also apply a similar code for the footer:

add_filter('cs_match_footer_assignment', 'custom_thankyou_footer');
function custom_thankyou_footer($match) {
	if (is_page(123) ) {
		$match = 90; // the post ID for your header
	}
	return $match;
}

Make sure that the correct page ID and the custom footer ID is used to make it work.

#7

That works. Thank you again!

#8

You are most welcome. :slight_smile:

#9

Sorry one additional question. So I used the PHP to set up the header and footer on the thank you page. But I notice the footer is formatted differently on the thank you page. Normally, the footer includes a subscribe button where the form and the blue button are on the same line. But on the thank you page, they are on separate lines. It’s not a spacing issue as I encounter the problem even when the form/button is all by itself on a single line. (If this is a question better directed to the plug-in developer, please let me know).

#10

Hey There,

​
​To assist you better with this issue, would you mind providing us the url of the page in question and your site with login credentials if necessary so we can take a closer look?

To do this, you can create a secure note with the following info:
– Link to your site
– WordPress Admin username / password
​
Thank you.

#11

The email form is from Ibericode’s Mailchimp for Wordpress plugin, but the problem has now been confirmed to be related to the Pro theme. See below for details:

  • The broken form in the footer occurs on most of the WooCoomerce pages — Checkout, Account and Thank You. (But not the Cart page).

  • The broken form is fixed as soon as I switch the theme to storefront so it is definitely related to how Pro theme is interacting with a few select pages.

  • I have put the shortcode for the broken form in the Account Page. So you can see plainly how the form breaks even though it has plenty of horizontal room to work with.

#12

Hello There,

I have logged in to your site and I could not replicate the issue.
This is what I am seeing:

By the way, Could you please update to the latest versions?
- Pro theme 2.2.5

This latest release contains fixes for several issues so be sure to check out the changelog (http://theme.co/changelog/).

_After doing the updates, always remember to clear all caches (if you are using WP Rocket, WP SuperCache or W3 Total Cache) when updating so that the code from the latest release is always in use. This will help you to avoid any potential errors.-

Please let us know how it goes.

#13

Thanks. Our re updating the Pro theme.

In response to your reply, two things…

First, can you please set the screenshots to private as I’d prefer not to have them publicized.

Second, the problem only occurs on specific pages. I have had third parties try it from different computers in different locations… so it IS NOT a caching issue.

I will provide a specific page link where the error occurs in the secured note.

#14

Hi,

The plugin is in conflict with the theme’s css. Since it’s a simple fix I will provide you with the css code.

You can add this in Theme Options > CSS

.mc4wp-form .mc4wp-form-fields input {
     width:auto;
}

If you need more in depth changes, you may wish to consult with a developer as this is outside the scope of support. X is quite extensible with child themes, so there are plenty of possibilities.

For future reference, I came up with the code using google inspect element.
In case you want to learn, you may refer to the links below.

Thanks

#15

Ok, thanks very much for the CSS update. And also thank you for the links. I will definitely check them out.

#16

You’re more than welcome, glad we could help.

Cheers!

#17

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.