Skip Navigation

[Resolved] Toolset display issues in subsite of multisite build

This support ticket is created 3 years, 9 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 - - 9:00 – 13:00
14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 - - 14:00 – 18:00

Supporter timezone: Africa/Casablanca (GMT+01:00)

Tagged: 

This topic contains 14 replies, has 2 voices.

Last updated by serenus 3 years, 9 months ago.

Assisted by: Jamal.

Author
Posts
#1944209
sub_site.jpg
main_site.jpg

I have moved a single site to a the subsite of a multisite installation. I use some of the same (i.e., same build, same code) content templates, views, & layouts in both the main site and the subsite. Themes are also very similar. However, the Toolset in the subsite do not display correctly. I have tried to activate Toolset at network level or at site level. That makes no difference. I do not know what to try anymore to fix this issue.

#1945601

Hello and thank you for contacting the Toolset support.

It seems that some styles are missing from the migrated site, this needs to be debugged a bit with the browser dev tools to understand what are the missing styles, and where they come from. Can you share the URLs of both pages to let me check?

#1945697

Thanks, Jamal. Any pointers will be much appreciated.
Main: hidden link
Sub: hidden link

The particular screenshots are for a Toolset content template for logged users only but the problem is throughout the sub-site. I have removed the two content templates on the frontpage of the sub because they were displaying completely wrong in the sub. The problem, whatever it is, should be viewable anywhere.

#1945703

I am sorry but I can't see any style differences. The screenshot that you have added showcases an example of style differences(buttons, and the texts below icons).

If you can share two URLs for the pages where these screenshots are used, I can give it a try.

If not, please share another example. Let me know what styles are differents and what URLs where I can see that on both sites.

#1945705

I am sorry but I can't see any style differences. The screenshot that you have added showcases an example of style differences(buttons, and the texts below icons).

If you can share two URLs for the pages where these screenshots are used, I can give it a try.

If not, please share another example. Let me know what styles are differents and what URLs where I can see that on both sites.

If this needs to have a logged in user, your next reply will be private to let you share credentials safely. ** Make a database backup before sharing credentials. **

#1945779

Thank you for these details.

Regarding the space between icons and the text below them, the subsite generates an additional empty <p> tag as you can see in this screenshot hidden link
I removed it from the browser console in the "CONNECT WITH OTHER WOAWIES" section, which is not persistent, and it seems to produce the expected results.

Regarding the buttons' styles, it seems that both sites use different styles. The root site uses bootstrap.css and the subsite uses bootstrap.min.css. The root site includes some styles in style.css for the "btn-default" class, while the subsite does not have such styles.

It turns out that both sites use different themes and load different versions of bootstrap in the Toolset settings:
- Different themes: hidden link
- Different Bootstrap version in Toolset->Settings->General(tab): hidden link

I hope this helps. Let me know if you have any questions.

#1945839

Thanks for pointing out the lack of consistency in the settings between the two sections. That solves some of the problems in the sub.

However, I still do not know what inserts the additional <p> tags automatically. They are not in the template. I tried the "manual" and the "automatic" paragraph settings but that appears to not make a difference for this issue.

#1945853

The page is using a layout that displays the title and the page content. And the page content displays a content template. I tried to pass different arguments to the wpv-post-body shortcode, but it did not help.

I suspect that this is caused by the theme or another plugin. The themes are different between the websites, and both websites use different sets of plugins. So, I thought to fix it using custom Javascript code that will remove the empty tags. I added it to the content template and it does remove the empty tags hidden link

( function( $ ) {

	$( 'p' ).each( function() {
		var $this = $( this );
		if ( $this.html().replace( /\s| /g, '' ).length === 0 ) {
			$this.remove();
		}
	});

})( jQuery );

I hope this is a viable workaround for you. Let me know if you have further questions.

#1948271

What I meant by same style / same plugins was "as before I imported everything in the sub-site". Everything was happy together there. Both the main & sub use a generatepress child theme. There is not much difference between the two.

Your solution works but I not comfortable with a website standing with underlying issues. I just did a test Toolset blocks (using Toolset view before) to take some layers off. It appears to wok. That's good but I was planning to rebuild most everything in the sub...

A note. Toolset blocks appears to be fantastic. Great job.

#1948861

Thank you for your feedback. Toolset Blocks is still evolving and we are not yet where we want it to be. We are working on it and we'll get there.

I understand your point of view. An issue needs to be resolved. We can continue debugging it and find out the cause of it. But, I wanted to offer a workaround, so you don't get stuck with something that does not work as expected.
To continue debugging the cause of these empty tags, we'll need to perform several tests:
- Compatibility test: we'll need to check if the issue happens with a default theme(such as 2020) and only Toolset plugins.
- Server test: Will this issue appears if the multisite runs on a different server(eg: my local server, or our online platform).
Depending on the results we'll decide what to do next.

If you want us to continue debugging, I wonder if you could copy the whole multisite into a staging site, where I can perform tests without impacting active users. We may also need to take a copy of your multisite to run it on our servers. Let me know what would you prefer.

#1953021

I am still in process of cleaning up stuff & transferring to the "new" WordPress to see if it will take care of the issue. If it does not, I will move everything to a staging area and advise you.

#1958025

Ok. I'll remain at your disposal.

In the meantime, I am setting this ticket as waiting for your feedback. It should be kept open for 3 weeks, and you will receive an email notification before it is closed.

#1960663

I seem to have resolved the original "look" issues by rebuilding from scratch in the new WordPress.
However, I am running into some conflicts with WooCommerce (e.g., billing fields layout - found the css fix). Are there known issues with WooCommerce besides css?
Is there an activation preference on multisites (i.e., network activate vs. individual site activate).
Sadly, I cannot use staging at my host because it is a multisite setup. It only available for single WordPress installs.

New threads created by Jamal and linked to this one are listed below:

https://toolset.com/forums/topic/conflicts-with-woocommerce/

#1961183

I am glad you could fix the issues with your website. I hope I was of some help.

However, for support rules, we are able to handle only one issue at a time. This helps us to bring you a better service and also helps other users to find all the information here exposed. For that reason, I have created another ticket for you and I'll post my replies there.

#1967435

My issue is resolved now. Thank you!