If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Originally posted by Gordon - Phosphor MediaView Post
I think that having an ability to message the person you're trying to boot is going to be essential.
"I need to get into the admin right now to start my shift."
"Hold on, I need 5 more minutes to make sure this template code actually works. Kick me out if I'm not done by then."
Live store, asked for support with StoreMan5. Their desktop version was out of sync with their admin connector module, so I thought I would go in and update it for them. Oops. They are running Merchant 9, only one admin login. But wait! The login manager shows that there are two logins active.
I send them email saying they need to 1. update their module, then 2. log out to run StoreMan5. I get a reply 15 minutes later that says the error is the same. I attempt to log back in, but once again I see there are two active logins already (even though it says there is 1 concurrent login possible).
An hour later I get an email:
'There was some kind of glitch in Miva or something. I finally got it to work.
I kept going in and clearing them out, plus logged out the current and I was getting the same error. When I just logged in it even showed you were still in. I'm sure you logged out.
The instances seemed to be cleared out now and it's working.
Very sorry for the hassle.'
I agree with Dan (“Glendale Designs), you should NEVER be kicked out of a session, it will cause major issues. If anything, it should be you cannot create a new session, until those who are logged in, release their position.
Why not make it so you never get booted or locked out. Simply treat the seats, the way a cell phone company handles data plan, it automatically bumps you up to the next tier level, and charges your account (it could be a credit card on file), basically an automatic charge for every extra seat. That puts the responsibility back on the store owner, and in the event your working one month, with web designers, graphic guys, programmers , whatever, and you can easily get the extra seats need. Most of us have either an account or credit card on file, which could easily be charge.. If the owner doesn’t have a payment method on file, too bad for them. they don’t get the seat.
To be honest, we have already mapped out the number of seats we need and have added few more so we would never be blocked in anyway. I do have one question that I have never seen on the forum, For example let assume website A, have 4 paid additional licenses, and one month, a 5th person logs in at the same time and they purchase a another seat. So that month, they have 5 paid additional seats, the next month, is my question; Does the account revert back to 4 additional paid seats, or will miva servers continue to charge 5 additional paid seats each month there after?.
I’m not complaining either way, Just trying to understand the rules, in order to play the game.
Why not make it so you never get booted or locked out. Simply treat the seats, the way a cell phone company handles data plan, it automatically bumps you up to the next tier level, and charges your account (it could be a credit card on file), basically an automatic charge for every extra seat. That puts the responsibility back on the store owner, and in the event your working one month, with web designers, graphic guys, programmers , whatever, and you can easily get the extra seats need. Most of us have either an account or credit card on file, which could easily be charge.. If the owner doesn’t have a payment method on file, too bad for them. they don’t get the seat.
This option scares me - I already have to deal with "whodonit" issues and I'm sure they would be a way to figure out who did but without some really clear cut acknowledgments that "you WILL be charged" before you click that button I'm afraid this option might cause as much fury as clicking the update button has.
Our initial goal was a system like you described where you just accept the fee and you're in, the logistics of our underlying billing system prevent that (for now).
We're also looking at protected accounts that can't be force logged out. The new Developer Accounts we're working on will have that feature.
The reason it's not this way by default is there are too many people who change their admin timeout to be longer than it should be and would inadvertently end up locked out until their timeout expired.
The reason it's not this way by default is there are too many people who change their admin timeout to be longer than it should be and would inadvertently end up locked out until their timeout expired.
Rick:
Specifically what is the admin timeout supposed to be, or in other words, how can someone tell if it is too long?
Gordon Currie Phosphor Media - "Your Success is our Business"
The reason it's not this way by default is there are too many people who change their admin timeout to be longer than it should be and would inadvertently end up locked out until their timeout expired.
Can you clarify what you mean by this? What effect would the Time Out setting have IF that account was logged out.
Comment