AdminCP and ModCP both give "Invalid Page URL" in some settings panels

[lilfields]

I'm running vBulletin 5.2.4 Patch Level 2. The issue seems to be that the /admincp/ is missing from the URL in the control panel frame the AdminCP and ModCPs are using: mydomain.com//banning.php

Is there any way to fix this?

[glennrocksvb]

That was a known issue in earlier versions that I thought was already fixed in all instances.

The workaround for now is to open the link in new tab and then when you encounter a missing /admincp, add it to the URL. But if the URL with missing /admincp is a result of submitting a page (POST request), then you have no option but to edit the admincp php code to add it. Otherwise, you'll have to wait for it to be officially fixed (it has to be in JIRA bug report, though).

[Mark.B]

I can't replicate this on 5.2.4 at all.

Can you please download a fresh copy of the FULL 5.2.4 PL2 package from the members area, upload all the files taking care to overwirite what is already there, and then run the upgrade script.

[lilfields]

I can't replicate this on 5.2.4 at all.

Can you please download a fresh copy of the FULL 5.2.4 PL2 package from the members area, upload all the files taking care to overwirite what is already there, and then run the upgrade script.

I just did that this morning and it's still doing it.

[lilfields]

Anyone? It's been a solid month. I have even updated to 5.2.5 now and I still have the same problem

[Mark.B]

There isn't much else we can suggest, as we cannot replicate this issue.

Try uploading a fresh htaccess file....you need to take a copy of the existing one, and then rename htaccess.txt from the download package to .htaccess (note tha dot at the start) and upload that.
This will remove any custom rewrite rules you may have in place.

Failing that, there may be some sort of custom URL rewriting going on at server level.

[lilfields]

I was able to solve this by changing out my config file in the /core/includes/ folder. Apparently this never updated and was stuck on 5.2.0. However despite this being fixed with the config file update, the pagination on the ban page is still broken, still showing just the root domain then /banning.php which results in a 404 page.