Trying to login to Magento 2 dashboard but get stuck on “It’s Time To Change Your Password” page

Just another little treat thrown at us today. I tried to login and got stuck on the It’s time to update your password page. I updated my password, logged out, cleared cache, cleared cookies, logged back in, tried changing the password again. Blah! Still stuck on that darned page.

This problem is documented in the magento2 github repository of course but none of the suggested fixes helped me. I’m special that way!

So I couldn’t get into the dashboard. But I could get into phpmyadmin and because this was the dev Magento site I felt real relaxed about poking at the tables.

Hold up! If you have the same issue and you Googled it right you’d land here and if you are really lucky one of the suggested fixes will help you fix it. But if they do not help you and you are stuck on the It’s time to update your password page, try  what I did.

Login to phpmyadmin or whatever db tool you use. Locate the admin_users table and note your user_id number. Then go to the “admin_passwords” table. You will see there is a row for Expires. That seemed suspiciously like a place I could extend the expiration of my password. For some reason each user_id has 2 password_ids. Don’t ask me why.

What we want to do here is edit the number under Expires.

My Expires number was something like 1569633535. I changed it to 1969633535 for both of the password_ids that were listed for my user_id. I could then login and go to other places in the Magento admin.

Hope this helps.


Magento Scares Us, Like Daily


For ages I was able to avoid the nightmare that is Magento because I was focussed entirely on freelance jobs working with LightSpeed Webstore.

Once in awhile someone would try to ruin my life with a Magento project (usually fixing something that had worked then “mysteriously” just broke) but I had so much LightSpeed Webstore stuff going I could just say no, thanks.

Irony is now I provide support to a folks running Magento stores. Ha Ha! It’s what I do from 10 am to 6pm. Every day. And when I got started I knew only that Magento was a beast like creature of terrible proportions and that it would make me cry. Because it breaks like all the time. I was totally spoiled by other eCommerce shop platforms because they don’t break nearly as easily. I still have a site with an online store built with a really old version of WordPress e-Commerce plugin. It’s so old it should be on life support. But it’s fine. We keep everything else updated, of course. But even applying the latest version of WordPress doesn’t break the store. See? Spoiled.

Magento releases patches that break stuff. All the time. That’s why I have a job. I shouldn’t complain. Except I have to because I’m alive.



Why is they always problems?

Why is they always problems, jQuery?
Why is they always problems!!!!$#%!?

So I was minding my own business peacefully putting together this little website. Nothing all that complicated even to me even though I hadn’t built a site in a while.

Though there was this one feature powered by  waypoints.js  and jquery.counterup.js that kept going wrong.

We had this little bit of animation in place to make 2 sets of numbers count up to the actual stats we wanted to display. The counter action should trigger whenever the div was in view: by scrolling down the page to the stats div, the numbers should start “counting up” and then stop on the right number. And it should fire more than once. Go back to the top and scroll down again no matter how many times the numbers should count and stop on the right numbers. It worked OK until around the 5th or 6th time you scrolled down. Then line 62 of jquery.counterup.js would throw an error: Uncaught TypeError: Cannot read property ‘shift’ of null. Stats would still animate but the final numbers would be the wrong ones.

CounterUp is in GitHub and I tried digsite’s fork . This fork fixes the problem when jquery.counterup.js is used with the more current versions of waypoints.js. But then it only allows the stats animation to trigger once. We wanted it to be triggered any time the stats div came into view. Then I want back to the original and found this issue: which was fixed around a week ago – just when I needed to wrap up my little web project! A web miracle! The same error (Uncaught TypeError: Cannot read property ‘shift’ of null) is logged in Console but the stats numbers stay correct each time the animation is triggered and then stops, thanks to the fix by

Which LightSpeed Point of Sale Will Work Best For Your Next Endeavor into eCommerce: LightSpeed OnSite or LightSpeed Retail?


The title is a bit of a trick question really.

Because by the time most folks go looking for advice or help with an eCommerce site, they’ve already got one. They’ve also usually already bought (or signed up for) a Point of Sale System. Problem with this way of going about it is, by the time they need help they’re locked into one system or another, having often invested a serious amount of cash.

Whether the $$$$ was allocated for an eCommerce site or the latest cutting edge Cloud Point of Sale system – they’re hardly ready to do a 360 degree turn and start from scratch with something else based on my ramblings (though some might call them findings based on solid empirical data!).

Hardly anyone I’ve worked for has ever made a choice of a Point of Sale based on how it’s going to work out for the eCommerce site they have always wanted.
Why would it matter to the eCommerce site which POS you buy? For the reason that most POS systems do not synchronize your brick and mortar sales with your eCommerce site sales.

Possible headache:

2 stores, 2 inventories that are unconnected. One store is the eCommerce site with manually updated inventory and the other is the brick and mortar inventory updated by walk-in sales. So a customer buys a product in the brick and mortar – the eCommerce store is essentially clueless until someone logs in and updates stock manually. Not such a huge nightmare for small shops with slow sales. But I’ve known a few people who would groan very loudly if they ever had to do anything manually. But what if you have an eCommerce site with lots of daily transactions as well as lots of in-store sales? Pretty soon you’d be burned out having to manually update the eCommerce stock counts (to match inventory to real life).

Which is why when (around 10 years ago) when LightSpeed for Mac came on the scene some people got real, real excited. Because, from the beginning, one of LightSpeed’s major claims to fame was if you had its eCommerce connector from its POS to its web store, brick and mortar inventory synced with web store sales and vice versa – the inventory pool was one and the same!

Because I know you’ve already read this short post on the difference between LightSpeed Retail and LightSpeed OnSite and you know what eCommerce means
(e = electronic. Commerce = providing goods and services in exchange for money – you add products to your website, people buy them, repeat).

Now let’s get one thing straight. If we can’t get anything but this one thing straight we are still ahead of the game: LightSpeed is first and foremost a Point of Sale system. It is not an eCommerce solution. An eCommerce solution is a package of software that makes up and runs an online store. An online store is only as good as the software that powers it. Yes, LightSpeed has built an eCommerce solution named LightSpeed Web Store which we will discuss in more detail in a later post. But please let’s just make it clear in our minds that LightSpeed’s main focus is providing Point of Sale solutions.

Low cost! Easy to setup! No programming required! It practically runs itself! – a sales rep, lying to you.

So, back to “Which LightSpeed Point of Sale Will Work Best For Your Next Endeavor into eCommerce: LightSpeed OnSite or LightSpeed Retail?”. Let’s first assume you know that you don’t need a Point of Sale system if you don’t have a brick and mortar store.

These are many of the points people have to consider when choosing between the 2 kinds of LightSpeed Point of Sale systems. It’s called real life.

  • Limited Budget
  • Limited Time
  • Steep Learning Curve
  • Employee Knowledge Skills

Do you have a small budget? Do you have only yourself to rely on to learn all the steps and processes for getting setup with LightSpeed? In other words, how much work are you willing to do and do you have to do it all by yourself?

Low upfront cost and not having that much time are the main reasons people choose LightSpeed Retail. And they are naturally attracted to the fact that when they sign up for it they can add the LightSpeed Web Store to the monthly charges for 51.00 USD.
Yeah, yeah, yeah: so what if low prices are based on whether or not you agree to pay 14 months upfront?

What people don’t know is the fact that with LightSpeed Retail + LightSpeed Web Store you have to love one of the approved themes that can be downloaded from the Theme Gallery in the LightSpeed Admin Panel – you might have to learn to love them because in an out of the box situation without any 3rd party solutions (whose services cost money), you’re stuck.

Here’s something not that many people know:
With LightSpeed Retail + LightSpeed Web Store the Web Store theme is not accessible with an FTP program or Control Panel/File Manager. You can make changes, like font colors or how big the type is, using the CSS editor in the Admin Panel. CSS controls how content looks.

Just having access to the Web Store theme CSS is not nearly enough access to be able to extend the Web Store content, not to mention it makes theme development impossible.

Unfortunately, having a small budget and limited time can sometimes mean learning to love what you get with the deal you made.

If you have Mac computers and a somewhat larger budget and would really like to have a custom Web Store think about LightSpeed OnSite also known as Lightspeed for Mac.

Tiny Little Update

Here is a great review of LightSpeed Retail. I don’t think the reviewers are biased toward either type of POS. It’s just a very well put together article that really breaks things down well. The article was first written in 2013 but was updated on Sept. 2015. Read the comments as well. Nothing like feedback from actual users!