Show Posts

Messages - helperbee

Pages: [1] 2 3 ... 6
Extension Support / Technical Updates
« on: March 23, 2016, 01:24:21 AM »
I am trying to determine if the upcoming technical changes in will affect our payment extension. We are only using (AIM) payment extension.
See attached for complete details about the technical updates coming.

I know that RC4 Ciphering is not used by AbanteCart.
But I haven't been able to find anything about AbanteCarts and these:
Transaction ID field size > 10
Akamai SureRoute

Can someone tell me if any of these technical changes apply to us?

General Support / Re: password rules
« on: February 29, 2016, 01:24:44 PM »
Did you know what browser your customers use? What is your site URL?
If problem only with new customers does your host change something on your server - for example php version, add some php modules, change mysql version etc... This info may help to catch problem.

Yes, our host did change PHP version to 5.6.
Site URL:

When I use Chrome to reset password, it works. The other browsers our customers use are Firefox, Safari and Internet Explorer.

General Support / Re: password rules
« on: February 24, 2016, 11:41:26 AM »
Thanks for your response. We did not change SALT value in config.php.
Only new customers are are having problems with the functioning of their initial password. Even when they use the "Forgot Password" the reset password does not work for them. Once we change their password for them, they have no problem logging in.

Does anyone else have these problems? Can you share any troubleshooting tips or ideas why 15% of our customers struggle with password use?

General Support / password rules
« on: February 22, 2016, 03:46:14 PM »
Our customers continue to have problems logging in. Once we reset their passwords for them, they can log in. We're wondering if there are password rules which limit the use of certain characters.

I've searched documentation and the forum for details on password creation limits.

General Support / Re: "Act on Behalf" not working
« on: February 19, 2016, 07:31:40 PM »
Thanks to your diligence, the latest sql was successful! Thank you! However, it did not fix the problem. Act on Behalf still requires a repeat login and fails with invalid token error. :'(

General Support / Re: "Act on Behalf" not working
« on: February 19, 2016, 03:07:31 PM »
Sorry to report that didn't work. Even when auto_increment" was set to 0, the new value in "store_id" became 1. It was a good idea, however.
On my own, I tried setting the auto_increment to -1, but that SQL failed.

What do you recommend next?

General Support / Re: "Act on Behalf" not working
« on: February 19, 2016, 12:00:58 PM »
Within the "stores" table, the store_id column is "AUTO_INCREMENT" so when I ran the SQL the specified value of "0" was ignored. Instead it incremented to 4.

I checked the table "settings", key "config_url" value and it matched my admin URL.

What should I try next?

I very much appreciate your time and assistance. This is an important feature to our business.

General Support / Re: "Act on Behalf" not working
« on: February 18, 2016, 03:29:33 PM »
i checked your admin and your case looks like:
 you created some additional store, some customers registered in it, and then this additional store was deleted, but assignment "customer-to-store" still present.
Can you please check you database table "customers", column "store_id".
 value must be the same as in table "stores".

The "stores" table has no records.
The value for "store_id" within "customers" table is 0 for all records.

If I were to create a record for the "stores" table, the store_id column is "AUTO_INCREMENT" so I don't know if I can enter the value of "0" what value is needed for the "alias" and "status" columns?

I tested the above, by using "status=1", but it did not fix the "Act on Behalf" issue.

General Support / Re: "Act on Behalf" not working
« on: February 17, 2016, 03:12:08 PM »
Yes. Thank you for responding! How do you suggest I do that? Do you want me to create you an admin account?

General Support / Re: upgrade to 1.2.4 SQL update issue
« on: February 07, 2016, 03:23:00 PM »
Thank you! Yes, that worked.

General Support / "Act on Behalf" not working
« on: February 07, 2016, 03:22:31 PM »
Our current AbanteCart version is 1.2.5. The feature "act on half" doesn't not work when using HTTPS.
We only have one store.

This is the behavior: when Act on Behalf button is clicked, red popup message appears
"To act on behalf of customer in additional store you should to login into another store's admin side. Continue?"
Clicked Yes.
Login page is displayed with this URL
I entered correct credentials, but error:
"Invalid token session. Please login again."

This issues was reported as a bug and logged a while back, but even after upgrading, the issue continues for our site.
What should I try?  Thank you for your kind assistance.

General Support / Re: upgrade to 1.2.4 SQL update issue
« on: February 05, 2016, 03:59:43 PM »
Thank you, abolabo! I checked again.

Records within ab_order_status_ids match your example. However, error message continues to repeat. The error message also refers to the ab_order_statuses table which doesn't match your example, and is missing the last record. Should I add 'canceled_by_customer' as #14 to the ab_order_statuses table?

Attached is the screen shot of records within order_status_ids table.

General Support / upgrade to 1.2.4 SQL update issue
« on: February 05, 2016, 12:47:54 AM »
After upgrading to 1.2.4 (on my way to 1.2.5), this warning message is displayed
Incorrect status text id for order status #14. Value must be "canceled_by_customer" (). Please check data of tables ab_order_status_ids and ab_order_statuses

I have checked the tables ab_order_status_ids and ab_order_statuses and noticed that the later didn't have the record for "canceled by customer" which I then added. Cleared cache in both places, but no joy.

Should I fix prior to upgrading to 1.2.5? How do I fix?

Thank you kindly.

General Support / Re: database error when upgrading from 1.2.2 to 1.2.3
« on: February 04, 2016, 06:19:26 PM »
You should to check your system/config.php. contsnt DB_DRIVER value.
Then look into core/database and check is this driver file present there.
for ex. your db-driver is 'mysql' seek mysql.php file
Thanks. Yes, the DB driver is present. Still no luck with admin auto update. I did get manual upgrade to work on another site thanks to  your tip, because it helped me discover that the config.php file was empty.

General Support / database error when upgrading from 1.2.2 to 1.2.3
« on: February 04, 2016, 02:26:26 AM »
On a test system, I've attempted to upgrade from 1.2.2 to 1.2.3. I first tried the admin auto upgrade, but received this error:

2016-02-03 18:18:12 - database error: AbanteCart core v.1.2.2 Error:
SELECT dataset_id
FROM ab_datasets
WHERE dataset_name = 'install_upgrade_history'
AND dataset_key='admin' LIMIT 1 in <b>/home/xxxxx/public_html/test/core/database/amysqli.php</b> on line <b>105</b>

I did a backup and attempted manual upgrade. I had host check the permissions on directories and files. I confirmed PHP version.

Files copy fine. Run of upgrade.sql goes fine. The thing the documentation doesn't mention is the step after running the sql.
For me, I navigate to the AbanteCart dashboard, and it displays an install page:
I walk through the steps entering database name, etc. It is able to make the database connection, yet fails on step 4. Data Load.
Error message on screen is not helpful. (see attached).

I've reviewed documentation and exhausted all search paths.

Please help. 

Error Log says:
2016-02-03 18:18:12 - database error:  AbanteCart core v.1.2.2 Error: <br />SELECT dataset_id
                                FROM ab_datasets
                                WHERE dataset_name = 'install_upgrade_history'
                                    AND dataset_key='admin' LIMIT 1 in <b>/home/xxx/public_html/test/core/database/amysqli.php</b> on line <b>105</b>

2016-02-04 6:04:53 - database error:  AbanteCart core v.1.2 Error: Could not load database file ! in <b>/home/xxx/public_html/test/core/lib/db.php</b> on line <b>45</b>

Thank you in advance for any tips/solutions.

Pages: [1] 2 3 ... 6

Powered by SMFPacks Social Login Mod