Once installed, enabled and used as a widget, the module generates an error every time you try to open its configuration from views. It is not possible to change or review its configuration.
Just try to open the configuration from Filter Criteria and look at the message on the browser screen (above) and the message issued by the console:
At the code level, it appears that a method is being called that is not defined from this call:
| Comment | File | Size | Author |
|---|---|---|---|
| hts-hts-issue-config-2.png | 93.23 KB | davidjguru | |
| hts-hts-issue-config.png | 171.46 KB | davidjguru |
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
davidjguruComment #4
cesarmsfelipe commentedMerged the feature into the main branch and created tag 1.0.2 for further testing.
Thanx @davidjguru.
Comment #5
davidjguruUpdating local installation to 1.0.2, the change is returning the error message:
TypeError: Drupal\hts\Plugin\views\filter\HtsTaxonomyIndexTid::__construct(): Argument #6 ($entity_repository) must be of type Drupal\Core\Entity\EntityRepositoryInterface, Drupal\Core\Session\AccountProxy given, called in /var/www/html/sot/web/modules/contrib/hts-hts/src/Plugin/views/filter/HtsTaxonomyIndexTid.php on line 83 en Drupal\hts\Plugin\views\filter\HtsTaxonomyIndexTid->__construct() (linea 74 de /var/www/html/sot/web/modules/contrib/hts-hts/src/Plugin/views/filter/HtsTaxonomyIndexTid.php).Because the order of the parameters in the constructor has been altered.
Comment #9
cesarmsfelipe commentedMerged the feature into the main branch and created tag 1.0.3 for further testing.
I know it's not good practice, we are treating this as a hotfix so next time it should be done in 1.0.x-dev version.
Comment #10
cesarmsfelipe commented