Ok, before you all jump on this, I now relize I needed to edit the sql file that was in the contrib itself. I was looking everywhere else but the file itself. It was in my own quote! Yea, like you never could find your glasses when they were resting on your nose.
Now I am going to try and fix my unsussesful sql installs and hope not to create any damages to DB, although it appears and checks ok.
(yea I backed up) but i want to learn how to repair. I see referances to other contrib causing simlar conficts so I'll need to learn how this works and what undos are available besides reinstal backup.
These are my clues;
error first try
1062 Duplicate entry '469' for key 1
(original sql.)
#2nd try sql instal
(only changed 469 to 950)
1062 Duplicate entry '470' for key 1
# 3rd try
and after changing all 469+ referances starting with 469 to 950, for 470 into 951, 470 to 952, - etc.
I got;
6 statements processed.
ERROR: Cannot create table user_tracking because it already exists
ERROR: Cannot insert configuration_key "ADMIN_CONFIG_USER_TRACKING" because it already exists
ERROR: Cannot insert configuration_key "CONFIG_USER_TRACKING_EXCLUDED" because it already exists
Note: 3 statements ignored. See "upgrade_exceptions" table for additional details.
The zen admin user tracking entrys are there, the file code is in footer, but nothing is recording and user tracking appears turned off when I look at it in phpMyAdmin.
So off I go to consult the search wizards and reread what I read until it sinks in.


Reply With Quote

