I too faced it and I think it’s a bug in Keras. Anyway, I have updated the article to explicitly specify the steps which it should have automatically got in the first place.
UPDATE: Looks like using keras_preprocesing instead of keras.preprocessing throws this error due to updates that keras_preprocessing received. explicitly set steps for now.