- Posts: 49
- Thank you received: 0
warning shows up after 2.6.1 upgraded.
-- HikaShop version -- : 2.6.1
-- Joomla version -- : 3.4.8
-- PHP version -- : 5.5.9
-- Browser(s) name and version -- : chrome 47
-- Error-message(debug-mod must be tuned on) -- : a warning: JLIB_APPLICATION_ERROR_COMPONENT_NOT_LOADING shows up after 2.6.1 upgraded
Hi
a warning: JLIB_APPLICATION_ERROR_COMPONENT_NOT_LOADING shows up in products page after 2.6.1 upgraded.
market.zaihaiwai.net/index.php/category/...bert-louis-stevenson
and a warning: load component error: 914, could not find component in category page.
as show:
market.zaihaiwai.net/index.php/category.html
there is no these warning in 2.6.0. How to fix these issues?
thanks
Please Log in or Create an account to join the conversation.
We already checked the HikaShop code and we re-checked it.
Few weeks ago ; we had a similar report in the forum :
www.hikashop.com/forum/install-update/88...r-update-to-2-6.html
But in HikaShop ; we did not have any code which can use the Joomla "JComponentHelper" with a dynamic value.
We do use that "JComponentHelper" in few places but only for the function "getParams" and always for the "com_hikashop" component.
That's why we think that it is a side effect coming from something else.
Like I just wrote, the message is from "JComponentHelper" which is a library from the Joomla core. That is something that any plugin can use.. That's right that the issue is on HikaShop page but it does not means that HikaShop is the source.
Now the best is to have the "debug trace" in order to understand from where the issue is coming from.
The best is to modify temporally the file "libraries/cms/component/helper.php" and replace
And also
And it will display in the page the debug trace which will help us to find the source.
Regards,
Jerome - Obsidev.com
HikaMarket & HikaSerial developer / HikaShop core dev team.
Please Log in or Create an account to join the conversation.
I changed the code in helper.php as you show, but the pages become HTTP 500 internal server error
Please Log in or Create an account to join the conversation.
replace
And also
That should display a blank page with only the debug data when the problem occurs.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
So you can put the "echo" line just before the "JLog::add" line.
Regards,
Jerome - Obsidev.com
HikaMarket & HikaSerial developer / HikaShop core dev team.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
We got the debug data from someone else with the same error:
As you can see in the debug data, the processing doesn't go through HikaShop when displaying that error.
So the problem doesn't come from HikaShop.
The solution will be to simply delete the lines:
Please Log in or Create an account to join the conversation.
thank you~
Please Log in or Create an account to join the conversation.
- Posts: 62
- Thank you received: 3
Want to know, because now, potentially, when updating Joomla the error would return, so I want to keep track of it...
Please Log in or Create an account to join the conversation.
Jerome - Obsidev.com
HikaMarket & HikaSerial developer / HikaShop core dev team.
Please Log in or Create an account to join the conversation.
we were referred here from the other thread where we mentioned our "component not found error" ( www.hikashop.com/support/forum/install-u...r-update-to-2-6.html ). We think we found out where the error is coming from.
After starting out with a clean install of Joomla and Hikashop and setting everything up again one by one, we've found the error starts showing up when we added a Hikashop Filter Module. By unpublishing the filter module the error disappears again.
The number in the error message, "Error loading component: 110", corresponds with the number set in the Menu field under the Hikashop Filtering Module, which was set to our products listing menu with ID 110. We can manually change this field to whatever number, and that number will then also appear in the error message on our front end. So the error clearly refers to the Menu field in the Filter Module.
Unfortunately we do not have enough programming knowledge to figure out what causes the error exactly, but hopefully this will help to reproduce the issue and find a solution.
Thanks very much!
Please Log in or Create an account to join the conversation.
- Posts: 38
- Thank you received: 0
This site is due to go live Monday 1st Feb. I can work around this to finish the site but I will either have to downgrade Hikashop or have this sorted by then.
I do not have any extension numbered 134 which is the number it is showing. I have a menu item with that number as described. A workaround to stop the error would be good enough as the filter works fine.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Could you try to edit the view "product / filter" and replace the lines:
We are waiting for your feedbacks to fix this issue as soon as possible !
Please Log in or Create an account to join the conversation.
thanks, that fixes the error, and as far as we can see everything still works as it should.
Thanks again!
Please Log in or Create an account to join the conversation.
Yes working here too. Thanks for the fix.
many thanks.
Please Log in or Create an account to join the conversation.
Thanks for the feedback ; we will generate new 2.6.1 packages with that hotfix.
Regards,
Jerome - Obsidev.com
HikaMarket & HikaSerial developer / HikaShop core dev team.
Please Log in or Create an account to join the conversation.
- Posts: 38
- Thank you received: 0
Please Log in or Create an account to join the conversation.
Instead of being directed to the payment environment, we get a blank page with the error:
"Notice: Trying to get property of non-object in /components/com_hikashop/views/product/tmpl/filter.php on line 30 Fatal error: Call to a member function get() on null in /components/com_hikashop/views/product/tmpl/filter.php on line 30".
We undid the change suggested by Xavier and payment works fine again, but we get the error message back. Can you suggest any solution to get rid of the component not found error, and also get our payments to work?
Thanks very much once again.
Please Log in or Create an account to join the conversation.