Re: 1.3.9g -> 1.3.9h upgrade
Quote:
Originally Posted by
DrByte
If you display that admin page in your browser, where those customer or product details apparently don't "show", and then choose View Source in your browser, do those details show up in the raw HTML?
Also what CHARSET are you using in your english.php file?
What Character Set and/or collation is your database using?
I've already gone back to 1.3.9g (and the problems are solved), so I can't tell you whether customer & product details show up in View Source.
In my english.php files, CHARSET is iso-8859-1.
MySQL charset: UTF-8 Unicode (utf8)
MySQL connection collation: utf8_unicode_ci
Re: 1.3.9g -> 1.3.9h upgrade
Quote:
Originally Posted by
DrByte
If you display that admin page in your browser, where those customer or product details apparently don't "show", and then choose View Source in your browser, do those details show up in the raw HTML?
Also what CHARSET are you using in your english.php file?
What Character Set and/or collation is your database using?
Responses:
View Source --> I only see the dates in raw HTML, no names
Char set in english.php --> iso-8859-1 (only thing I see that mentioned char set)
Char set for db --> utf-8
Re: 1.3.9g -> 1.3.9h upgrade
Quote:
Originally Posted by
DrByte
If you display that admin page in your browser, where those customer or product details apparently don't "show", and then choose View Source in your browser, do those details show up in the raw HTML?
This is the source for the "New Customers" section:
<div class="header">New customers: </div>
<div class="row"><span class="left"><a href="http://www.donallnagealai.ie/shop/admin/customers.php?search=&origin=index" class="contentlink"> </a></span><span class="rigth">
28/10/2010 </span></div>
<div class="row"><span class="left"><a href="http://www.donallnagealai.ie/shop/admin/customers.php?search=&origin=index" class="contentlink"> </a></span><span class="rigth">
28/10/2010 </span></div>
<div class="row"><span class="left"><a href="http://www.donallnagealai.ie/shop/admin/customers.php?search=&origin=index" class="contentlink"> </a></span><span class="rigth">
26/10/2010 </span></div>
<div class="row"><span class="left"><a href="http://www.donallnagealai.ie/shop/admin/customers.php?search=&origin=index" class="contentlink"> </a></span><span class="rigth">
26/10/2010 </span></div>
<div class="row"><span class="left"><a href="http://www.donallnagealai.ie/shop/admin/customers.php?search=&origin=index" class="contentlink"> </a></span><span class="rigth">
23/10/2010 </span></div>
</div>
(I have actually renamed the "admin" directory but have edited the urls here for clarity)
So, no, the customer details don't appear in the source.
Here's a short extract from the corresponding source for the same page in version 1.3.9g:
<div class="row"><span class="left"><a href="http://www.donallnagealai.ie/shop/admin/customers.php?search=Deane&origin=index" class="contentlink">Michael Deane</a></span><span class="rigth">
28/10/2010 </span></div>
Quote:
Also what CHARSET are you using in your english.php file?
What Character Set and/or collation is your database using?
For english.php I have:
// charset for web pages and emails
define('CHARSET', 'iso-8859-1');
On the "Version" info page I have:
HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7
Is that what you're looking for?
In both cases it's unchanged from the default and is the same as I used in all the previous versions of Zen Cart up to 1.3.9g.
Regards
Nick
Re: 1.3.9g -> 1.3.9h upgrade
Curious to know whether your database tables are UTF8 or latin1
Re: 1.3.9g -> 1.3.9h upgrade
Is there something else you'd like for me to check?
Re: 1.3.9g -> 1.3.9h upgrade
Quote:
Originally Posted by
DrByte
Curious to know whether your database tables are UTF8 or latin1
Mine are UTF-8.
Regards
Nick
Re: 1.3.9g -> 1.3.9h upgrade
In post #21 nickgreaves posted "Database Patch Level: 1.3.9a".
Could that have anything to do with his problem, as his database isn't 1.3.9g, while he's trying to upgrade from 'g' to 'h'?
I mean, if he had a "working 1.3.9g", shouldn't the database reflect that?
Just a question..................
Re: 1.3.9g -> 1.3.9h upgrade
I too have upgraded from 1.3.9g to 1.3.9h and am experiencing the same problem. Original installation was 1.3.9b but I have upgraded religiously since then.
I have added new products and their descriptions as normal, but the description field disappears if I go back and have to edit something.
I have retraced my steps twice now but still the same problem. I noticed the problem occured before I added any of the new files, so assume it was one of the pages that was overwritten.
Server details are as follows:
PHP 5
Charset from english.php: iso-8859-1
SQL Charset: utf8 utf8_general_ci UTF-8 Unicode 3
SQL 5
Hope this helps. If anything isn't clear please ask and I shall clarify.
Thanks
Re: 1.3.9g -> 1.3.9h upgrade
Quote:
Originally Posted by
Get Em Fast
In post #21 nickgreaves posted "Database Patch Level: 1.3.9a".
Could that have anything to do with his problem, as his database isn't 1.3.9g, while he's trying to upgrade from 'g' to 'h'?
I mean, if he had a "working 1.3.9g", shouldn't the database reflect that?
Just a question..................
I don't think there have been any changes to the database structure since 1.3.9a. Certainly it was working fine with 1.3.9g so unless there has been a change between g and h (which isn't mentioned in the release notes), I doubt if this is the issue.
Regards
Nick
Re: 1.3.9g -> 1.3.9h upgrade
Quote:
Originally Posted by
nickgreaves
I don't think there have been any changes to the database structure since 1.3.9a. Certainly it was working fine with 1.3.9g so unless there has been a change between g and h (which isn't mentioned in the release notes), I doubt if this is the issue.
Regards
Nick
Yea, I know the docs say that there has been no database changes since "a", but I was thinking maybe something in the files just disagreed with "a". But, I know you're right.......I'm thinking that too, but I've seen stranger things happen, ya know?
Like I say though, it was just a question.......I already knew the answer before I posted, but curiosity made me post it anyway........haha.....that killed the cat, didn't it?