well @herb I cannot believe it, but the webform module was there in modules on the disc, but missing in the listed modules, so I delete the module folder, and downloaded it again.
Then...
Posted1 week 5 days ago by Francis Greaves (themetman) on:
The only thing I can think of is to make sure Webform module is enabled and that the content type that needs to contain the webforms has Webform enabled for it. Edit the content type and make...
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Posted2 weeks 4 days ago by Francis Greaves (themetman) on:
Comments
This issue may be related (and it looks like it has a PR that can be tested):
https://github.com/backdrop/backdrop-issues/issues/2134
That PR wont be in production any time soon. But you could make a quick access condition module, its quite simple. Use as a guide: https://github.com/backdrop/backdrop/blob/1.x/core/modules/layout/plugins/access/path_layout_access.inc or https://github.com/backdrop-contrib/block_scheduler
Your form function would probably be something like:
$form['nid'] = array( '#type' => 'textfield', '#title' => t('Node NID'), '#default_value' => isset($this->settings['nid']) ? $this->settings['nid'] : '', ); $form['term'] = array( '#type' => 'textfield', '#title' => t('Term'), '#default_value' => isset($this->settings['term']) ? $this->settings['term'] : '', );And your access function:
function checkAccess() { $entity = $this->contexts[$this->entity_type]->data; return isset($entity->{$this->settings['term']}); }Some adjustment may be necessary.
As an easy workaround without any coding Views could be your friend.
We'd need some more info about your use-case though. Could you describe a bit more, please?