Something similar was taking place in drupal 7.
I have hook_views_query_alter in MODULENAME.views.inc file in the same folder as module file. I found out, that query handler is class views_plugin_query_default. Within that class:
function alter(&$view) {//dpm($view); foreach (module_implements('views_query_alter') as $module) {//dpm($module); $function = $module . '_views_query_alter'; $function($view, $this); } }
Is called, but can't find any module that implements hook...
Of course I cleared all the caches, even truncated tables cache_views and cache_views_data, all in vain.
AFAIR in drupal 7 similar problem solved itself automagically after some time, and hook_views_query_alter started to work. So maybe there is something else cached somewhere? Maybe .inc file is not being seen by backdrop? Access rights are as usual...
Recent comments
After alot of trials, i have done the obvious and translated the whole block for different languages with each property condition as follows: ->propertyCondition('langcode', 'en...
How to get the current page language?
Thanks so much! It's working now: I was able to transfer the docroot files to the containing directory without the need for a second database or any manual configuration export/import/sync...
Backup & Migrate Config: There was a problem creating field...database table with the name already exists.
Ah, I see. Sorry, I hadn't clicked the link and assumed it was the instructions for upgrading from Drupal 7. If you are simply copying a site from one location on a server to another, the...
Backup & Migrate Config: There was a problem creating field...database table with the name already exists.
Thanks for the quick reply, laryn. No features, no Drupal: I built the source site in Backdrop in a subdirectory of the target directory under the same user home directory on the same...
Backup & Migrate Config: There was a problem creating field...database table with the name already exists.
This doesn't sound right -- when the upgrade completed, did you export the post-upgrade configuration into the staging folder (and commit that to the repo if you are using a git-based workflow...
Backup & Migrate Config: There was a problem creating field...database table with the name already exists.