i've written a views backend plugin ('null')
it does not need own fields.

all perfect, but a minor cosmetic issue:
when creating a new "null" view, a default field is added saying:

Broken/missing handler (Broken handler null.table)

export snippet:

/* Field: Broken/missing handler */
$handler->display->display_options['fields']['table']['id'] = 'table';
$handler->display->display_options['fields']['table']['table'] = 'null';
$handler->display->display_options['fields']['table']['field'] = 'table';

(this is not too ugly as we always can delete that field)
where the hell gets this added and how can i override this?

adv-thanx-ance!

CommentFileSizeAuthor
#1 1485910.patch817 bytesdawehner

Comments

dawehner’s picture

dawehner
Primary language German
commented
Status: Active » Needs review
StatusFileSize
new 1485910.patch817 bytes

Wow someone is writing query backends, this is interesting, what is the purpose of the module?
Is this module available somewhere?

The field is added on the wizard, just for the purpose of better user experience. For example this allow users to save the view without the need to add a field.

Here is a patch which should fix the problem.

tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
commented
Status: Needs review » Needs work 
+++ b/plugins/views_wizard/views_ui_base_views_wizard.class.phpundefined
@@ -636,11 +636,15 @@ class ViewsUiBaseViewsWizard implements ViewsWizardInterface {
+    // Maybe some query backends doesn't have fields.

s/doesn't/don't

+++ b/plugins/views_wizard/views_ui_base_views_wizard.class.phpundefined
@@ -636,11 +636,15 @@ class ViewsUiBaseViewsWizard implements ViewsWizardInterface {
+    if ($field) {

Might as well use isset(), right?

geek-merlin’s picture

geek-merlin
Primary language German
Location Freiburg, Germany
commented

(busy but will look into this!)

kars-t’s picture

kars-t commented
Status: Needs work » Fixed

Dear fellow Drupal enthusiasts,

this issue is now lasting for a very long time in the issue queue and was unfortunately never solved. As Drupal is a open source project everyone is helping on voluntary basis. So that this is was not solved is nothing personal and means no harm. But perhaps no one had time to deal with this issue, maybe it is too complex or did not describe the problem comprehensibly.

But this issue is not the only one. There are thousands of issues on Drupal.org that have never been worked on or could not be processed. This means that we are building a wave that is unmanageable and just a problem for the Drupal project as a whole. Please help us keep the issue queue smaller and more manageable.

Please read again, "Making an issue report" and see if you can improve the issue. Test the problem with the current Core and modules. Maybe the problem doesn't exist anymore, is a duplicate or has even been solved within this issue but never closed.

Help can also be found for it on IRC and in the user groups.

In order to remove this issue, I have set this issue to "fixed".

If there is new information, please re-open the issue.

--
This issue was edited with the help of Issue Helper

tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
commented
Status: Fixed » Closed (won't fix)

This is not fixed. Please feel free to reopen if you can respond to my comment.