xyz.com not working; www.xyz.com is working

hy,
please try to swap the lines in your config. and of course always delete your sites cache and browser cache when testing.
i noticed that your webfonts are not loading on the mapped domain. you should enable CORS on your page for your domains to allow shared resources across domains. as a starting point: https://enable-cors.org/server_apache.html

if you like the plugin i am always happy to see a positive review ?? and if you use it for business purpose, a small donation is also appreciated ??

matt

Excellent! Trying this in 20 minutes. Thanks so much. Review *and* donation coming shortly..

Really appreciate the tips on CORS as well.

Just tried – and had the same result (for clarity – I deleted the previous mappings; saved the page; added the mappings back with ciencetech.com first and https://www.ciencetech.com second). Then cleared test browser cache and reloaded.

Still have the mapping *working* at https://www.ciencetech.com and not working at ciencetech.com.

Any other thoughts?

hy,

hmmm – it could be that you found a bug here since ciencetech.com and cience.com start with the same characters. but this is only a thought, i will have to investigate that in our testing environment.

by now, you could try to redirect ciencetech.com to https://www.ciencetech.com in your .htaccess file:

RewriteCond %{HTTP_HOST} ^ciencetech.com$ [NC]
RewriteRule (.*) https://www.ciencetech.com/$1 [R=301,L] 

the possibility for an automatic redirection is on our roadmap as well, fyi ??

please report back if that helped

Thanks Mattias!

I opened the .htaccess file, and there are a bunch of settings there already adjusting those parameters – I’ll try to troubleshoot with our web guy on Monday.

Just to see if I could trouble shoot from another angle, I tried with another domain (leadware.io) and had the same problem. https://www.leadware.io works, and leadware.io doesn’t. Both are mapped to /leadware..

Seems like this probably suggests something else going wrong elsewhere (likely not in the add-on).

Will let you know what we discover. Certainly open to any other troubleshooting ideas from you, but don’t want to abuse your offer for assistance!

(also will try to address the CORS bit on Monday with the web guy!)

hy,

yes the .htaccess file should be edited only if you know exactly what you do ??

the additional testing is a really good hint. looks like you will have to try the (sometimes hard) task of disabling plugins and switching to standard theme one by one to see if anything causes the problem :/

i guess further assistance would need to share login data. usually i do not do this, but it looks like you know how to communicate in a support forum and appreciate the help ?? if you need me there, please find my mail address at matthias-wagner.at after talking to your web-guy

matt

any updates on this?

So sorry for the delay here Mattias, especially after your gracious earlier offers.

We had to put the troubleshooting on hold while we tried a different approach, but will be back to it in the next 60 days or so once the dust settles. If we discover anything new or have anything new to report, I will return here and post an update.

Thanks again for your help and attention..