Project60 / Project60/org.project60.banking
Unable to re-analyse or even delete transactions analysed with missing plugins
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 22
- Forks
- 45
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 7
Description
When a transaction has already been analysed using a matcher plugin that no longer exists (got deleted), the transaction can neither be re-analysed with the current plugin configuration nor can it be deleted. Also, the whole statement containing the transaction can not be deleted anymore.
The associated error being thrown is Expected one OptionValue but found 25 when querying plugin instances with
civicrm_api( 'OptionValue','getsingle', array(
'version' => 3,
'id' => $classNameId)
);
in \CRM_Banking_BAO_PluginInstance::getClass() where $classNameId is null.
This state can only be resolved by getting back the previously deleted plugins (with the correct IDs) or deleting transactions and/or statements from the database manually.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with CRM_Banking_BAO_PluginInstance::getClass() and the shown civicrm_api OptionValue getsingle call, then trace how missing matcher plugins are handled during transaction and statement re-analysis or deletion. Reproduce the missing-plugin state and follow the transaction and statement deletion paths; done means these operations no longer fail with “Expected one OptionValue but found 25”.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100