I was trying to do an upgrade to the latest release (c) just downloaded today. I did it as a new install in a new directory with new database. Per the install itself everything seemed to go fine.

Then when I log in to the admin I see a text list of the admin options on the left side of the screen. There appears to be no style sheet associated but then I have never seen the new release before so don't know what I should see.

But none of the links function. I can't access any admin settings.

Also the store front page is just a blank white screen.

I have installed a lot of Zen carts in the past but have never seen this problem before.

Did I miss something? Is there a bug in the new release?:unsure:

That's not a bug in the new release. Something is amuck with one or more things in your merging of changes to files, and/or your upload of components to the server.

You can start here as a first step in attempting to find out what's causing your blank pages:
https://www.zen-cart.com/tutorials/index.php?article=82
https://www.zen-cart.com/tutorials/index.php?article=87

I did not merge anything yet. As stated above I did a clean new install and have not been able to get to the point of merging anything.

Left old cart in place, new database etc. NOTHING of the old cart has been added to the new installation at all.

:lookaroun

Is it a problem with the stylesheet not loading?
Maybe your host doesn't like the settings in your /admin/.htaccess file? or the /admin/includes/.htaccess file?
https://www.zen-cart.com/tutorials/index.php?article=235

DrByte:

Is it a problem with the stylesheet not loading?
Maybe your host doesn't like the settings in your /admin/.htaccess file? or the /admin/includes/.htaccess file?
https://www.zen-cart.com/tutorials/index.php?article=235

Are these settings something other than in past distributions? I have no issues with many other installs on same server. What would I look for?

Much smarter security protections are included in v1.3.9.
However, there is the occasional server whose administrator has set up restrictions which cause the .htaccess protection rules to not work. In those cases you'll have to work with your hosting company to come up with alternative .htaccess rules that will provide the same security protections. Either that or you're welcome to leave your site open to hackers.

DrByte:

Much smarter security protections are included in v1.3.9.
However, there is the occasional server whose administrator has set up restrictions which cause the .htaccess protection rules to not work. In those cases you'll have to work with your hosting company to come up with alternative .htaccess rules that will provide the same security protections. Either that or you're welcome to leave your site open to hackers.

Where is the info in this instance. I have my own server so don't have a "hosting company" to ask.

Is there forthcoming an automatic update capability. From what I have seen so far this is going to be a major pain for anyone with a bunch of sites to upgrade.

Paul

stuffdone:

Where is the info in this instance. I have my own server so don't have a "hosting company" to ask.
In the .htaccess files I mentioned there are instructions explaining the server requirements.

DrByte:

In the .htaccess files I mentioned there are instructions explaining the server requirements.

I will go have a look.

PK

stuffdone:

I will go have a look.

PK
If you refer to this line:

The following blocks direct HTTP requests to all filetypes in this directory recursively, except certain approved exceptions

It also prevents the ability of any scripts to run. No type of script, be it PHP, PERL or whatever, can normally be executed if ExecCGI is disabled.

Will also prevent people from seeing what is in the dir. and any sub-directories

For this to work, you must include either 'All' or at least: 'Limit' and 'Indexes' parameters to the AllowOverride configuration in your apache/conf/httpd.conf file.

I am concerned that making this change might have a negative impact on other sites...what do you think? Remember this same server has a lot of CMS programs and a number of shopping carts installed including a number of prior versions of ZEN and they can't all be updated at once. I can't change anything for one update that could cause anything else to cease to function.

My server won't allow file browsing anyway but the bit about not allowing scripts to run including PHP is the line that bothers me since most of my sites run PHP.

Paul

The issue of preventing scripts refers only to the use of OPTIONS -ExecCGI ... which isn't even used in that file (that help text was copied from all the other similar .htaccess files elsewhere in Zen Cart, where the OPTIONS -ExecCGI line is included ... but we opted not to list that one in this admin file you're looking at, and thus some of the help text doesn't apply in this case).

So, for your case, you just need to add "Limit" and "Indexes" choices to your "AllowOverride" configuration in your httpd.conf file.
For help in understanding the httpd.conf file and all its zillion configuration choices, see apache.org

This is what my techs in the NOC said of this:

"You would not want to add this configuration globally to the httpd.conf as it would render all your web files inaccessible, what you would want to do is add it to .htaccess on a per directory bases as this only effect that directory and sub directories (not global to the server)."

I can't risk any update to one application that could cause me troubles on many dozens of other web sites. But if this from techs is correct anything I need is in the .htaccess file provided and I don't need to do anything to my conf file anyway.

Fair enough. So, apply the edit to the folder where your store runs. Also done in your httpd.conf or your vhost configuration.
Why not just ask your NOC how to do it in the first place?

DrByte:

Fair enough. So, apply the edit to the folder where your store runs. Also done in your httpd.conf or your vhost configuration.
Why not just ask your NOC how to do it in the first place?

I am not a linux tech and prefer to keep my hands out of configuration. I pay for managed dedicated server so let them take care of such things for me.

I don't want to risk playing with things I don't know well. :wink:

I won't get into upgrades that require me to monkey with server configuration files.