I am still getting this message in the frontend after upgrading to 2.0.8c. I have tried deleting and recreating the menu item with no success. Help!!!
Can someone please help with this? I've tried many things and it still happens, just upgraded to 2.0.14 and it still happens!
Hello,
Please try without template overrides and post back your results
Regards
AFAIK I have no virtuemart template overrides. I tested the Atomic joomla default template and it still appears. Help!
Please delete and recreate the menu item that you publish vm2 front page ... not sure why this is happen, can you post a screenshot?
really rare error.
also your PHP and joomla version
Joomla 2.5.8, Virtuemart 2.0.14, Kunena 2.0.3, Community Builder 1.9, PHP 5.3.3
[attachment cleanup by admin]
I tried recreating a new menu item for virtuemart (I use category layout) and also made a virtuemart frontpage link but neither fixed the issue.
posting url could help
Quote from: Milbo on December 17, 2012, 21:58:07 PM
posting url could help
The message is only viewable by admins when logged into the frontend.
Nice,
Only for administrators??? Why you didn't told that at the begin??? On all pages or on account maintenance? any way provide a live url? miltivendor is enabled?
Seems that missing an override or any template regarding to admins or vendors ... not sure
Did you also update aio or only vm2 to 2.0.14?
Regards
Quote from: bytelord on December 17, 2012, 22:24:42 PM
Nice,
Only for administrators??? Why you didn't told that at the begin??? On all pages or on account maintenance? any way provide a live url? miltivendor is enabled?
Seems that missing an override or any template regarding to admins or vendors ... not sure
Did you also update aio or only vm2 to 2.0.14?
Regards
1. This is the 3rd thread I've posted in to get this issue resolved. After months of posting things tend to get lost. (as you can see this thread was started on July 16th.) This issue seems to have been ignored by the admins for some reason as others have the same issue, just do a search on the web/vm forum.
2. All public pages when admin is logged in.
3. Live url is useless without admin access. I will PM url if necessary.
4. Multivendor is not in use.
5. How do I confirm no overrides exist?
6. VM was upgraded from v1 to v2 and a couple of updates since then to 2.0.14. AIO was updated.
This issue is reported to be related to SEF, Joomla menu links and using more than one language. Joomla menu links must all be made in the same language. See this thread https://forum.virtuemart.net/index.php?topic=101134.msg335262#msg335262
Quote from: jenkinhill on December 19, 2012, 10:22:51 AM
This issue is reported to be related to SEF, Joomla menu links and using more than one language. Joomla menu links must all be made in the same language. See this thread https://forum.virtuemart.net/index.php?topic=101134.msg335262#msg335262
There must be another reason for the message as I have not installed any additional languages and all menu items are set to language=all.
SEF?
Do you have SEF turned on?
Hello,
Sorry for asking again but could you also verify that AIO is updated also (2.0.14)?
Quote from: bytelord on December 19, 2012, 19:36:58 PM
Hello,
Sorry for asking again but could you also verify that AIO is updated also (2.0.14)?
Yes
OK can you turn off all SEF and see if the error goes away?
Go to the router.php line and enter at line 1012 vmdebug('my item with empty view'); so that the else part look like
else {
vmdebug('my item with empty $link["view"]',$item);
vmError('$link["view"] is empty');
}
Quote from: jenkinhill on December 19, 2012, 22:04:42 PM
OK can you turn off all SEF and see if the error goes away?
Yes it goes away, although turning off SEF is not a permanent option.
Quote from: Milbo on December 19, 2012, 22:29:55 PM
Go to the router.php line and enter at line 1012 vmdebug('my item with empty view'); so that the else part look like
else {
vmdebug('my item with empty $link["view"]',$item);
vmError('$link["view"] is empty');
}
Path to router.php? Will I have to change this every time vm is updated? Is this a permanent solution that will be supported in future versions?
Quote from: fire47 on December 20, 2012, 20:57:51 PM
Yes it goes away, although turning off SEF is not a permanent option.
Suggests to me that is caused by a Joomla menu link that maybe is disabled or hidden.
Milbo's code change to look for that Joomla link problem is included in the core now and is in 2.0.16 - you may possibly get an error message saying exactly what the problem link is (if any now) when you use SEF.
Quote from: jenkinhill on December 20, 2012, 23:25:47 PM
Suggests to me that is caused by a Joomla menu link that maybe is disabled or hidden.
Mystery has been solved, thanks.
So the vmdebug message helped you to find the broken menu item? We worked for your problem at least an hour all together. A bit more enlightning explanation would be nice.
Quote from: Milbo on December 21, 2012, 17:08:10 PM
So the vmdebug message helped you to find the broken menu item? We worked for your problem at least an hour all together. A bit more enlightning explanation would be nice.
Thinking the same, broken menu item and please fire47 will be very helpfull give some more feedback to understand where this error was related too.
Regards
I think, the debug message showed him that it was exactly what we said from begin on. So he may feel guilty, which is quite normal. What he not understands is that also adding a vmdebug will help 100s of other users migrating vm1 to vm2 next year. As far as I know the majority did not update yet.
Quote from: Milbo on December 21, 2012, 17:08:10 PM
So the vmdebug message helped you to find the broken menu item? We worked for your problem at least an hour all together. A bit more enlightning explanation would be nice.
No, actually I didn't have to. Just the suggestion that there was another unpublished or hidden link allowed me to find the bad one. No one ever told me that having multiple links to virtuemart could be causing it, only the primary ones.
Quote from: Milbo on December 21, 2012, 17:15:03 PM
I think, the debug message showed him that it was exactly what we said from begin on. So he may feel guilty, which is quite normal. What he not understands is that also adding a vmdebug will help 100s of other users migrating vm1 to vm2 next year. As far as I know the majority did not update yet.
I didn't need to use the additional debug as mentioned above. No one ever said to me before that other links, even unpublished, could cause this error. No guilty feeling at all, its actually quite sad that this took over 6 months!!! The virtuemart community should be the ones that feel guilty, or even the developers since this is not in the documentation anywhere either.
Go to joomla and ask them. It is a joomla infrastructure, has not a lot todo with us. But next time we can turn on vmdebug and then you see directly which menu item is causing trouble.
Quote from: Milbo on December 22, 2012, 01:02:17 AM
Go to joomla and ask them. It is a joomla infrastructure, has not a lot todo with us. But next time we can turn on vmdebug and then you see directly which menu item is causing trouble.
They sent me here.
The reason is the menuitem id. We dont want to see this id in links. So we must search it and if you did not set a correct menu item to virtuemart, you get this error.
I actually had the same problem. I had two outdated menus which came from a previously migrated joomla site. They have not been used anyway. Obviously there were many broken menu entries so they caused a list of several "vmError: $link["view"] is empty" messages.
Anyway I think it would help when you would display something like "Menu: xxx / menu-entry: yyy is empty/invalid" or something similar instead of identical "$link["view"]" which do not explain what is wrong. I understand that you have check menu-entries for correct links to VM but a more verbous explanation of the problem would help to identify the menu and the broken entry.
It looks like a broken debug info which needs a fix to become more understandable.