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

fix: Expense cannot accept credit card as payment account #654

Merged
merged 1 commit into from
Sep 3, 2024

Conversation

abouolia
Copy link
Contributor

@abouolia abouolia commented Sep 3, 2024

No description provided.

@abouolia abouolia merged commit 0c6f23e into develop Sep 3, 2024
1 check failed
@abouolia abouolia deleted the expense-credit-card branch September 3, 2024 10:23
@sbsroc
Copy link

sbsroc commented Sep 20, 2024

Thank you for working on this. For some reason my credit card is not in the payment dropdown yet, and I just pulled the new version down. I performed a hard browser refresh - Shift F5, added a new Credit Card account. Neither the old nor the new show as a dropdown option.
The release notes say that this was included 2 weeks ago. Did I do something wrong?
Thanks!

@abouolia
Copy link
Contributor Author

When you created Credit Card account from accounts chart, did you select Credit Card as a type for the account? Or you created the account from another place. @sbsroc

@sbsroc
Copy link

sbsroc commented Sep 20, 2024

When you created Credit Card account from accounts chart, did you select Credit Card as a type for the account? Or you created the account from another place. @sbsroc

Yes, both have "Credit Card" as the account type. I have "Chase Ink" and "Test" in the list.

I'm pretty sure I updated. How do I tell which version of Bigcapital I'm running? Is it in the UI somewhere?

@abouolia
Copy link
Contributor Author

abouolia commented Sep 20, 2024

weird, unfortunately showing the current version something would like to do, you can follow the upgrade guide, when you do docker compose pull if it pulled new images that means your current images are not up-to-date. https://docs.bigcapital.app/deployment/docker#upgrading

@sbsroc
Copy link

sbsroc commented Sep 20, 2024

I wrote a script to update it. It has almost no checks in it, but it works for me so far:

#!/bin/bash
cd /opt/bigcapital/
[ -f docker-compose.prod.yml ] || exit
docker-compose --file docker-compose.prod.yml stop
docker-compose --file docker-compose.prod.yml pull
docker-compose --file docker-compose.prod.yml up --build -d

@sbsroc
Copy link

sbsroc commented Sep 20, 2024

I ran it again.
"docker ps" says that the Bigcapital containers were created 2 days ago.
I run watchtower on this LXC and it fails to update Bigcapital, so I do it manually. It's possible something is wrong with my image, but I'm not very skilled with docker (new to it this year). if I could remove the image and re-create it without losing my data, I'm all for it. The mysql container holds all data I presume so if I destroy all else and re-run pull and build, would that work?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants