Tracking down some errant PHP complaints in dblog that are coming from quicktabs...

	Missing argument 3 for quicktabs_ajax_node() in /var/www/htdocs/prod-backup/sites/all/modules/quicktabs/quicktabs.module on line 231

I tracked this down to when quicktabs is called with a node, if "hide title" is not clicked then it will complain as above. If "hide title" is not clicked THEN if Teaser view is not clicked it will provide a similar complaint except that it is 'argument 2' that is missing instead of three.

Comments

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented
Status: Active » Postponed (maintainer needs more info)

repro steps:
1. install clean Drupal (6.x-dev)
2. enable Quick Tabs (6.x-2.0-rc3) module
3. create a node
4. create a quicktab
- ajax:yes
- tab 1: type: node; node id: 1; teaser view: true; hide title: false;
- tab 2: type: node; node id: 1; teaser view: false; hide title: false;
5. assign the qt block into region
6. test the quicktab with clicking on tabs

result: no php error displayed, the watchdog does not show any error

I will need repro steps which reproduce the bug, or need to know the environment where (and why) it creates an error..

Dave Kinchlea’s picture

Dave Kinchlea commented

Easier said than done I'm afraid, I was hoping that it was because I was displaying via a panel page, but I just tried it via a block and I have the same issue. All I need to do to reproduce the problem is toggle either of those settings for any QT node being loaded via AJAX... i even tried creating a new QT similar to the one you describe (except that I try all permutations). Using a new piece of content specifically for this testing, same result.

I have a very complex site with MANY modules, but there are no other complaints at this time. Can you offer any advice as how to narrow this down short of removing one module at a time? Perhaps there are some more obvious candidates than others? For instance, I can't see how any CCK modules could cause this behaviour, there are no CCK fields in the nodes used for QT nor on the pages where it is displayed ... can I then safely assume that CCK-based modules can be ignored? Would it make sense to concentrate on any AJAX-related modules?

Happy to share more information with you, just not sure what is relevant.

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented

one similar issue I can think of is the problem (in php?) with false and zero
if you have quicktabs created with php code then you might have to fix some values: #332895-26: render quicktab programatically
The issue might be related, and would be good if we could fix it.

Dave Kinchlea’s picture

Dave Kinchlea commented

I have very little custom mods / PHP in use, I can't swear right now that none of the QTs include any PHP-built content, but I can confirm that the problem happens with ordinary nodes with static content (and damn little of that). It may well be a FALSE != 0 issue, of course, but not by any programming I've done.

I do have many different content types in use, I think I have been consistently using only two in QT building, perhaps I'll try a few other content types to see if I can narrow it down that way ... but I'm already using pretty standard types (book pages) so I'm not overly optimistic given the problems show up in blocks as well as pages and are limited to ajax use.

I agree, it would be nice to fix it and I'm certainly willing to put in a valiant effort :-)

katbailey’s picture

katbailey commented
Version: 6.x-2.0-rc3 » 7.x-2.x-dev
pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

This issue is without response for more than a month, closing.

feel free to reopen if you can provide steps to reproduce this problem.