Jump to content

Site broken for members (not guests) after latest update


DReffects2

Recommended Posts

Posted

Hey Guys,

I've just updated from 4.3 to the latest 4.4 but unfortunately the site's now broken for logged in members. Guests can access database records with no issues but members get:

 

Error: Call to a member function url() on boolean (0)
#0 /var/www/vhosts/xxxx.de/httpdocs/applications/cms/modules/front/database/record.php(331): IPS\Theme\class_cms_database_display_news->record(Object(IPS\cms\Records6), '\n<div data-cont...', NULL, true)
#1 /var/www/vhosts/xxxx.de/httpdocs/system/Dispatcher/Controller.php(96): IPS\cms\modules\front\database\_record->manage()
#2 /var/www/vhosts/xxxx.de/httpdocs/system/Content/Controller.php(50): IPS\Dispatcher\_Controller->execute()
#3 /var/www/vhosts/xxxx.de/httpdocs/applications/cms/sources/Databases/Dispatcher.php(347): IPS\Content\_Controller->execute()
#4 /var/www/vhosts/xxxx.de/httpdocs/applications/cms/widgets/Database.php(128): IPS\cms\Databases\_Dispatcher->run()
#5 /var/www/vhosts/xxxx.de/httpdocs/applications/cms/sources/Pages/Page.php(1283): IPS\cms\widgets\_Database->render()
#6 /var/www/vhosts/xxxx.de/httpdocs/applications/cms/sources/Pages/Page.php(2220): IPS\cms\Pages\_Page->getWidgets()
#7 /var/www/vhosts/xxxx.de/httpdocs/applications/cms/modules/front/pages/page.php(112): IPS\cms\Pages\_Page->output()
#8 /var/www/vhosts/xxxx.de/httpdocs/applications/cms/modules/front/pages/page.php(43): IPS\cms\modules\front\pages\_page->view()
#9 /var/www/vhosts/xxxx.de/httpdocs/system/Dispatcher/Controller.php(96): IPS\cms\modules\front\pages\_page->manage()
#10 /var/www/vhosts/xxxx.de/httpdocs/applications/cms/modules/front/pages/page.php(33): IPS\Dispatcher\_Controller->execute()
#11 /var/www/vhosts/xxxx.de/httpdocs/system/Dispatcher/Dispatcher.php(152): IPS\cms\modules\front\pages\_page->execute()
#12 /var/www/vhosts/xxxx.de/httpdocs/index.php(13): IPS\_Dispatcher->run()
#13 {main}

I've reverted all customizations and templates but still get that error... any clue what might cause this?

 

Thanks!

Posted
2 minutes ago, DReffects2 said:

I've reverted all customizations and templates but still get that error... any clue what might cause this?

My guess would be you didn’t succeed in reverting or upgrading the templates. 

Posted
12 minutes ago, opentype said:

My guess would be you didn’t succeed in reverting or upgrading the templates. 

your guess was right. I redid my steps and forgot about the database listing template itself.

 

Strange though...

I had this line of code in there:

	{{if $nextUnread !== NULL}}
		<div class='ipsGrid_span6 ipsType_right ipsPager_next'>
			<a href="{$nextUnread->url()->setQueryString( array( 'do' => 'getNewComment' ) )}" title='{lang="cms_view_next_unread_title" sprintf="$record::database()->recordWord( 1 )"}'>
				<span class="ipsPager_type">{lang="cms_next_unread_title" sprintf="$record::database()->recordWord( 1 )"}</span>
				<span class="ipsPager_title ipsType_light ipsTruncate ipsTruncate_line">{$nextUnread->mapped('title')}</span>
			</a>
		</div>
	{{endif}}

I've reverted this to the original:

		<div class='ipsGrid_span6 ipsType_right ipsPager_next ipsPager_noDesc'>
			<a href="{$record->url()->setQueryString( array( 'do' => 'nextUnread' ) )}" title='{lang="cms_view_next_unread_title" sprintf="$record::database()->recordWord( 1 )"}'>
				<span class="ipsPager_type">{lang="cms_next_unread_title" sprintf="$record::database()->recordWord( 1 )"}</span>
			</a>
		</div>

 

 

I do not quite understand why the original (from 4.3) hat the URL call with 'getNewComment' in there but I am also noticing that I do no longer get the title of the next record displayed since the {$nextUnread->mapped('title')} thingy is missing.

What has changed here?

 

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...