Semanticmediawiki: Incompatibility with Extension:Flow ?

[simontaurus]

I have encountered a strange problem within two independent Mediawiki installations. When the flow extension is enabled in LocalSettings.php before SMW, the parser functions of SMW are not registered when rebuildDate.php is called. This has the consequence that for example inline queries are misinterpreted as annotation.
For example, for the page text
{{#ask: [[Has part.Has part::Some part]] }}
an annotation error message
a property chain is not permitted during the annotation process
occurs. If the page content is recreated by a "purge" via webinterface instead, everything works correctly. If the loading order of Flow and SWM is reversed (first SMW then Flow), everything also works correctly (also via rebuildData.php).

Are there any known incompatibilities between the extensions or is this just a specific local problem?

Product | Version Wiki 1 | Version Wiki 2
-- | -- | --
MediaWiki | 1.31.6 | 1.31.12 (e3f6093) 16:13, 24 February 2021
PHP | 7.2.24-0ubuntu0.18.04.2 (fpm-fcgi)  | 7.1.33-34+ubuntu16.04.1+deb.sury.org+1 (apache2handler)
MySQL | 5.7.29-0ubuntu0.18.04.1 | 8.0.17
Semantic MediaWiki | 3.0.2 | 3.2.2
Flow | 1.1 (a6eab4d) 17:23, 25 July 2020 | 1.1 (e60a9b1) 12:35, 1 January 2021

[kghbln]

@simontaurus Thanks for reporting this issue. You are the first one to report this incompatibility.

Unfortunately I have no workaround for you at hand. Also I do not expect that this will be fixed on the end of SMW even if it turns out that SMW is the cause. The simple reason is limited man power here and at the same time Flow being a legacy software for years already which wlll probably be abandoned in the near to middle future in favour of the new discussion and replying tool if I am not mistaken.

[simontaurus]

Thank you for your reply. In fact, swapping the loading order is already a working workaround for me. However, the problem has cost me two days, which I wanted to prevent for others =)

[kghbln]

Thank you for your reply. In fact, swapping the loading order is already a working workaround for me.

Ah right. There is a way out. Good that you pointed this out! I documented this also on the troubleshooting page

However, the problem has cost me two days, which I wanted to prevent for others =)

This is the way to do it. Sadly it took so long. From experience I know that this not only happens with SMW from time to time - unfortunately.