[Closed] FEEDBACK ON BETA of v1.5.5

Quote:

---

Originally Posted by DrByte

Also using Navicat I discovered that you have a single customer record in your particular DB whose customers_dob is set to '0000-00-00 00:00:00' (which is invalid in modern MySQL versions) instead of '0001-01-01 00:00:00'. Changing that lets the installer properly update the schema in the customers table for the v153 changes, and lets the installer proceed.

---

I have no clue as to how the date was changed but, you are right, it should not have been what it was.
Could you share your Navicat method for finding this? I've had no luck in doing so myself. Of course, a sort in the customer table works but, I've found this in more than one database. It would be nice to have a shortcut for doing this since several of our current sites transferred in. it would be prudent for me to check a little closer before updating.
THANX

Quote:

---

Originally Posted by dbltoe

I have no clue as to how the date was changed but, you are right, it should not have been what it was.
Could you share your Navicat method for finding this? I've had no luck in doing so myself. Of course, a sort in the customer table works but, I've found this in more than one database. It would be nice to have a shortcut for doing this since several of our current sites transferred in. it would be prudent for me to check a little closer before updating.
THANX

---

I just used the sort.

Yeah, knew that. Just thought you knew some way of using search.

Quote:

---

Originally Posted by dbltoe

Yeah, knew that. Just thought you knew some way of using search.

---

I suppose a simple SQL query would suffice, like "select * from customers where customers_dob = '0000-00-00 00:00:00' ".
But I usually avoid that since I'm intending to fix the bad data at the same time, so a couple clicks gets me there faster than typing out a query and guessing the field name, etc.

Hi , just saw that 1.5.5 is coming up.
I'm currently updating from 1.51 to 54, but still in a early stage.
Should I proceed with 1.54, or wait a litle while ? I mean, it's a matter of a couple of weeks or a long way to go ?

Thanks

Quote:

---

Originally Posted by mesnitu

Should I proceed with 1.54, or wait a litle while ? I mean, it's a matter of a couple of weeks or a long way to go ?
Thanks

---

personally i would start the upgrade. the differences between 1.5.4 and 1.5.5 will probably be far less that the task of upgrading to 1.5.4 from 1.5.1.

my understanding is that 1.5.5 is close.... but the last 5% is always the hardest, and i do not think the ZC team will commit to a specific release date... until it is released.

just my 2c.

Quote:

---

Originally Posted by carlwhat

personally i would start the upgrade. the differences between 1.5.4 and 1.5.5 will probably be far less that the task of upgrading to 1.5.4 from 1.5.1.

my understanding is that 1.5.5 is close.... but the last 5% is always the hardest, and i do not think the ZC team will commit to a specific release date... until it is released.

just my 2c.

---

Yeah, I can understand that, I was just trying my luck :) You never know
But I think I'll wait. it's not only zencart, but all the modules, after a while, things get complex

admin_page_registration
id missing. I added it a long time ago, can't remember why...maybe just because all the others have one!

Quote:

---

<div>
<label for="pageParams"><?php echo TEXT_PAGE_PARAMS ?></label>
<?php echo zen_draw_input_field('page_params', $page_params, ' id="pageParams"');?>
<span><?php echo TEXT_EXAMPLE_PAGE_PARAMS ?></span>
</div>
<div>
<label for="menuKey"><?php echo TEXT_MENU_KEY ?></label>
<?php echo zen_draw_pull_down_menu('menu_key', $menu_options, $menu_key) ?>
</div>

---

Quote:

---

<label for="pageParams"><?php echo TEXT_PAGE_PARAMS ?></label>
<?php echo zen_draw_input_field('page_params', $page_params, ' id="pageParams"');?>
<span><?php echo TEXT_EXAMPLE_PAGE_PARAMS ?></span>
</div>
<div>
<label for="menuKey"><?php echo TEXT_MENU_KEY ?></label>
<?php echo zen_draw_pull_down_menu('menu_key', $menu_options, $menu_key, ' id="menuKey"') //steve added id ?>
</div>

---

Did another clean install today for testing and see this is still an issue and think it would be confusing for a new installer....

Quote:

---

Originally Posted by stellarweb

Had one problem with install - Running zc_install it says...

"We did not change your admin directory automatically as it already seems to have been changed from the default." but it DID automatically change the directory and does not allow it to be edited on that page.

So, perhaps it should say...."We changed your admin directory for security. You can change the name through FTP or FileManager when install is complete."

---

The issue below in quotes is still present with latest version tested today, vanilla DB, no mods, no demo products installed.

After adding a Text option Name.... then clicking Attribute Controller or going to product list and clicking the "A" by the product
goes to /options_values_manager.php
Warning: No Option Values have been defined

HTTP Server: Apache
PHP Version: 5.4.32 (Zend: 2.4.0)
PHP File Uploads: On
Upload Max Size: 2M
PHP Memory Limit: 128M
POST Max Size: 180M
Database: MySQL 5.5.48-cll
Database Host: localhost (127.0.0.1)
Database Date: 02/11/2016 15:22:54
Database Data Size: 211 kB
Database Index Size: 398 kB
MySQL Slow Query Log Status: On
MySQL Slow Query Log File: /var/lib/mysql/server-slow.log
MySQL Mode: (None set)

Zen Cart 1.5.5
Database Patch Level: 1.5.5
v1.5.5 [2016-02-11 15:08:46] (New Installation-v155)
v1.5.5 [2016-02-11 15:08:46] (New Installation-v155)

Quote:

---

Originally Posted by stellarweb

However.... we are still left with the core / vanilla 1.5.5 issue of not being allowed to add a text attribute to a product without first creating a "fake" non/text option name and value.

This happens when there are NO option names or values entered - which is the core settings. Guessing someone needs to revise that - otherwise people are not going to have a clue that they need to create that "fake" attribute in order to get a text attribute to work. This could be as simple as to just to include a "sample" option name and value in the core SQL. That would solve the issue as long as no one deletes that... has the page empty of attributes, then tries to enter a text attribute. :shocking:

---