At first I thought I wrote something in custom CSS that make my header title and subtitle vanish, but after browsing more I found out that pages/posts, that weren’t edited with page builder, had maintitle and subtitle show up. Just to be sure, I’ve tried disabling each plugins to find the culprit. Page builder was the cause. I need page builder to make the website smooth and responsive, but I also need both maintitle and subtitle visible. Any advice is appreciated.
h2 class maintitle and subtitle missing on pages with siteorigin page builder
This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.
Hi Justasm,
To clarify, is the maintitle and subtitle something your theme adds? If not, what is adding it? Do you have a public URL where we can take a look at what’s going on? If you need to keep this URL private from other users, just select “Private Reply” on the bottom right of the comment box.
Both main and sub titles are a part of Sydney theme header. I’m currently using wordpress localhost. It works fine on pages without pagebuilder so maybe there’s some sort of conflict between the theme and plugin ?
Hi Justasm,
Sydney directly integrates with SiteOrigin Page Builder so, to be honest, it’s very unlikely that it’s a conflict.
Hm, that makes it tricky. Can you please view the relevant page and then press CTRL + S and save the page as Web Page, Complete. This will generate an HTML file and an assets directory. Please archive and send me both – you’ll need to do this via a third party hosting site. I recommend teknik.io
This is a private message.
Hi Justasm,
Well, apparently the Sydney theme doesn’t survive the page save very well. :/
Regardless, I can see the markup for the header and the subtitle in the provided page. I suspect that the JavaScript associated with said functionality isn’t able to run for whatever reason. Can you please send me the contents of your console when viewing the relevant page? Please refer to this guide on how to access your browser console.
This is a private message.
Hi Justasm,
You can safely ignore the JQMIGRATE message – that’s purely a debug notice.
The Mozilla warning can also be safely ignored – it won’t cause this issue and is purely a performance warning.
At this stage, without seeing the website itself, I’m not really able to work out why this is happening as I can’t seem to replicate this issue locally. I would recommend getting in contact with aThemes to see if they’ve had any similar reports.
I’m sorry I can’t be of more assistance at this time.
Understood. Thank you for your support.