Hi.
We are currently on a trial version. As explained before, i don't wish to use much of the front end at all and mainly want to use payment / admin along with some customised product displays that i will use in flash.
I am finding the API documentation very hard work as a great deal of it has been generated and has little, and sometimes no explanation of what a method / property / class actually does. Is there any other documentation for developers who wish to use the API? I am pretty confident that the code is good but i am finding it very difficult to do anything as there seems to be such little developer support for the product.
Thanks
Dave
Developer Documentation - Future plans for more?
- Shopping Cart Admin
- AbleCommerce Admin
- Posts: 3055
- Joined: Mon Dec 01, 2003 8:41 pm
- Location: Vancouver, WA
- Contact:
Re: Developer Documentation - Future plans for more?
Hello Dave,
The AbleCommerce wiki will contain the developer documentation as it becomes available. Now that we've gone final you'll find more and more being added. Given the helpful replies in our forums and our developers being active in our forums, I don't really think there is 'little developer support' for AbleCommerce. .
http://wiki.ablecommerce.com/
The AbleCommerce wiki will contain the developer documentation as it becomes available. Now that we've gone final you'll find more and more being added. Given the helpful replies in our forums and our developers being active in our forums, I don't really think there is 'little developer support' for AbleCommerce. .
http://wiki.ablecommerce.com/
Re: Developer Documentation - Future plans for more?
Hi Mike.
Please don't misunderstand me. The forums are helpful but seem to focus on questions relating to the controls and themes (which is entirely understandable).
I have looked at the wiki already and found the DAL example helpful but i wish there was more!
A good example of a query i have this minute is to do with Token.Instance.User.UserId and how this is generated and stored for future use when IsAnonymous is true. When i look up UserID in the chm file i simply get:
If there was a short description along with it explaining about how these are generated when a user is anonymous it would be a great help.
As i mentioned in my first post, the codebase seems great and i look forward to seeing more examples soon.
Dave
Please don't misunderstand me. The forums are helpful but seem to focus on questions relating to the controls and themes (which is entirely understandable).
I have looked at the wiki already and found the DAL example helpful but i wish there was more!
A good example of a query i have this minute is to do with Token.Instance.User.UserId and how this is generated and stored for future use when IsAnonymous is true. When i look up UserID in the chm file i simply get:
Code: Select all
public:
property int UserId {
int get ();
void set (int value);
}
If there was a short description along with it explaining about how these are generated when a user is anonymous it would be a great help.
As i mentioned in my first post, the codebase seems great and i look forward to seeing more examples soon.
Dave
Re: Developer Documentation - Future plans for more?
Hello Dave,
The Anonymous user is also a user in the Database table.... just with one difference : It has 'IsAnonymous' property true.
The ID for the anonymous user is also just an ID of its corresponding record in database.
Thanks,
Sohaib
The Anonymous user is also a user in the Database table.... just with one difference : It has 'IsAnonymous' property true.
The ID for the anonymous user is also just an ID of its corresponding record in database.
Thanks,
Sohaib
Re: Developer Documentation - Future plans for more?
Hi Sohaib.sohaib wrote:Hello Dave,
The Anonymous user is also a user in the Database table.... just with one difference : It has 'IsAnonymous' property true.
The ID for the anonymous user is also just an ID of its corresponding record in database.
Thanks,
Sohaib
Thanks for your response. I presume this information is stored on the client machine in a cookie for a finite amount of time until the user signs up or logs in?
Re: Developer Documentation - Future plans for more?
By default forms authentication timeout in ASPNET 2 is 30 minutes. Unless you change this in your web.config 30 minutes is what the session is active for. The user information is not necessarily stored in client cookie. The cookie may only include a session identifier. Session state information is maintained on the server. A session cookie may not necessarily expire for a session to be considered expired. Unless cookies are specifically set to be persisted for a longer duration, by default they are removed when the browser window is closed.
Re: Developer Documentation - Future plans for more?
Hey again.sohaib wrote:By default forms authentication timeout in ASPNET 2 is 30 minutes. Unless you change this in your web.config 30 minutes is what the session is active for. The user information is not necessarily stored in client cookie. The cookie may only include a session identifier. Session state information is maintained on the server. A session cookie may not necessarily expire for a session to be considered expired. Unless cookies are specifically set to be persisted for a longer duration, by default they are removed when the browser window is closed.
Possibly my question was a little vague. What i meant was, how is the anonymous UserID persisted between visits?
I can close the browser and come back and i still have the items in my basket. I wanted to know how to access this information programmability and how long is this information stored in the database? Are baskets purged that never see it through to an order?
Dave