Is it possible to 'hook' into the accounts database? I would like to do so in order to add functionality associated with the login, such as a wish list and tracking information associated with orders, and be able to avoid 2 logins required for built-in account functionality and custom account functionality and also maintain any functionality related to the built-in accounts system (such as checkout information being pre-loaded?). Has anyone been able to do this?
If that is not possible, has anyone built their own accounts area/functions? What are the pitfalls you experienced?
As to why I would go through all the trouble - I really would prefer to not leave shopsite after almost 9 years of success using this software.
Thank you,
David
Any way of hooking into accounts database
There is no direct access to the registered user accounts in the Shopsite database. There is encrypted data used in that (and payment) parts of the data base and there is no method provided to decrypt the data, so even if you could access it might not be helpful.
The database is an sqlite database, ShopSite provides no external interface to the database or description of the structure but there are other tools that you could find that might help you access it. However, if you do so you are on your own and ShopSite accepts not liability and will provide no support for it.
The database is an sqlite database, ShopSite provides no external interface to the database or description of the structure but there are other tools that you could find that might help you access it. However, if you do so you are on your own and ShopSite accepts not liability and will provide no support for it.
Thank you for the reply. I appreciate the heads up on being on my own and not providing support for direct database access.
Maybe this should go into the requested changes forum, but an adequate hook for me would be a way of checking if the customer is logged in and at the same time provide a unique identifier that stays with that log-in. Nothing like that exists I presume? any sort of work arounds you can think of? I am thinking from your note that the database will not help since the login is probably secured with encryption.
thank you,
David
Maybe this should go into the requested changes forum, but an adequate hook for me would be a way of checking if the customer is logged in and at the same time provide a unique identifier that stays with that log-in. Nothing like that exists I presume? any sort of work arounds you can think of? I am thinking from your note that the database will not help since the login is probably secured with encryption.
thank you,
David