muntle

OK, I have now worked-out the first part, so no need to answer that. Still need an answer to the second paragraph.

On the live site, I encountered a fatal error. It would appear that this is due to a clash with the events plugin we are using. You said in the response nearly a year ago that this would be fixed soon, is there any timescale on that please?

OK, at least we know what it is. The ‘devastation’ caused is not limited to headers, by the way, it also changes other formatting, eg button defaults. So it’s a little more than a minor ‘problem’, as finding all the bits took me more than an hour this morning, and I have had to stop the client from broadcasting blogs until I can sort it satisfactorily.

The first question, therefore, is can you 100% guarantee that your Divi add-on solves this? The reason I ask is that you want me to pay $97 to buy it, along with a great load of other addons that I will never use. Is it not available separately?

Anyone there to answer this?

Thanks for the comment, and I absolutely agree, which is why I applied a wildcard ssl certificate to the subdomain multisite I mentioned. It is also important to remember to use subdomains and a wildcard ssl if you want to map other domain names to the subdomains, in which case you must also add all of the other domain names to the certificate before you try any mapping.

However, you do NOT need a wildcard ssl certificate for a sub-directory multisite, which is what this thread was pertaining to.

Marking as Resolved

Thank You ospiotr, spot on! I hadn’t looked at that particular codex link, because I was looking specifically for multisite references. The first option of adding those two lines in the wp-config resolved the issue. Also worked on a sub-domain multisite I have as well.

No problem, managed to sort it.