shipping rates no longer work

[RodG]

It would appear that was relating to 'ssu' which is no longer supported

There is/was *nothing* in the log file that you posted that suggested that this was involved in any way. I acknowledge that it may have been further down in the log file (these can get quite large, and we don't need to see them all), but wasn't my 1st piece of advice:

------------------------------------------------------
This looks like you have one or more 'corrupted' files. The error above is the 1st error you'll need to take care of, which may or may not take care of the errors that follow (these things have a cascading effect).

You'll need to work through the error messages one at a time 'cos you may have more than one problem.
--------------------------------------------------------

You have somehow managed to skip the error reported by 'session.php' error and gone of on a wild tangent with something that may or may not have been something that needed to be fixed separately from any previous fixes. If you wish to have any hope of a recovery you must work in precise *logical* steps. If you can't do that, then give up all recovery attempts now. It will be quicker to re-install a fresh system (keeping your existing database of course).

but also seo urls which i have now installed.

BIG MISTAKE. You should fix the problems you already have before adding more stuff that can only make matters worse.

Shipping still doesnt display though.

I'm a wee bit surprised much of anything at all is working really. The sessions.php file (and the files that *it* loads, eg, query_factory.php) are essential for the store to function.

It is also for this reason you shouldn't go messing with things hoping to stumble across a fix. I fear that your store is in a very precarious state at the moment and that it could be reading some files from /public_html/2013update/includes/functions/sessions.php and some from /public_html/includes/functions/sessions.php, or any one of an infinite number of other variants/possibilities.

Is there a way to refresh the logs? Or will it only create new logs if different errors are created?

Yeah. Just delete them. New ones will be create is/when further errors occur.

edit:
with shipping estimator added to the cart you can click a button and see how much postage should cost... it doesnt add it to the overall cart though.

This could be a matter of the shipping not being enabled in the modules->order_total settings.

Anyway, so exactly where are we up to now? From the way I'm reading things, I'm not sure exactly what you've done, but it now all seems to be working correctly (other than the final total addition?). If this isn't correct, please supply a copy of the first few entries and any 'new' error logs and we'll continue the debugging from there.

Cheers
Rod

[RodG]

just to add another update, i have tried using the old factory.php file from 1.3.9 but it still doesnt work.

Never ever use old zencart code on a newer installation (especially the core code). This will never help.
Replacing the store copy from the zencart distribution files (of the same version) is the only thing that will work as a 'is it this file or isn't it'? test.

Besides, what we are seeking is a *missing* file, not a changed or corrupted file. These produce a different error message. Usually a 'Syntax' error. You have already seen (and fixed) one of these.

The computer says it is missing file (not found where it is expected to be found).
You say it *is* where the computer is telling it is.

One of you has made a mistake.
Computers don't make mistakes.

win merge shows the files as being almost the same, just slightly different in places..

These slight differences could be enough to cause the code to fail (at best). Using the older code could also be re-introducing some old bugs or security issues. You must revert this file back to the correct one for your zencart distribution. Even if it doesn't cause any problems now, it may well be the source of hard to find issues at a later date.

is there a way of taking this section along with the database back to standard?
I dont know how to repair this part :/

There is pretty much always a way to do almost anything. All it takes is enough time and money, and THAT is the key question.

You could be just 5minutes away from a complete fix, or depending on how many tangents you follow it could take weeks, and eventually become a near impossible task anyway.

Meanwhile, a 'going back to standard' will take somewhere in between these two extremes.

There is no way to know in advance which is going to be the quickest solution, but as a general rule, problems that arise due to updates are generally a lot quicker and easier to fix than starting afresh.

Only one thing though. You must take it slow. Fix one 'fault' at a time in the order they appear in the error logs, and avoid the urge to jump the gun.

Also *READ* the error messages. If one says 'syntax error', another says 'permission denied' and a 3rd says 'file not found', there is little amiguity that they are not the same errors, therefore is is wrong to think that they will all need to be fixed in the same way.

My current concern is that you say one thing, the computer is saying another. As much as I'd like to think that a computer can make a mistake, it just doesn't happen. I'm somewhat counting on the fact that if we can solve this apparent contradiction the rest will start to fall into place. That's my hope anyway.

Cheers
Rod