Undefined index: view in /home2/user/public_html/components/com_content/router.php on line 73

158 views
Skip to first unread message

Richard Hellyer

unread,
Jul 27, 2016, 2:12:27 PM7/27/16
to Joomla! CMS Development
I recently upgraded to J3.6 and noticed (possibly coincidentally), the following error in my error logs

Undefined index: view in /home2/user/public_html/components/com_content/router.php on line 73

Prior to 3.6 I was not receiving this error. 
I checked in github issues and see that there is a reference to the error but it has been closed. 
I don't completely understand the explanation, but it seems that a malformed link in an article triggers this.
However, I don't understand why any link should result in an 'undefined index' error in the error_log.
Is this something that I can circumvent or will it be fixed in a future release (the closure of the issue on github makes me think that it won't)





brian teeman

unread,
Jul 27, 2016, 4:38:26 PM7/27/16
to Joomla! CMS Development
What was the issue number?

Richard Hellyer

unread,
Jul 27, 2016, 5:06:49 PM7/27/16
to Joomla! CMS Development
Thanks for the quick reply - It looks like it was issue #10721

piotr_cz

unread,
Jul 28, 2016, 4:20:43 AM7/28/16
to Joomla! CMS Development

brian teeman

unread,
Jul 28, 2016, 5:29:59 AM7/28/16
to Joomla! CMS Development
Richard if that works for you please report back directly on the issue to confirm it. Right now it doesn't have enough people who have been able to confirm the bug in order to test the fix.

Richard Hellyer

unread,
Jul 28, 2016, 10:01:11 AM7/28/16
to Joomla! CMS Development
. I was able to figure out the specific urls that were causing it, so I'll try that out today and report back on the github issue list

On Thu, Jul 28, 2016, 2:30 AM 'brian teeman' via Joomla! CMS Development <joomla-...@googlegroups.com> wrote:
Richard if that works for you please report back directly on the issue to confirm it. Right now it doesn't have enough people who have been able to confirm the bug in order to test the fix.

--
You received this message because you are subscribed to a topic in the Google Groups "Joomla! CMS Development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/joomla-dev-cms/8PtHeQsbfO8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to joomla-dev-cm...@googlegroups.com.
To post to this group, send an email to joomla-...@googlegroups.com.
Visit this group at https://groups.google.com/group/joomla-dev-cms.
For more options, visit https://groups.google.com/d/optout.

Richard Hellyer

unread,
Jul 28, 2016, 9:24:23 PM7/28/16
to Joomla! CMS Development
I tried out the pull request but it didn't fix the error. I can now reproduce the error on my local server with our site and specific uri requests so I can try an additional fix if necessary.
I posted the more detailed error stack on github issues, but my comments aren't there now that I look so I may have done that wrongly.


On Thursday, July 28, 2016 at 7:01:11 AM UTC-7, Richard Hellyer wrote:
. I was able to figure out the specific urls that were causing it, so I'll try that out today and report back on the github issue list

On Thu, Jul 28, 2016, 2:30 AM 'brian teeman' via Joomla! CMS Development <joomla-dev-cms@googlegroups.com> wrote:
Richard if that works for you please report back directly on the issue to confirm it. Right now it doesn't have enough people who have been able to confirm the bug in order to test the fix.

--
You received this message because you are subscribed to a topic in the Google Groups "Joomla! CMS Development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/joomla-dev-cms/8PtHeQsbfO8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to joomla-dev-cms+unsubscribe@googlegroups.com.
To post to this group, send an email to joomla-dev-cms@googlegroups.com.

Richard Hellyer

unread,
Jul 31, 2016, 7:28:50 PM7/31/16
to Joomla! CMS Development
Just closing this out. I installed the corrected com_content/router.php and tested and it worked fine on my test and live system (I think this is from pull request 6488)
Many thanks for everyone's help.
Reply all
Reply to author
Forward
0 new messages