Recent content by gigipmc

Integration news: Job System by Olakunlevpn now integrates the wallet as a withdrawal method, in addition or as an alternative to DragonByte Credits.

Sale: Buy this add-on and get the Atlos.io Crypto Payment Provider add-on for free. Sign up at XFCoder.com, top up your wallet and receive a 50% bonus, which you can then use to purchase both products.

As far as I see the account you have created is pending email confirmation, please confirm your email address and go ahead with the purchase. If there is an issue with that please DM me here on xf.com.

@Wishingz you have not completed your user registration on the site, please complete the registration or create a new user and then go ahead with the purchase.

The wallet can be used as a payment method to purchase items at the RM Marketplace, but it currently cannot be used as a withdrawal method, since the withdrawal mechanism is unique to that add-on. The required changes in the wallet add-on so as to make it work as a withdrawal method are minimal...

The prefix text is actually an XF phrase, so alphabetical sorting isn't straight forward code wise and will take a toll on performance (page loading time). Filtering by prefix is a different story since that's just the prefix ID in play.

I use Atlos.io and the add-on that I myself programmed :) https://xenforo.com/community/resources/xfcoder-atlos-io-crypto-payment-provider.9627/ Also optionally check out the on-site wallet if you want an on-site credit system (users can top it up with the crypto add-on).

Yes that works :) by far the easiest solution. Should be used within the node_id conditional while extending: XF\Pub\Controller\ForumController\actionForum() XF\Pub\Controller\ThreadController\actionIndex()

I looked into it again, I mentioned controllers but that's inaccurate. There are 2 elements to handle for censoring: the thread title and the thread posts content. For the title, in the thread entity structure, the 'title' column has censor set to true. You can conditionally set it to false...

You can do the node check in the controllers instead (which is the proper way to do it) and then the node ID is readily available, but that obviously requires more code extensions.

It's available on the page but it's not available to the censor method which is 'page agnostic', which is why we forcefully fetch the parameter bag. I can't debug on the actual add-on since it's behind a paywall :)

On your installation, can you debug and check the value of $parameterBag->node_id on the relevant page? I tested it here and it returns the proper node_id. It could be some other issue rather than the node_id detection..

Replace the method in the above post with this: public function censorText($string, $censorChar = null) { $app = \XF::app(); $options = \XF::options(); if ( $excludeForumId = $options->ozzmodz_email_convo_monitor_node ) { $routeMatch =...

The add-on is now supported as a payout method in the RM Marketplace.

gigipmc updated XFCoder :: Latest XF Threads Widget for WordPress with a new update entry: 1.0.4.3 Read the rest of this update entry...