-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No method named getRunModel() in Job.php even though it is called in getCallback() #295
Comments
+1 Same issue here, would be great if solved Thx! Love AOE Scheduler |
For now?
|
Hi, Have a great day, |
thanks I understand however you must know sometimes we have limited influence on others .... so a workaround, or at least the ability to stop receiving clogged error logs and emails about this would already be a lot of help how about adding a quick check thx |
What would one have to add the extension? I dont see RunModel or run_model variables on other cron .... and am trying to fix but dont know how/where to add what ;P (any tips appreciated) This is what makes it a little more complex in confix.xml - the way that the cron jobs are added where would one add
|
@fbrnc Thanks for the resolution. Seems to be extension devs that need to get on the ball. should have thought about it being a magic method. Again, thank you for the explanation. |
Hi,
You have a method that is being called in getCallback() in Job.php that tries to return $helper->getCallBack($this->getRunModel()); getRunModel() doesn't even exist in the program
. thus this is what we are getting on a customer store:
Cron error while executing xtento_orderexport_profile_1:
exception ‘Mage_Core_Exception’ with message ‘Invalid model/method definition, expecting "model/class::method".’ in /public_html/app/Mage.php:595 Stack trace:
#0 app/code/community/Aoe/Scheduler/Helper/Data.php(294): Mage::throwException('Invalid model/m…') #1app/code/community/Aoe/Scheduler/Model/Job.php(143): Aoe_Scheduler_Helper_Data->getCallBack('')
#2 /public_html/app/code/community/Aoe/Scheduler/Model/Schedule.php(180): Aoe_Scheduler_Model_Job->getCallback()
#3 public_html/app/code/community/Aoe/Scheduler/Model/Schedule.php(570): Aoe_Scheduler_Model_Schedule->runNow(true)
#4 /public_html/app/code/community/Aoe/Scheduler/Model/Observer.php(39): Aoe_Scheduler_Model_Schedule->process()
#5 public_html/app/code/local/Xtento/OrderExport/Model/Observer/Cron/Config.php(24): Aoe_Scheduler_Model_Observer->dispatch(Object(Varien_Event_Observer))
#6 public_html/app/code/core/Mage/Core/Model/App.php(1338): Xtento_OrderExport_Model_Observer_Cron_Config->addCronjobsToConfig(Object(Varien_Event_Observer))
#7 public_html/app/code/core/Mage/Core/Model/App.php(1311): Mage_Core_Model_App->_callObserverMethod(Object(Xtento_OrderExport_Model_Observer_Cron_Config), ‘addCronjobsToCo…’, Object(Varien_Event_Observer))
#8 public_html/app/Mage.php(448): Mage_Core_Model_App->dispatchEvent('default', Array)
#9 /public_html/shell/scheduler.php(356): Mage::dispatchEvent('default', Array)
#10 /home/afsupply/public_html/shell/scheduler.php(21): Aoe_Scheduler_Shell_Scheduler->cronAction()
#11 public_html/shell/scheduler.php(382): Aoe_Scheduler_Shell_Scheduler->run() #12 {main}
The text was updated successfully, but these errors were encountered: