phae

I believe i've installed it - at least there was a short installer with progress bar. But thanks to your hint that there might be a relevant difference here, i just: Uninstalled blog, which deleted the files Copied the files from client area again Installed Blog again Now everything seems to work!

Thanks for the quick reply. I had forgot to mention this, but I did in fact enable the application there, right after copying the files and before "Get Support" prompted me for the SQL queries. So the app is enabled, there's a link to "blogs" on the staging site, just a template error on those files.

It does? Sorry for the confusion. I'll try a timeline: Bought the blog but didn't install it immediately Upgraded to the February Release 4.7.7 when that came out Wanted to install the blog, but it wasn't visible in Site Features Applications Downloaded a new set of files from the client area Copied those files in-place over existing community "Get Support" told me to run blog-specific SQL queries /admin/upgrade says There are "no applications available to upgrade" Blog templates are broken Hope that clears it up?

As written, I had just upgraded to the February release before trying to install the blog. /admin/upgrade just says "There are no applications available to upgrade"

Hope it's okay to re-use this thread, as it's concerning the same instance @Dannyowas writing about. I had just upgraded the instance to the February release after the blog had been bought, but still couldn't find it listed inside the AdminCP. So I've downloaded the latest files from the client and overwrote the existing folder with those & set permissions. I then started to see the Blog in System>Site Features>Applications and run its installer. Curiously enough "Get Support" prompted me to run some SQL queries to modify the blog schema. I now see no warnings, all updates seem to be applied and the site generally works, but the blog site fails with a template error (i see the stack trace if i put the theme in developer mode): OutOfRangeException: (0) #0 /srv/www/system/Content/Item.php(1461): IPS\Patterns\_ActiveRecord::load() #1 /srv/www/system/Theme/Theme.php(4628) : eval()'d code(103): IPS\Content\_Item->container() #2 /srv/www/system/Theme/Dev/Template.php(171): IPS\Theme\theme_blog_front_browse_indexGridEntry() #3 /srv/www/system/Theme/Theme.php(4628) : eval()'d code(122): IPS\Theme\Dev\_Template->__call() #4 /srv/www/system/Theme/Dev/Template.php(171): IPS\Theme\theme_blog_front_browse_indexGrid() #5 /srv/www/applications/blog/modules/front/blogs/browse.php(108): IPS\Theme\Dev\_Template->__call() #6 /srv/www/system/Dispatcher/Controller.php(118): IPS\blog\modules\front\blogs\_browse->manage() #7 /srv/www/system/Dispatcher/Dispatcher.php(153): IPS\Dispatcher\_Controller->execute() #8 /srv/www/index.php(13): IPS\_Dispatcher->run() #9 {main} Is this to be expected with a custom theme? it seems to inherit those templates right from the default theme.

Not sure what exactly happened here, but setting `DEBUG_TEMPLATES` in constants.php to true helped me to get an error message and for my templates.

Sorry, you are right. error_log is logged, but syntax errors are not for some reasons. Will post again when i found a solution.

As stated, if i add error_log("Test"); to my invisioncommunities index.php, that line shows up in the error log just fine, so unless I am misunderstanding you, it seems like PHP errors aren't suppressed per se? (I am running the host myself)

Hi @Marc Stridgen - Yes, I've cleared system caches from the support area multiple times. And disk template changing is turned off.

Thanks for your answer, @Randy Calvert. Forgot to mention it, but according to "/admin/?app=core&module=support&controller=phpinfo" all 3 of those settings are already in effect. Something still seems to suppress my errors

Hello, I've been in the process of adapting a custom theme for the latest InvisionCommunity 4.7.6. and PHP 8. It worked well with 4.7.2 and PHP 7.4, Since I hav disabled some incompatible plugins and updated a few custom blocks, it started working with the upgrade - but *only* in designer mode. Without theme designer mode I just see a blank page and no errors in the system log, the error log or my php error log. Some subpages also work without designer mode, but my start page and a few others do not. I've synced my theme changes when disabling designer mode, cleared caches and made sure my php settings are working by temporarily adding error_log("Test") to index.php. Any hints on how to investigate, debug this further? I except some of my templates or blocks to need an update, but I'd except to get some form of error or exception if the whole board fails to load. thanks for your time