vmError: $link["view"] is empty

[jenkinhill]

SEF?

[fire47]

SEF?

Huh?

[jenkinhill]

Do you have SEF turned on?

[bytelord]

Hello,

Sorry for asking again but could you also verify that AIO is updated also (2.0.14)?

[fire47]

Do you have SEF turned on?

Yes

[fire47]

Hello,

Sorry for asking again but could you also verify that AIO is updated also (2.0.14)?

Yes

[jenkinhill]

OK can you turn off all SEF and see if the error goes away?

[Milbo]

Go to the router.php line and enter at line 1012 vmdebug('my item with empty view'); so that the else part look like

Code Select Expand


else {
vmdebug('my item with empty $link["view"]',$item);
vmError('$link["view"] is empty');
}


[fire47]

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.

[fire47]

Go to the router.php line and enter at line 1012 vmdebug('my item with empty view'); so that the else part look like

Code Select Expand


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?

[jenkinhill]

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.

[fire47]

Suggests to me that is caused by a Joomla menu link that maybe is disabled or hidden.

Mystery has been solved, thanks.

[Milbo]

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.

[bytelord]

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

[Milbo]

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.