The bottom line is this. Block settings persist with the account, not in the browser or in a cookie.
I proved how the block settings persist by taking the following steps.
- I opened browser a on machine a and logged into a test account
- I opened browser b on machine b and logged into the same test account.
- I added some blocks while logged into machine b
- I refreshed machine a and saw the changes I had just made
- I then made some changes in machine a, then refreshed machine b and saw those changes.
- The final check I made was to log off both accounts on machine a and b. Then logged into the same account from machine c and saw the most recent changes as I would expect.
Clearly the changes to the blocks are stored in the DB and associated with the user account.
The end.
No comments:
Post a Comment