Undefined index in theme subsystem on view order page [#1206788]

Notice: Undefined index: theme path in theme() (line 802 of /home/webuildl/public_html/make/includes/theme.inc).
Notice: Undefined index: render element in theme() (line 824 of /home/webuildl/public_html/make/includes/theme.inc).
Notice: Undefined index: type in theme() (line 905 of /home/webuildl/public_html/make/includes/theme.inc).
Notice: Undefined index: template in theme() (line 933 of /home/webuildl/public_html/make/includes/theme.inc).
Warning: include(/home/webuildl/public_html/make/.tpl.php) [function.include]: failed to open stream: No such file or directory in theme_render_template() (line 1247 of /home/webuildl/public_html/make/includes/theme.inc).
Warning: include() [function.include]: Failed opening '/home/webuildl/public_html/make/.tpl.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in theme_render_template() (line 1247 of /home/webuildl/public_html/make/includes/theme.inc).

/admin/commerce/orders/4/view

Not sure how to hunt this one down :/

Comments

Comment #1

gagoo CreditAttribution: gagoo commented 7 July 2011 at 09:03

Comment #2

rszrama CreditAttribution: rszrama commented 7 July 2011 at 15:28

Status:

Active

» Closed (cannot reproduce)

I'm not seeing any problems, and my hunch is this might have just been mitigated by patches we just committed last night to centralize all of our entities' view / build_content functions through the default Commerce entity controller. Go ahead and update to the latest dev of Commerce (and be sure to clear your cache afterward) and see if the problems persist. If so, I'm going to need to know more about how to reproduce the bugs (versions of Drupal / modules, contributed modules you may have installed, etc.).

Comment #3

gagoo CreditAttribution: gagoo commented 7 July 2011 at 16:29

OK,
For my case I solve the problem.

This issue is due to a little bug with the Display Suite module (latest recommended version) when trying to display an order review page (ex : admin/commerce/orders/30 ).
When I disable this module, there is no issue anymore.
And the solution I found to continue to use the Display Suite module in my site is to define a Display Suite layout in the order display settings ( at admin/commerce/config/order/display ).
By default there is no Display Suite layout defined, I just choose the "one column" layout that don't change the default drupal display.
That way the error message disappears.
But it would be better if there was no need to make this configuration by default, just like any other entities that works fine with Display Suite.
I don't know if it is a Drupal Commerce bug or a Display Suite one, but the solution is here !

Thanks

Comment #4

rszrama CreditAttribution: rszrama commented 7 July 2011 at 16:30

Ahh, great, thanks for the extra information. : )

Comment #5

PI_Ron CreditAttribution: PI_Ron commented 29 July 2011 at 02:28

Thanks alot for that, got rid of a few errors for me.

Comment #6

iAugur CreditAttribution: iAugur commented 15 August 2011 at 12:26

That saved me some time too - thanks!
Once you do that the order display fields (Line Items, order total, Shipping, billing, etc) will be disabled and you must go and configure the display to place them in the content region - Otherwise your order screen will be blank.