You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some wikis are setup using the ShortURLS format where actions (e.g. &action=edit) can be handled via a pretty url(e.g https://wiki.site/edit/Page_Name). It seems like for wikis using this format this extension cannot create pretty URLs (whilst the traditional urls might work it defeats the purpose of having pretty urls).
This setup makes use of the re-write functionality in the webserver e.g.
It might be good if the extension could allow for such a configuration, maybe by looking to see if the relevant $wgActionPaths config options are set (the default article path should be in $wgActionPaths['view']
The text was updated successfully, but these errors were encountered:
* Use AbuseFilterShouldFilterAction hook for Flow actions (kulttuuri#16)
* Use AbuseFilter hook for Flow actions
* build: Add AbuseFileter as a dependency
* Add a type check for UUID
* Do not ruin Flow\Tests\Api\Api*Test
(cherry picked from commit da9123b)
* Remove links syntax from Flow topic titles
(cherry picked from commit 7892b54)
* Reflect breaking changes of AbuseFilter for MW1.36
* Cleanup phpcs errors
* Fix Phan errors
* Fix failed phpcs tests
Some wikis are setup using the ShortURLS format where actions (e.g.
&action=edit
) can be handled via a pretty url(e.ghttps://wiki.site/edit/Page_Name
). It seems like for wikis using this format this extension cannot create pretty URLs (whilst the traditional urls might work it defeats the purpose of having pretty urls).This setup makes use of the re-write functionality in the webserver e.g.
the wgActionPaths config option within media wiki e.g.
This allows for the following urls
Other actions may still use the
?action=
like: https://wiki.evergreencoin.org/w/index.php?title=Main_Page&action=watchIt might be good if the extension could allow for such a configuration, maybe by looking to see if the relevant
$wgActionPaths
config options are set (the default article path should be in$wgActionPaths['view']
The text was updated successfully, but these errors were encountered: