CodingJungle

@Kjell Iver Johansen as promised

I'll keep 2.x servers running for 30 days after 3.0.0 launch, then i will shut them down. a few minutes of this video (its from a much earlier build, but the concepts are still similar), i talk about the mobile for babble 3.0. I'll do a fresh video later today of it, as it think it is a big improvement over 2.x "mobile".

I will be launching Babble 3.0.0 Chat service this monday, 10/19/2020. I will also be offering a 30 day free trial, that is limited to 20 connected user for anyone to get to test out. here is a short video explaining some of the features and to show off what is new in babble 3.0.0 Hope you enjoy!

One of the biggest complaints about my support (other than my disappearances) has been that i chose to keep it all in one topic. I've decided to make a topic for each of the apps, and will be requesting this topic be closed/deleted. CJ Duplicate Member Logger Keyword Tooltips Babble Downloads Plus Menu Groups Manager Name 2 Avatars Stratagem Nettoolkit Geo Regards, Michael

Nettoolkit Geo (Support Topic)

Stratagem (Support Topic)

Name 2 Avatars (Support Topic)

Menu Groups Manager (Support Topic)

Downloads Plus support topic.

CJ Duplicate Member Logger Support Topic

Support topic for Keyword tooltips

feel free to send me a PM

thanks for the shout out, but CJDML doesn't actually prevent same IP account creations or logins, it just detects them and sends out notifcations/PM's about them. it can be configured to delete automatically delete an alt account, but that is a bit extreme imho.

This topic is for babble support and/or questions.

are you still on IPS 4.4? if so, it is cause when i was developing the later versions of stratagem, i was using a more recent version of mysql that removed the length parameter for INT columns (the schema manager was actually throwing a lot of errors for me, so i removed them), but it causes that to show up in the support tool. i just missed that one when i put them back in for 4.4, in 4.5 this shouldn't show up. the 4.5 update has been released.

good point

I'm updating one of my apps, and it has a ton of ajax request, and i've done this in the execute method of my controllers: if( Request::i()->requestMethod() !== 'GET'){ Session::i()->csrfCheck(); } as all my POSTs are for state changes and my GETs aren't (so basically any http request that isn't a GET will hit the csrfCheck). from my testing, it appears to be effective, or should i be putting the csrfCheck into each method of the controller that needs to check it?

will be working on it this weekend, originally when i checked it out for 4.5 it was working fine, but i didn't take into account all the new rule changes for the market. So i will be updating the app this weekend to reflect those changes.

if you have this setting enabled, it will only use the mobile menu (on desktop too). i use it on my own site. so its not a bug, just a misunderstanding of what the setting is for :).

is it producing any errors? when i upgraded a few of my sites that use it and tested it on my local it didn't seem to be causing any issues. sorry for my late reply, for some reason i did not see the email notification (got a lot that day for various things). it creates a tab in the club for it: there aren't at this time, but this might change if the demand is there for it. its both, everything you need to run it yourself is made available in the ACP (the node script and the package.json for the node dependencies) or a hassle free purchasing a service subscription from my site (where my servers host the node/sockets components) okay ill test it out

sorta my point that extensions should implement an interface/extend an abstract class instead, that way if there is a change like this, it would be reflected in the interface/abstract and i wouldn't have to go on a wild goose chase to figure what this new method is expecting. since it was working for me on the notification settings on the front end, i figured it was something that was caught/fixed in 4.5.1/2/3 cause i added the method in one of my other apps, but that was back during the beta when i was upgrading it.

<?php /** * @brief Notification Options * @author <a href='https://www.invisioncommunity.com'>Invision Power Services, Inc.</a> * @copyright (c) Invision Power Services, Inc. * @license https://www.invisioncommunity.com/legal/standards/ * @package Invision Community {subpackage} * @since {date} */ namespace IPS\{app}\extensions\core\Notifications; /* To prevent PHP errors (extending class does not exist) revealing path */ if ( !\defined( '\IPS\SUITE_UNIQUE_KEY' ) ) { header( ( isset( $_SERVER['SERVER_PROTOCOL'] ) ? $_SERVER['SERVER_PROTOCOL'] : 'HTTP/1.0' ) . ' 403 Forbidden' ); exit; } /** * Notification Options */ class _{class} { /** * Get configuration * * @param \IPS\Member $member The member * @return array */ public function getConfiguration( $member ) { // Basically just return a list of the keys for the types of notification your app will send // keys can be anything you want. You can specify what should be the default value and any disabled values (acceptable values are "email" and "inline") // For each key, create a language string "notifications__<key>" which is what will display in the user's Notification Options screen return array( 'key' => array( 'default' => array( 'inline', 'push' ), 'disabled' => array() ), ); } // For each type of notification you need a method like this which controls what will be displayed when the user clicks on the notification icon in the header: // Note that for each type of notification you must *also* create email templates. See documentation for details: https://remoteservices.invisionpower.com/docs/devdocs-notifications /** * Parse notification: key * * @param \IPS\Notification\Inline $notification The notification * @return array * @code return array( 'title' => "Mark has replied to A Topic", // The notification title 'url' => \IPS\Http\Url::internal( ... ), // The URL the notification should link to 'content' => "Lorem ipsum dolar sit", // [Optional] Any appropriate content. Do not format this like an email where the text // explains what the notification is about - just include any appropriate content. // For example, if the notification is about a post, set this as the body of the post. 'author' => \IPS\Member::load( 1 ), // [Optional] The user whose photo should be displayed for this notification ); * @endcode */ public function parse_key( \IPS\Notification\Inline $notification ) { return array( 'title' => "Mark has replied to A Topic", // The notification title 'url' => \IPS\Http\Url::internal( '' ), // The URL the notification should link to 'content' => "Lorem ipsum dolar sit", // [Optional] Any appropriate content. Do not format this like an email where the text // explains what the notification is about - just include any appropriate content. // For example, if the notification is about a post, set this as the body of the post. 'author' => \IPS\Member::load( 1 ), // [Optional] The user whose photo should be displayed for this notification ); } } this is currently the boilerplate for when creating an extension, however you've added a method to this, that doesn't appear here, causing this error:

its really not the support, most people come to me wanting me to add something in that is highly illegal to track members (like implementing a JS lib that exploits browser vulnerabilities, to insert tracking code in it) or to track ETAGS, or implement a system based on IP's, when IP's are possibly the least reliable things in the world when it comes to VPN's, open networks available at every cafe and bar this side of the mississippi or when often same cell phone towers will give identical IP's to the different users. then they get upset when i explain to them i wont do it due to its illegality. There are also times i don't address issues, either cause it isn't an issue or the issue was mentioned in a negative review and they never contacted me in any way other than the review (or they complain about the one topic i have to support my handful of apps). I also get bombarded with features that are very use case and don't have any added marketability to the app itself, i am always open to ideas for improving it, but they have to be ideas that i feel also add value to the app. as it stands its a very simplistic app, to give you a basic idea if accounts are being shared or dupes are being used, or banned members attempting to ban evade, its not an end all be all app, as i mentioned before, a lot of those techniques to make it that, are a lot of illegal in most of the western world. Regards

cjdml update has been accepted.

The way it is worded when you submit a file, it seems like saying to clients "oh just register at my site, i'll give you access to the forbidden update to my app" would be "promoting" my site/store, where i do offer different deals and possible discounts and what not to my apps that are also available here. I edited this section and the quote above to remove information that could be misused to cause damage to applications installed, if the action was done improperly.