View Issue Details

IDProjectCategoryView StatusLast Update
0000924OXID eShop (all versions)1. ----- eShop frontend -----public2012-12-10 14:37
Reporterhairpoint_de Assigned To 
PriorityhighSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Version4.1.2 revision 18998 
Fixed in Version4.1.3 revision 19918 
Summary0000924: Class Order_account drops error
DescriptionHi,

When calling class account_order, it fails with:

"Function 'getStatus' does not exist or is not accessible! (oxOrderArticle)"

please confirm, than you
TagsNo tags attached.
Theme
BrowserAll
PHP Version5.2.6
Database Version5.0.33

Activities

arvydas_vapsva

2009-05-22 16:56

reporter   ~0000941

Reminder sent to: hairpoint_de

what oxid version do you use? this method is only available in EE and in default installation it should work, as there is such method in oxorderarticle class. If you use EE maybe someone applied PE/CE version patch?

hairpoint_de

2009-05-22 18:15

reporter   ~0000942

Hi,
at first, sry for the sloppy report - was in a hurry..

We use the PE (4.1.2_18998), the error occures after clicking the 'Order History' Link on the 'My Account' Page. But I just checked the Demo Shop - works fine there. So I guess the problem is caused by one of our modules.

thank you anyway

arvydas_vapsva

2009-05-25 13:37

reporter   ~0000944

while debuging i found another problem - if product, which was ordered once, does not exist any more or is inactive - you get error on same view. Fix applied on oxarticlelist::loadOrderArticles() method:

    $sArticleFields = $oBaseObject->getSelectFields();

  to:

    $sArticleFields = str_replace( "$sArticleTable.oxid", "oxorderarticles.oxartid as oxid", $sArticleFields );

  plus at the end of function added check:

    // not active or not available products must not have button "tobasket"
    foreach ( $this as $oArticle ) {
        if ( !$oArticle->oxarticles__oxactive->value ) {
            $oArticle->setBuyableState( false );
        }
    }

arvydas_vapsva

2009-05-25 13:38

reporter   ~0000945

user defined bug does not exist, but fixed another one, which were found trying to reproduce problem.