Everything posted by teraßyte
-
Guests can post in bog entried event when guest blog posting is switched
You probably have the Post Before Registering setting enabled. It allows guests to reply, but they have to register/validate an account before the comment appears: Allowed where Members group can post Guests will see the ability to submit content and then will immediately be prompted to register an account before the content is actually submitted and viewable. This is useful for encouraging guests to register. Guest users will have up to one week to complete their registration before their content will be permanently removed. If the guest user does not complete their registration immediately, they will be sent a reminder email shortly after making the post.
-
Missing icon
The icon comes from a language string, so you probably translated the string used for that and it can't find/display the FA icon anymore. Does the icon appear if you switch back to an unmodified English default language?
-
Cannot add a code block by selecting multiple lines
I selected 3 lines in the editor to convert them into a code box, but the Block Style dropdown became disabled after selecting a second row. I had to select only the first line, convert it to a code box, and then copy/paste the other 2 lines into it. It's an unnecessary and (extremely) annoying process.
-
Very slow animation of setting the selector on the user menu 5.0.3
I just tested the tooltips with Opera and the lag is even worse there: the normal title attribute is first displayed, and only after a few seconds the JS kicks in and replaces the title attribute with _title (underscore) to show the tooltip. 👀 EDIT Opera One (version: 117.0.5408.39) Windows 10 64-bit Chromium Version: 132.0.6834.209
-
Very slow animation of setting the selector on the user menu 5.0.3
It's a known issue. The JS is horribly slow in certain OS/browser combinations (Windows + Chrome browser seems to main issue?). I have reported the tooltip issue myself in the old v5 beta bug tracker, but it's not resolved yet. You can read what @Matt Finger posted in this other bug report about the root cause:
-
Invision Community 5.0.2 Released
Manually. Maybe they'll show it as an update when v4 is unsupported, but for now, it still is.
-
[5.0.2] UINode::rowBadge() extension method not called for \IPS\nexus\Package
Another related issue to this location is that the code should not return the whole ipsBadge ipsBadge--intermediary CSS, but only intermediary because the code already automatically adds the ipsBadge ipsBadge-- part: protected function get__badge(): ?array { if ( $this->deleteOrMoveQueued() === TRUE ) { return array( 0 => 'intermediary', 1 => 'mass_change_purchases_in_progress', ); } if( $this->locked ) { return array( 0 => 'negative', 1 => 'product_locked' ); } /* Check extensions for a possible badge */ return $this->ui( 'rowBadge', array(), true ); } With the current code, the output is the following with a non-existent ipsBadge--ipsBadge CSS class: <span class="ipsBadge ipsBadge--ipsBadge ipsBadge--negative">Locked</span>After my change above the output is as expected: <span class="ipsBadge ipsBadge--negative">Locked</span> EDIT This issue is present in a lot of other get__badge() functions from other classes, not just this one.
-
[5.0.2] UINode::rowBadge() extension method not called for \IPS\nexus\Package
I added a UINode extension on the \IPS\nexus\Package class but the rowBadge() method is not being executed at all. This happens because the code in the file returns NULL rather than calling the parent Model method that contains the ui() call: protected function get__badge(): ?array { if ( $this->deleteOrMoveQueued() === TRUE ) { return array( 0 => 'ipsBadge ipsBadge--intermediary', 1 => 'mass_change_purchases_in_progress', ); } if( $this->locked ) { return array( 0 => 'ipsBadge ipsBadge--negative', 1 => 'product_locked' ); } return NULL; } The parent Model method correctly calls the extension function at the end instead of returning NULL: protected function get__badge(): ?array { if ( $this->deleteOrMoveQueued() === TRUE ) { return array( 0 => 'ipsBadge ipsBadge--intermediary', 1 => 'node_move_delete_queued', ); } /* Check extensions for a possible badge */ return $this->ui( 'rowBadge', array(), true ); } I tried replacing the NULL return locally with the ui() method and the badge was properly displayed.
-
.htaccess and API
That's the correct response when it's trying to test if the .htaccess is present.
-
IPS 4.7.20 - SendGrid for bulk emails not working anymore
There was a bug in an old version (4.7.18 or 19?) where it displayed the wrong email choice. If you update to version 4.7.20 it should be fixed. If you are already on 4.7.20, it might be a different bug instead.
-
PHP version
I've seen people post a few times saying they're using PHP 8.4.3, but I haven't checked myself if everything works. Based on some replies I've seen, there were bugs that have been fixed for it, so I suppose it should(?) work with 8.4, too.
-
PHP version
Version 4 supports only PHP 8.0 or 8.1. Version 5 supports PHP 8.1+.
-
Translit URL (Sonya*) - 5.0 version
Yeah, that application from the link is for v5 and I can confirm the site loads for me. Maybe something is blocking the site's domain/IP. 🤷♂️ http://isup.me/invisiondevs.com
-
Mark as Solution
@Square Wheels Found it. I was able to reproduce what you're seeing after I enabled this setting in the Theme Editor: Page Layouts > Feature first post? When this specific setting is enabled the post marked as solution is moved to the top. Not sure if it's a bug or working as intended, though. IPS will have to answer this. 😋
-
Mark as Solution
I can indeed see what you mean after looking at the video. Maybe there's a setting that does that and you have it enabled on your forum while it's not here. 🤔
-
Mark as Solution
What are you seeing exactly? Even just looking at a randomly solved topic on this forum you can see the post itself remains in its original location. It does add a Solved by XXX / Go to Solution message + link after the first post, but that's it. 🤨
-
5.0.2 - [[Template core/front/global/widgetContainer is throwing an error
I posted a bug report about this issue ~15 minutes ago before seeing your topic. 😅 The bug report starts from publishing future topics, but the root issue is the same with modPermission() returning a NULL value.
-
[5.0.2] Errors with restricted moderators after upgrade from 4.7.20
The restricted moderator permissions also caused all sorts of template issues all over the place (userBar, WidgetContainer at the top, Sidebar, WidgetContainer at the bottom, etc.). Once I edited the moderator and made it unrestricted, (despite the error above) all issues went away. I believe some code assumes a certain moderator permission always exists while in fact, it's not there. I'm saying this because this was a test upgrade from version 3.4.9 to 5.0.2 (passing through 4.7.20) and moderator permissions like posting topics in the future were not included in v3.
-
[5.0.2] Errors with restricted moderators after upgrade from 4.7.20
This is the error I see trying to view a topic after upgrading a site to 5.0.2: TypeError: IPS\forums\Topic::canViewFutureItems(): Return value must be of type bool, null returned (0) #0 /home/nuovo/domains/domain.com/public_html/invision/system/Content/Item.php(3029): IPS\forums\Topic::canViewFutureItems() #1 /home/nuovo/domains/domain.com/public_html/invision/applications/forums/sources/Topic/Topic.php(379): IPS\Content\Item::getItemsWithPermission() #2 /home/nuovo/domains/domain.com/public_html/invision/system/Helpers/Table/Content.php(418): IPS\forums\Topic::getItemsWithPermission() #3 /home/nuovo/domains/domain.com/public_html/invision/system/Helpers/Table/Table.php(531): IPS\Helpers\Table\Content->getRows() #4 /home/nuovo/domains/domain.com/public_html/invision/applications/forums/modules/front/forums/forums.php(568): IPS\Helpers\Table\Table->__toString() #5 /home/nuovo/domains/domain.com/public_html/invision/applications/forums/modules/front/forums/forums.php(75): IPS\forums\modules\front\forums\forums->_forum() #6 /home/nuovo/domains/domain.com/public_html/invision/system/Dispatcher/Controller.php(139): IPS\forums\modules\front\forums\forums->manage() #7 /home/nuovo/domains/domain.com/public_html/invision/system/Dispatcher/Dispatcher.php(169): IPS\Dispatcher\Controller->execute() #8 /home/nuovo/domains/domain.com/public_html/invision/index.php(16): IPS\Dispatcher->run() #9 {main} The issue comes from the canFuturePublish() function in the FuturePublishing trait: /** * Can set items to be published in the future? * * @param Member|NULL $member The member to check for (NULL for currently logged in member) * @param Model|null $container Container * @return bool */ public static function canFuturePublish( ?Member $member=NULL, ?Model $container = NULL ): bool { $member = $member ?: Member::loggedIn(); return $container ? static::modPermission( 'future_publish', $member, $container ) : $member->modPermission( "can_future_publish_content" ); } Without a container, the $member->modPermission( "can_future_publish_content" ) is executed code, and this specific function can return a NULL value: /** * Get moderator permission * * @param string|null $key Permission Key to check, or NULL to just test if they have any moderator permissions. * @return mixed */ public function modPermission( string $key=NULL ): mixed { /* Load our permissions */ $permissions = $this->modPermissions(); if ( $permissions == FALSE ) { return FALSE; } /* If we have all permissions, return true */ if ( $permissions === '*' or $key === NULL ) { return TRUE; } /* Otherwise return it */ return $permissions[$key] ?? NULL; } === This issue is because the user I'm logged in as is a restricted moderator. I then tried to set it as unrestricted to test if anything changed, and received this new error in ACP instead: TypeError: IPS\core\extensions\core\ModeratorPermissions\ContentGenerator::onChange(): Argument #2 ($changed) must be of type array, string given, called in /home/nuovo/domains/domain.com/public_html/invision/applications/core/modules/admin/staff/moderators.php on line 527 (0) #0 /home/nuovo/domains/domain.com/public_html/invision/applications/core/modules/admin/staff/moderators.php(527): IPS\core\extensions\core\ModeratorPermissions\ContentGenerator->onChange() #1 /home/nuovo/domains/domain.com/public_html/invision/system/Dispatcher/Controller.php(128): IPS\core\modules\admin\staff\moderators->edit() #2 /home/nuovo/domains/domain.com/public_html/invision/applications/core/modules/admin/staff/moderators.php(74): IPS\Dispatcher\Controller->execute() #3 /home/nuovo/domains/domain.com/public_html/invision/system/Dispatcher/Dispatcher.php(169): IPS\core\modules\admin\staff\moderators->execute() #4 /home/nuovo/domains/domain.com/public_html/invision/admin/index.php(15): IPS\Dispatcher->run() #5 {main}The moderator was still updated to Unrestricted despite the error, and trying to re-edit it generated no error.
-
Additional information in the profile?
Looks like you enabled only the Show on Member's profile? option. To display the fields with topics/posts, enable also the Show with member's content submissions? option.
-
Additional information in the profile?
You can use custom profile fields to display data below the photo while viewing a topic (or profile):
-
Member Blocked but not Blocked
Based on the error, it seems to be coming from CloudFlare (?). Are you using it on your site?
-
HTML Editor
The link still works for me. You might have some kind of block for that site/IP. 🙄 Iframe embeds can still be added. This was actually part of the feedback in the initial alpha testing. 😋 You can select the text and use the Clear Formatting button in the editor. I just quoted your text and used it in the quote below so you can see the result.
-
HTML Editor
All of that is gone. You can't edit anymore the HTML source directly nor you can set group/area permissions for each single editor button in v5. As for editing the HTML, you can use this modification as a workaround: https://invisiondevs.com/files/file/76-edit-html-of-posts/
-
Mark forum read
Yeah. This has been mentioned as feedback for v5 several times already. I was using this feature too, so I hope they'll add it back. 👀