Contact Us not working, receiving alert messages even though all fields filled in

mc12345678:

And if there is not an htaccess in the "shop" directory, how about the directory above that?

Just to avoid further confusion - there will be NO directory above that since this is a subdomain and the store is in the root...

balihr:

Just to avoid further confusion - there will be NO directory above that since this is a subdomain and the store is in the root...

So you're saying that an htaccess in:

/home/content/a/t/o/atomicorchard/html

Has no impact on:

/home/content/a/t/o/atomicorchard/html/shop

Which is a subdirectory of the former?

Yes, that's what I'm saying. That's the idea with a subdomain instead of a subfolder. Am I missing something? :lookaroun

Me apologizes... Me wrong... :oops::lamo:

mc12345678 was absolutely right - check the above folder as well. Sorry.

balihr:

Yes, that's what I'm saying. That's the idea with a subdomain instead of a subfolder. Am I missing something? :lookaroun

balihr:

Me apologizes... Me wrong... :oops::lamo:

mc12345678 was absolutely right - check the above folder as well. Sorry.

Valid question and hopefully don't feel like a "right" person "wrong" person thing or that it will negatively affect future postings, balihr offers good solutions to issues. We all make mistakes.

For a feeble attempt at an explanation about this, htaccess files are server side files propogating to the sub-directories below them (generally speaking). "Properly" implemented, if sub-domains are located outside of a "primary domain" and each has it's own htaccess file then there will be no intermingling... So yes one structural goal of a sub-domain is for it to have it's own htaccess file (if one is to be used as ZC doesn't require one) with no htaccess file commands in a parent folder that apply undesireable effects to the "children".

Hopefully though the cause of this issue will be soon discovered and corrected. :)

Thank you very much for all your help! I will post the info later this evening after I get out of work. I appreciate it!

mc12345678:

Valid question and hopefully don't feel like a "right" person "wrong" person thing or that it will negatively affect future postings, balihr offers good solutions to issues. We all make mistakes.

For a feeble attempt at an explanation about this, htaccess files are server side files propogating to the sub-directories below them (generally speaking). "Properly" implemented, if sub-domains are located outside of a "primary domain" and each has it's own htaccess file then there will be no intermingling... So yes one structural goal of a sub-domain is for it to have it's own htaccess file (if one is to be used as ZC doesn't require one) with no htaccess file commands in a parent folder that apply undesireable effects to the "children".

Hopefully though the cause of this issue will be soon discovered and corrected. :)

Ok... so I tried it with disabling SSL, and it didn't change anything. Still getting the same error messages. However...I did notice that even with SSL enabled, the Contact page is showing that Https is not set up correct, as it's saying it includes other resources that are not secure. So either that's a separate issue unto itself, or related to this issue...

For the Htaccess file, here is the htaccess for my root folder (in the main 'shop' subdirectory folder):

RewriteEngine On
RewriteCond %{SERVER_PORT} !=443
RewriteCond %{HTTP_HOST} ^(www.)?shop.atomicorchard.com$ [NC]
RewriteRule ^ https://shop.atomicorchard.com/%{REQUEST_URI} [R,L]

One idea I had was maybe that 'www' part should be different, as my site with the ssl is only set for https://shop.atomicorchard.com

I also have an htaccess file in my main website root folder, as I have SSL on the mainpage as well. This is the htaccess file for that main page root folder (www.atomicorchard.com):

RewriteEngine On
RewriteCond %{SERVER_PORT} !=443
RewriteCond %{HTTP_HOST} ^(www.)?atomicorchard.com$ [NC]
RewriteRule ^ https://www.atomicorchard.com/%{REQUEST_URI} [R,L]

Let me know what you think.... again, I really appreciate your help. If any of you figure it out, I'll send you a free t-shirt from this site (if you want) :)

Just found where that extra "/" is coming from.... the htaccess file! ok, got that straightened out.

Dang, no free tshirt :)

So, is the contact page working now?

Never mind, I see that it isn't. Can you turn the SSL off again if you are still there? I see that message that you spoke of.

L

blackeyed5:

Just found where that extra "/" is coming from.... the htaccess file! ok, got that straightened out.

So what was the specific issue then? (Ie. to help others that might have the same issue/come across this thread.)

As for the mixed content, that is a separate issue and can/should be addressed... I think there is a FAQ about it and it provides guidance on how to find/identify/correct all of those issues or at least make a good start at it..

Congrats on fixing the // issue, does it resolve the original issue? On my test a moment ago the answer is no it did not. :/ I did receive a notice that submission of the form would send the information insecurely... So seems something is "off"...

Did we ever ask if you were getting any errors in your log files?

lruskauff:

Never mind, I see that it isn't. Can you turn the SSL off again if you are still there? I see that message that you spoke of.

L

Ha, yeah, don't worry....free shirt is still available.

Ok, I just set the enable to 'false' for https. So it's off now (i'm assuming... it doesn't go to http, it just puts the error message on the https).

mc12345678:

So what was the specific issue then? (Ie. to help others that might have the same issue/come across this thread.)

As for the mixed content, that is a separate issue and can/should be addressed... I think there is a FAQ about it and it provides guidance on how to find/identify/correct all of those issues or at least make a good start at it..

Congrats on fixing the // issue, does it resolve the original issue? On my test a moment ago the answer is no it did not. :/ I did receive a notice that submission of the form would send the information insecurely... So seems something is "off"...

Yeah, all the issues are still present. I only fixed the extra slash issue by deleting the extra slash from the htaccess file. Sorry for being misleading!

lruskauff:

Did we ever ask if you were getting any errors in your log files?

How would the errors appear? (I'm more of a graphic designer with HTML knowledge, so some stuff you have to walk me through. I apologize for that). Looking in the Logs folder, there are 3 files: index.php, index.html, .htaccess, and then there is the _notes folder with a dwsync.xml file in it.

Are these files normal to be in there, or do they appear there because there's an error or something with them?

Turn SSL back on please. I'm comparing it to my site (same template designer) and I think we need to figure out why those pages aren't secure. MC12345678, what do you think?

Also, on your double "//" , did you actually have a double "//" somewhere or was it a trailing "/"? Can you show us the line before and after?

lruskauff:

Turn SSL back on please. I'm comparing it to my site (same template designer) and I think we need to figure out why those pages aren't secure. MC12345678, what do you think?

Also, on your double "//" , did you actually have a double "//" somewhere or was it a trailing "/"? Can you show us the line before and after?

Ok, SSL back on.

no, it was just a trailing "/".

In the htaccess file, I noticed I had the / after the name, which I probably shouldn't have had.

So I had this:

RewriteEngine On
RewriteCond %{SERVER_PORT} !=443
RewriteCond %{HTTP_HOST} ^(www.)?shop.atomicorchard.com$ [NC]
RewriteRule ^ https://shop.atomicorchard.com/%{REQUEST_URI} [R,L]

And I deleted the / so I would have this:

RewriteEngine On
RewriteCond %{SERVER_PORT} !=443
RewriteCond %{HTTP_HOST} ^(www.)?shop.atomicorchard.com$ [NC]
RewriteRule ^ https://shop.atomicorchard.com%{REQUEST_URI} [R,L]

And that got rid of it.

It says it is still in maintenance.

never mind

lruskauff:

It says it is still in maintenance.

never mind

Hmm, it shouldn't... I'm not uploading or anything, and I never set it to maintenance. Maybe it just takes a couple minutes?

If I go to: https://www.atomicorchard.com/contact.html I get the message you are in maintenance mode, and this site is marked as SSL.

If I go to: https://shop.atomicorchard.com/ it crosses out the https (site not SSL).

Are these two linked? Did you turn the SSL on the wrong shop?