Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migration issue #33

Closed
Pegasuz opened this issue Dec 7, 2014 · 6 comments
Closed

Migration issue #33

Pegasuz opened this issue Dec 7, 2014 · 6 comments

Comments

@Pegasuz
Copy link

Pegasuz commented Dec 7, 2014

I've just migrated from the last tag and I get the following error when I browse to the dashboard:

production.ERROR: exception 'InvalidArgumentException' with message 'View [transactions.journals-small-index] not found

I've run the migrate command, flushed the cache and dump-autoloader.
But nothing helps.

@JC5
Copy link
Member

JC5 commented Dec 7, 2014

That shouldn't happen. Plenty of problems in the latest release but that one should not have happened. The view has disappeared indeed but also, it's not referenced to anymore. Have you changed any files maybe?

@Pegasuz
Copy link
Author

Pegasuz commented Dec 8, 2014

I've reset my repo and did a reinstall of composer dependencies.
Now I get

production.ERROR: exception 'Symfony\Component\Debug\Exception\FatalErrorException' with message 'Class 'Filter' not found'

@JC5
Copy link
Member

JC5 commented Dec 8, 2014

Alright I can see what the problem probably is but it's going to be a huge pain to fix it manually. It's entirely my fault, I've messed up the migrations which made upgrading / updating very difficult. What's more, the installation instructions fail to take this into account.

Your best bet right now is to create a second Firefly III installation using these instructions:

https://github.com/JC5/firefly-iii/wiki/Installation

Then, using a tool like PHPMyAdmin or Sequel Pro or others, compare the database schemes and adjust where necessary. Your second Firefly installation will only have the tables you need, but you don't need to delete any tables if you feel uncomfortable.

Then, edit the second's Firefly installation to use the first database. That should fix things.

I know this sucks, but it's the best I can do.

@Pegasuz
Copy link
Author

Pegasuz commented Dec 9, 2014

Alright.... I will try this tonight. Thanks anyway!

@Pegasuz
Copy link
Author

Pegasuz commented Dec 16, 2014

I've synced both the database to the new schema, but I still get this error.
Can you help me?

@JC5
Copy link
Member

JC5 commented Dec 17, 2014

Of course!

There should be log files in firefly-iii/app/storage/logs. Could you find the latest one (they're grouped by date) and copy the last ~60 lines?

@JC5 JC5 closed this as completed Jan 2, 2015
@lock lock bot locked as resolved and limited conversation to collaborators Jan 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants