teraßyte

It's not listed in the new Marketplace's site. You can find it directly on the developer's site: https://invisiondevs.com/files/file/2-robokassa-payment-gateway/

No, there is no option to moderate blog entries. I assume that's because blogs are technically "owned" by the users who create them. You'll need some kind of custom modification to add blog entries to the approval queue like other content. Unless one already exists, but I don't remember seeing one.

The template core > front > profile > allFollowers was updated in 4.7.14 to include type casting for the page value in the bottom pagination: {template="pagination" group="global" app="core" location="global" params="$url, ceil( $followersCount / 50 ), (int) \IPS\Request::i()->page ?: 1, 50"} However, the top pagination in the same template is still missing the (int) type casting: {template="pagination" group="global" app="core" location="global" params="$url, ceil( $followersCount / 50 ), \IPS\Request::i()->page ?: 1, 50"}

The articles page is the default one when you install the application. You simply need to select the new page you made as the default one. You can do so from the menu on the right of the page's row. Open it and click on Make default page for this folder.

Do you have the Pages application? If you do, you can set it up as the default application and create your homepage there. With that, the forum URL will become https://www.scalewings.org/forums/ without needing to use a "swoc" subfolder.

Their site has been having more and more issues lately. I'd suggest to your members to use another hosting image service.

Small trick: Compress all the files you have to upload into a single ZIP file, upload it to the server, and then uncompress it through SSH. It saves a lot of time. 🙂

https://invisioncommunity.com/clientarea/free-trial

Maybe some kind of caching? 🙄

Yes. But remember that together with the files, you also need the correct PHP version, though. You're likely using PHP 7.4 or an earlier version because 4.5 doesn't support PHP 8. (Support for PHP 8.0 was added in 4.6 if I remember correctly.)

A few points: Until you upload the new 4.7.14 files in the correct location, the upgrade script will tell you there's nothing to upgrade. After uploading the new files you get a 500 error because the last 4.7.14 version requires PHP 8 and you still need to run the upgrader from /admin/upgrade. If you want to be sure the upgrade works correctly, you could try a test upgrade on a copy of the forum on another folder/server first.

There's a plugin by @Adriano Faria to remove the Pages option from the quick search menu. That would make it default to Everywhere in your situation. However, after the move from the IPS Marketplace, the plugin is missing from his site. I've already let him know. You can keep an eye on his site for when it's re-added: https://www.sosinvision.com.br/ Another option would be to convert the pins database to a custom application or a database in the Pages application. That would take quite a lot of time to get things set up, though. 😋

For Application.php you can use: /** * Cleanup after saving * * @param bool $skipMember Skip clearing member cache clearing * @return void * @note This is abstracted so it can be called externally, i.e. by the support tool */ public static function postToggleEnable( $skipMember=FALSE ) { # Parent call parent:postToggleEnable( $skipMember ); # Your code here # [...] } Or you can also extend set_enabled(): /** * [Node] Set whether or not this node is enabled * * @param bool|int $enabled Whether to set it enabled or disabled * @return void */ protected function set__enabled( $enabled ) { # Parent call parent:set__enabled( $enabled ); # Your code here # [...] } They actually use set_enabled() to switch the application's tasks (which is what you want to do with the login handler): /* Update other app specific task statuses */ \IPS\Db::i()->update( 'core_tasks', array( 'enabled' => (int) $this->enabled ), array( 'app=?', $this->directory ) );

It's in the Integrations area in ACP. Look at the last part of this guide:

Don't use the upgrade script in ACP. Try going manually to /admin/upgrade instead.

Yes. That setting is not restricted to a specific forum, blog, gallery album, etc. It applies to everything the user posts.

There is no default option like that in Invision Community. You need a modification for it: https://www.invisioneer.org/files/file/36-dp42-topics-per-time/

While reviewing some code in the forums application I found a couple of places that check the wrong class name for topics if the group is allowed to hide its own topics. These are the 2 files where IPS\forums\Topics needs to be replaced with IPS\forums\Topic: Line 649 in \applications\forums\modules\front\forums\forums.php $canHide = ( \IPS\Member::loggedIn()->group['g_hide_own_posts'] == '1' or \in_array( 'IPS\forums\Topics', explode( ',', \IPS\Member::loggedIn()->group['g_hide_own_posts'] ) ) ); Line 530 in \applications\forums\sources\Topic\Topic.php $canHide = ( $item ) ? $item->canHide() : ( \IPS\Member::loggedIn()->group['g_hide_own_posts'] == '1' or \in_array( 'IPS\forums\Topics', explode( ',', \IPS\Member::loggedIn()->group['g_hide_own_posts'] ) ) ); I searched all the files just in case, but those are the only ones I found.

There is no option for that currently. You need to edit the template core > front > global > logo and replace (twice) the link: {setting="base_url"} with the one you want to use.

There is a tool in ACP to rebuild the achievements right away (see the button in the Other Settings screenshot): Before rebuilding, you can change the rules so that they add only 1 point for each content they make. By default, users get 10 points for a new item they post and 5 points for each comment/reply.

It's the joined column in the core_members table. The value must be a UNIX timestamp: https://www.unixtimestamp.com/ Example timestamp for the current time: 1700338973

Yeah. With 10k accounts, options #1 and #2 aren't really feasible. 😅 The only real option would be #3. A quick script to import a CSV file that contains only the account email and their joined date. It could quickly go through the data to update the date column in the members' table using the email. It should be easy enough for your developer in case you want to go ahead with it.

It's the name of IPS's hosting service: Community in the Cloud.

Not really. The setting may speed up things slightly based on the server configuration, but I found it causes problems more often than not. Personally, I suggest leaving it disabling.

Yes, it skips the account. The code doesn't account for updating existing ones. Your only options are: Delete the imported members and re-import them with the proper field selected for the join date. If the accounts are only a few, manually update the unix timestamps directly in the database. (Always make a backup before any manual edits.) If you have a lot of accounts, create a script to automatically update the joined unix timestamp. Give up on updating the joined date. 😋