teraßyte

Probably a wrong rule inside an .htaccess file, or maybe your new hosting has some kind of redirect setup that is interfering with something else in Invision Community. 🤔

Did you customize the email templates at some point perhaps? The last update changes the templates to include a new security key, and if the parameters of the template don't match, it's most likely causing an error preventing the email from being sent.

I usually see this issue logged when the setting to cache templates to disk is enabled. Check, and if you have it enabled, try disabling it and the error should go away. Unless you need it enabled for some reason? It usually causes only more trouble enabled, though. 🤷‍♂️

The list of followed members is available in User Menu > SETTINGS > Manage Followed Content > OTHER > Members. You can also look up all other kinds of categories/items. Here's a direct link to the page on this site: https://invisioncommunity.com/followed/?type=core_member

I guess that's why I was getting 504 timeouts for a while then: The site seems fast again now. 🤔

Today this site is extremely slow and/or unresponsive when I try to load anything (even the latest notifications with an ajax request). I'm also getting often a 504 error: 504 Gateway Time-out 🤷‍♂️ === EDIT: Seems fast again for now. 🙄

If the mbstring extension is installed but disabled, and you can enable/disable PHP extensions in cPanel, you can fix it. However, if the extension is not installed, or you can't enable/disable PHP extensions in cPanel, you'll have to ask your hosting about it because it needs to be installed/enabled through the WHM panel instead. And unless you're on a VPS/Dedicated server, you won't have WHM access. Nevermind. I missed your last line that you fixed it. Great! 🙃

You may be missing some required extensions on version 8.1 and have them enabled with 8.2. Use the requirements checker with both PHP versions to compare if anything is missing/different:

My post was split from this topic and acknowledged as a bug:

@Marc This is about the auto-complete field when you're creating a new PM. The member search when you type a name loads banned accounts: The member you see above is permanently banned. The problem is the code in applications/core/modules/front/system/ajax.php that doesn't skip banned members when loading the results: /** * Find Member * * @return void */ public function findMember() { $results = array(); $input = str_replace( array( '%', '_' ), array( '\%', '\_' ), mb_strtolower( \IPS\Request::i()->input ) ); $where = array( "name LIKE CONCAT(?, '%')" ); $binds = array( $input ); if ( \IPS\Dispatcher::i()->controllerLocation === 'admin' OR ( \IPS\Member::loggedIn()->modPermission('can_see_emails') AND \IPS\Request::i()->type == 'mod' ) ) { $where[] = "email LIKE CONCAT(?, '%')"; $binds[] = $input; } if ( \IPS\Dispatcher::i()->controllerLocation === 'admin' ) { if ( \is_numeric( \IPS\Request::i()->input ) ) { $where[] = "member_id=?"; $binds[] = \intval( \IPS\Request::i()->input ); } } /* Build the array item for this member after constructing a record */ /* The value should be just the name so that it's inserted into the input properly, but for display, we wrap it in the group *fix */ foreach ( \IPS\Db::i()->select( '*', 'core_members', array_merge( array( implode( ' OR ', $where ) ), $binds ), 'LENGTH(name) ASC', array( 0, 20 ) ) as $row ) { The code should be updated to skip banned members unless you're an admin/moderator maybe? Admins could still need banned members to show up when doing something in ACP, etc.

There's not even a hook point to add additional filters before the query loads the results. However, it's still possible to rewrite the whole function with a custom modification.

I don't think this option will ever be added to the framework. Rather, I believe there was an option for it in an older (2.x?) version, but it was removed at some point. Your best option is to have a custom modification made.

Ops, sorry. I pasted the wrong link it seems. I meant to post this one instead:

Have a look at this topic:

@Daniel F Nope. Still the same. I can even reproduce it in v5, and there it's actually worse because the option Only in Clubs still displays the block in both calendar and club view just like #1. You can take a look at my v5 test site if you want.

I'll test with .18 Beta 3 shortly.

Is the admin account you're trying to use restricted somehow in the ACP? If yes, try with an unrestricted account. Without a specific permission, I don't recall which or where it is right now, the upgrader will throw an error.

The auto mode tends to break things often. It would be best if you put the ads in each location manually. 🙄

Just confirming that the tags issue is fixed in 4.7.18 Beta 2. 👍 The updated column issue in the second post is still there for now.

This is fixed in 4.7.18 Beta 2.

I can reproduce the issue on a fresh 4.7.17 install: Add the Upcoming Events block while viewing a calendar. Now create a club and add a calendar. Issues: Select Everywhere except clubs for the Visibility option => The block shows in both calendar and club view. Select Only in clubs for the Visibility option => The block doesn't show anywhere. I also tried different blocks and applications (like Downloads), but the result is the same. The visibility options are completely broken. 🤷‍♂️

Anyone affected must re-install and re-uninstall the app to fix it for now then. 🤷‍♂️ This kind of fix should really be retroactive to fix sites where the issue already happened, though.

And in case your hosting has no idea how to proceed, and you don't want to move to Cloud, you can hire a 3rd party Provider to do the upgrade for you. 😋

That error is usually thrown if a utf8mb4 character is in the text and your database is not utf8mb4. For example, posting an emoji while the database is utf8/utf8mb3. Is your database using utf8mb4? Maybe something in the YouTube embed has a utf8mb4 Unicode character that triggers the check. 🤔

The column max_threads_error is not a default one. It was added by a modification you installed at some point. You'll need to contact the modification's developer for support.