Recent content by MaGeFH

You could create a parent addon that‘s a dependency of both addons and provides the shared functionality. That way you don‘t have to duplicate the code and still keep it „dry“.

This happens when the importer step fails to set a new value for $step->start_at. Make sure it gets set properly.

I don't think entirely removing that part could be considered "fixing" it. :p

@Chris D I digged into the router code (src/XF/Mvc/Router.php on line 834) a bit and could fix the problem by replacing this: $findReplacements[$placeholder] = '(/?)'; with that: $findReplacements[$placeholder] = '(/|$)';

IMHO, it seems absurd not to use it. ;) But, you don't have to. Just create the directory in /src/addons/ and place a valid addon.json inside. Then you should be able to install the new blank add-on in your backend.

I have not yet looked under the hood of searching and indexing in XF2, but I would assume that you apply a strip_tags funcion call before inserting your data to the search index. :)

We are riding the bleeding edge here... :eek::LOL:

Mayba I should have searched the resolved bugs, too... :unsure: :notworthy:

Just noticed that when a select with a size attribute contains more content than it's size allows, it's not possible to scroll without moving the selection via the cursor keys. The is caused by the overflow: hidden rule on the select.input selector defined in core_input.less. You could...

We stopped waiting and did it ourselves. We did automate a large part and used an XF1.5 translation to proof comparable phrases. Not perfect, but working well enough for us. And it makes for some very funny discoveries like "Root breadcrumbs" -> "Wurzelbrotkrümel" 🤣

It's possible to do this for XF2 with an addon. We are using one internally that does that in addition to CSS source-mapping and some other useful stuff. :) However, it's not really possible to cover everything. Some phrases are used in title attributes, some are for javascript, etc. You can't...

@Sim Yeah, I was referring to Integration tests. Got a bit mixed up on that. 😊

An official API! Finally! *sigh of relief* Now we can really start to upgrade our website-management system. 😁 This is fantastic news, really. Loving it! 🎉

That's not correct. If you develop an addon you could use the default tests (with hooks enabled) to test if your code has any negative impact on standard forum behavior that you might have missed. This happens a lot. ;) Really? I can't imagine any scenario that would be problematic.

First: Nice to see this coming to the core. I think this will spawn a lot of interesting addons. :) My 2 cents concerning positive or negative ratings with increasing value: If you do this, you essentially de-value the reactions that don't have a maximum impact. Even if the associated reaction...