Suddenly home redirects to settings#/subscription

And even more annoying as I just found out, it only affects existing users that I imported. New users are not affected. So it definitely has something to do with the MySQL import.

How did you "import" it. What did you modify? All we can really do is guess without seeing/knowing exactly what you did.

Well, I exported the users table in MySql and re-imported it after I did a migrate:refresh. So at first everything seemed fine with respect to users logging in but I just found out about this new "feature"...

To be precise, I used MySQL workbench to navigate through my database. This tool has an export/import table option.

Are they able to login successfully, but it just sends them to the subscription page once they do?

What did you modify? Do the users still have an active subscription?

Hi Cronix, yes they are able to login successfully and all other pages work but as soon as they go to the /home route, they are reroutes to the settings/subscription page. I think the subscription has changed but can't figure it out where to locate it in the database?

In either subscriptions or team_subscriptions, depending on if teambilling is implemented.

Yes, I've checked those. Both tables are completely empty. I actually had one subscription for one user (myself) and the other user didn't. However, both users experienced the same problem (redirecting to settings/subscriptions).

I did some database tweaking`, migrated it and manually imported the user table together with some other tables.

Ok, so what did you change then? If you changed some things, and it broke, we kind of need to know what you changed.

Well, I have some other tables in which I stored some identifiers in every row. I changed the column date field so that it could hold much more data. So now all identifiers that were stored in single rows are now stored in a single row. To get this implemented, I did a migrate:refresh and after that I specifically imported the users table to have the convenience of having the logins back.

btw I appreciate your time Cronix, i don't think it's an easy thing. So if we can't figure I'll do a complete migrate:refresh and have my test user redo their things.

I've found it! The trial_ends_at date entry somehow was messed up. When I copy pasted another entry everything was right again. Cronix thanks for helping out.