Announcement

Collapse
No announcement yet.

Ban User for AdminCP broken

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • [Bug / Issue] Ban User for AdminCP broken

    In my admin CP the ban user and view banned users links go to https://mysite.com//banning.php. The one in ModCP works fine as it links to https://mysite.com/modcp/banning.php.

    Any idea how to fix this?

  • #2
    Both locations actually link to the same file.

    When you upgraded to 5.5.6, did you delete the /admincp directory? And if so, are you using the .htaccess file that shipped with 5.5.6?
    Translations provided by Google.

    Wayne Luke
    The Rabid Badger - a vBulletin Cloud demonstration site.
    vBulletin 5 API - Full / Mobile
    Vote for your favorite feature requests and the bugs you want to see fixed.

    Comment


    • #3
      We actually migrated servers but kept the SQL database so 5.5.6 was a fresh file install and it upgraded the database. Also, we are using the .htaccess file that came with the install. This seems to be the only links in the admincp that are broken.

      Comment


      • #4
        So I saw this down below the related topics and this is the exact thing for me. Didn't show in my search results though.

        https://forum.vbulletin.com/forum/vb...r-broken-links

        It seems leaving it blank with '' breaks the banning as the install showed the default was 'modcp' might be a bug in the code that specifically calls for that path without using the default if none is specified.

        Comment


        • #5
          I can't recreate this. My installs properly link to /modcp/banning.php from the AdminCP. That is how it is supposed to work.

          What do you have for the modcp value in the /core/includes/config.php file?

          See: https://forum.vbulletin.com/forum/vb...68#post4363368

          Originally posted by Grouper View Post
          It seems leaving it blank with '' breaks the banning as the install showed the default was 'modcp' might be a bug in the code that specifically calls for that path without using the default if none is specified.
          The default needs to be specified in the code. Leaving it blank does indeed break the links. This is not a bug. It is how the system was designed in 2004. This has never changed.

          Translations provided by Google.

          Wayne Luke
          The Rabid Badger - a vBulletin Cloud demonstration site.
          vBulletin 5 API - Full / Mobile
          Vote for your favorite feature requests and the bugs you want to see fixed.

          Comment


          • #6
            it was blank because it said the default was modcp. It works now that I put a value in it. I guess the documentation is just misleading stating there is a default when there isn't.

            Comment


            • #7
              If you're talking about the makeconfig.php file, it means enter the word modcp since that is the default when the software is shipped. That the value is even there is a carry over from vBulletin 4 when site owners could change the page to give themselves a false sense of security.

              When doing an upgrade from vBulletin 4, you should never see the makeconfig.php and should manually edit the config.php files. When doing an upgrade from vBulletin 5.x, the config.php files should already exist and should not need to be edited.
              Translations provided by Google.

              Wayne Luke
              The Rabid Badger - a vBulletin Cloud demonstration site.
              vBulletin 5 API - Full / Mobile
              Vote for your favorite feature requests and the bugs you want to see fixed.

              Comment

              Related Topics

              Collapse

              Working...
              X