On one of several wikis I run RT 1.4.1 is misbehaving: if I enter some text I want to replace, it just re-loads the initial replace text page. When I enable debugging there are no entries in the log that seem related. PHP logs are not showing anything either. MW is 1.32.1 and 7.2.11 like the others where it works so probably unrelated. Does anyone else have a problem like this?
Topic on Extension talk:Replace Text
This ended up being because my domain/hosting was set up to redirect pages to www.<mydomain>; when I changed it to not redirect, it worked fine.
@Tenbergen Would you mind going into more detail about your solution? Do you happen to use Plesk Server for Domain Management? I started running into this problem recently myself after some issues with my Hosting Domain occurred. I'm using MediaWiki v1.41.
Yes, that wasn't very clear, sorry, and now I barely remember the details, but here it is. I use shared hosting, and the provider uses a web page to let me manage how my domain names lead to my wiki. By default, their setup turns e.g. https://mywiki.ca into https://www.mywiki.ca, ie it adds the www. I have is set up to do the opposite, turn any httpss://www.mywiki.ca into https://mywiki.ca. It appears that something got messed up behind the scenes when I made an unrelated change - the domain web page tool is not totally reliable, I have run into problems when I am impatient and open things in multiple tabs. So, something got messed up behind the scenes, and changed the ridirect setting. The rest of the wiki worked just fine that way, but replacetext didn't. Once I changed it back to how it was set up originally, and how localsettings expects it to be set up, it worked again.
Depending on how you have things set up, I could imagine a .htaccess file having a similar effect, but as I said, that'd me imagining :-) Hope that helps! Tenbergen (talk) 20:24, 15 December 2019 (UTC)
@Tenbergen I am wondering if perhaps you had the same problem as I did, and if this may have been an alternative solution: Topic:Vg8hqoqtliti4eru
@Naupe, you are right it sounds similar. I am kind of glad I was able to resolve the problem without editing the code of the extension, largely because I download updates for all extensions every few months, and editing one of them would mean always having to also edit it again. I am glad you found a solution!