[SOLVED] News Module Error on CMSMS 1.10.2

[mr.bacan]

Hi, I just updated a site from version 1.9.4.3 to 1.10.2 and everything is working great, except for the news module.

The summary template is showing the news articles, but when I try to access the article's detail I get this error:

Code: Select all

Fatal error: Uncaught exception 'Exception' with message 'Requesting indvlid data from News article object medio' in /home/vxv/public_html/modules/News/lib/class.news_article.php:306 Stack trace: #0 /home/vxv/public_html/tmp/templates_c/News^%%2C^2C9^2C9CD35F%%module_db_tpl%3ANews%3BdetailDetalle.php(12): news_article->__isset('medio') #1 /home/vxv/public_html/lib/smarty/Smarty.class.php(1263): include('/home/vxv/publi...') #2 /home/vxv/public_html/lib/classes/module_support/modtemplates.inc.php(242): Smarty->fetch('module_db_tpl:N...', '', 'News') #3 /home/vxv/public_html/lib/classes/class.CMSModule.php(2438): cms_module_ProcessTemplateFromDatabase(Object(News), 'detailDetalle', '', false, '') #4 /home/vxv/public_html/modules/News/action.detail.php(63): CMSModule->ProcessTemplateFromDatabase('detailDetalle') #5 /home/vxv/public_html/lib/classes/class.CMSModule.php(1583): include('/home/vxv/publi...') #6 /home/vxv/public_html/modules/News/action.defaulturl.php(4): CMSModule->DoAction('detail', 'cntnt01', Array, '103') #7 in /home/vxv/public_html/modules/News/lib/class.news_article.php on line 306

Does anyone has any idea why is this happening?

Thanks for any help on this.

[(M)]

I have the same problem with the News module after update to 1.10.3

Code: Select all

Fatal error: Uncaught exception 'Exception' with message 'Requesting indvlid data from News article object cms_selflink' in /.../modules/News/lib/class.news_article.php on line 306

Code: Select all

Exception: Requesting indvlid data from News article object cms_selflink in /.../modules/News/lib/class.news_article.php on line 306

i think it have something to do with 'cms_selflink'.

Did you solved it?

[mr.bacan]

I don't have the solution for this, I just upgraded to version 1.10.3 and problem solved. Sorry, but I never knew the origin of this error.

Hope you get it solved.