Messages

Evolution: That also generated warning messages.

But my point is that AbanteCart should accept any valid URL without generating warning messages.

On the System > Setttings > Checkout page, the description of the 'Require login name' option name is in Spanish instead of English:

"Para mejorar la seguridad, preguntar a los clientes a crear el nombre de inicio de sesión único. Si se establece en ON, los clientes existentes se les pedirá que crear nuevo nombre de usuario en el primer inicio de sesión. Si OFF, nombre de usuario es la misma que la dirección de correo electrónico."

Google translates this as:

"To improve security, ask customers to create the logon name only. If set to ON, existing customers will be asked to create new user name in the first login. If OFF, username is the same as the email address."

> If you specify https as the protocol, it means that ALL pages of AbanteCart ONLY available via ssl.

And that is exactly what I want. My .htaccess file is set to convert any http request to https, so all pages are always referenced vial ssl.

> If you turn off ssl (by mistake or hack-attack) in the error log will be written to the store owner took action.

I don't understand what that means.

> If you plan to use both protocols, you should specify a URL prefix http://

I do not play to ever use the http protocol (see above). If I only want to use https, I believe that I should be able to specify the URL that way without generating warning messages.

Got it, thanks!

I found many instances of this message in the Error Log. After trying a few things, it appears that this message is issued when the Store URL in Settings->General starts with 'https://'. When I changed the setting to 'http://' I stopped getting the messages.

This is isn't a big problem for me, because my .htaccess is set to convert all http accesses to https. (I run my commerce sites with all pages under https so I don't need to worry about which parts of the site are protected.)

However, https should be a valid prefix in the URL setting, and should not cause warning messages.

~~ Grey

After upgrading to V1.1.6 I found the following message in the Message Manager:

Error: Can't upgrade file : 'admin/controller/common/page_layout.php

All file and directory permissions are set per the installation instructions. I got a message that the 'extensions' directory was not writeable, even though it is. I suspect it was complaining about one of the subdirectories. (I just did a recursive permissions change to '777' for everything in 'extensions' so that should not be an issue in the future.)

I completed the upgrade using the FTP option, and everything seems to be fine except for this error message.

~~ Grey