<![CDATA[ ERROR in modTemplateVar::renderOutput - My Forums]]> https://forums.modx.com/thread/?thread=104767 <![CDATA[ERROR in modTemplateVar::renderOutput]]> https://forums.modx.com/thread/104767/error-in-modtemplatevar-renderoutput#dis-post-563416 
ERROR in modTemplateVar::renderOutput @ /path/to/../core/model/modx/modtemplatevar.class.php : 288) Old modTemplateVar getRender outputmethod is deprecated since version 2.2.0.


modx version is MODX Revolution 2.7.0-pl
php version is 7.2



]]> stahl303 Jan 02, 2019, 11:55 PM https://forums.modx.com/thread/104767/error-in-modtemplatevar-renderoutput#dis-post-563416 <![CDATA[Re: ERROR in modTemplateVar::renderOutput]]> https://forums.modx.com/thread/104767/error-in-modtemplatevar-renderoutput#dis-post-563561 https://github.com/modxcms/revolution/pull/14162]]> markh Jan 14, 2019, 07:35 PM https://forums.modx.com/thread/104767/error-in-modtemplatevar-renderoutput#dis-post-563561 <![CDATA[Re: ERROR in modTemplateVar::renderOutput]]> https://forums.modx.com/thread/104767/error-in-modtemplatevar-renderoutput#dis-post-563556
PHP 7 (which I suspect you have) is much more likely than earlier versions to throw a 500 error when it encounters a PHP issue.

It could be an outdated plugin or snippet.

Sometimes, watching the Network tab in Chrome Dev. Tools (Ctrl-shift-i or F12) while loading a page will give a clue. If there's a connector.php call, you can click on it and look at the response tab, which might contain a PHP error message (buried in some dense HTML).

]]> BobRay Jan 14, 2019, 06:46 PM https://forums.modx.com/thread/104767/error-in-modtemplatevar-renderoutput#dis-post-563556 <![CDATA[Re: ERROR in modTemplateVar::renderOutput]]> https://forums.modx.com/thread/104767/error-in-modtemplatevar-renderoutput#dis-post-563551 paulbohman Jan 14, 2019, 07:18 AM https://forums.modx.com/thread/104767/error-in-modtemplatevar-renderoutput#dis-post-563551