Recent content by NikitOS

You can put your files in the _no_upload directory: it will not be included in the addon build. If this method is not suitable, you can remove the files during the build process by executing the appropriate command. For example, let's remove the test.txt file from the add-on root: { "exec"...

At the moment, styles only have an auto-incrementing numeric identifier. It would be nice if the developer of the style could also specify their own string ID for the style, like addon IDs (but without the uniqueness requirement, of course). In some cases this can be useful, for example: To...

There is a typo in the exception message in the XF\Mail\Mailer::renderMailTemplate function: "Template mail:$name did not render to anything. It must provide either a text or HTML body." The template prefix must be email:.

The xf-addon:bump-version command overwrites the addon.json file with the new version, but the json_encode function escapes Unicode, so values with Unicode characters become unreadable. Before: "extra_urls": { "Тест": "https://example.com/" } After: "extra_urls": {...

@Dkf, there can be not only posts in the approval queue, but also users, threads, etc. Please provide the result of this request to determine if there is anything other than posts: SELECT DISTINCT content_type FROM xf_approval_queue In any case, you can clear the xf_approval_queue table to clear...

This option is located in inline moderation:

It seems to me that it is necessary to prohibit the deletion of cron, xfUpgradeCheck, fileCheck and xfCollectStats jobs, if not always, then at least when the developer mode is disabled, so that users do not break anything.

There is an outdated link in the phrase you_can_preview_icons_and_their_names_here. New link: https://fontawesome.com/v5/search.

And it must extend XF\Admin\Controller\AbstractController, not public.

If you want to allow style change for all registered users, you can replace MV\CForceUserStyle\XF\Entity::canChangeStyle with this: public function canChangeStyle(&$error = null) { return $this->user_id && parent::canChangeStyle($error); }

@styui, I think this add-on solves the problems that @Anatoliy had. Regarding your question: isn't this behavior out of the box? Guests see the default style and it will also be selected from them during registration. An exception is a style change by a user while he was a guest.

I have an add-on that changes the cost and currency for all payment providers and it changes those values in the insertPurchaseRequest repository function, and there is no problem with any payment providers.

For cost to display? At that time, it is not clear what the cost will be, because several payment profiles can be used for the purchase. In any case, you can get the desired payment profile through the finder. No.

In addition to the above extension, you need to extend XF\Data\Currency::languageFormat and change the value variable.

You can extend the XF\Repository\Purchase class and change the cost in the insertPurchaseRequest function. public function insertPurchaseRequest(XF\Purchasable\Purchase $purchase) { $purchase->cost = 123; return parent::insertPurchaseRequest($purchase); }