Recent content by Xon

Under User Registration in the admincp, the "default registration values" section; (I've got quite a few add-ons which extend it)

I need a stack trace (not just the title of the error), and a list of add-ons installed.

Check the renewal price with what paypal says they paid. You need to grant yourself more permissions to get the "convert cart" permission.

Good to see you figured out a workaround. This is theme dependent, and is fairly annoying. The XF2 version uses a different system so it doesn't have the same issue.

I'm not 100% sure, but I got two moved forum alerts when I assume the thread had already been moved to the resolved bugs forum. https://xenforo.com/community/threads/approval-queue-does-not-use-same-action-method-standardization-as-rest-of-the-codebase.156128/ I can't tell if this was moved...

Also, your regex has a case insensitive match option but you are testing for img|IMG bbcode tags. Additionally, that regex will fail on the new XF2.1 [img] format. Example; [IMG align="left" width="337px" alt="PHP versions"]

You are mixing class extensions with static code event listeners. Adding a method to an entity class must be done via the class extension system.

Most callback locations standardize the method name via $method = 'get' . \XF\Util\Php::camelCase($offset); (ie entities or controllers), but approval queue does not, it uses $method = 'action' . ucfirst($action); which is unexpectedly different. Worse, LogicException: invalid_method is thrown...

My User Essentials add-on (XF1 and XF2) support public username change lists, in addition to allowing individual username changes to be marked as private.

I work in IT, using beta code in a live environment is a fact of life. The difference between a version stamp of "1.0.0" and "1.0.0 beta' is basically non-existent. The version string sadly has very little to say on how production ready code actually is.

XF1 at least could get flaky if you don't have a flood limit of at least 1 second due to race conditions. Plus it prevents accidental double-posting

Probably should be string[]|string (ie an array of strings vs a single string) rather than an array of arbitrary items or strings.

Xon updated Sticky Any Post with a new update entry: 2.0.7 - Bugfix update Read the rest of this update entry...

Do not show "Sticky Post" option unconditionally when creating a thread

No, I do not believe it would