Read This Before Requesting Support.

Collapse
This topic is closed.
X
This is a sticky topic.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Wayne Luke
    vBulletin Technical Support Lead
    • Aug 2000
    • 73981

    Read This Before Requesting Support.

    Every support request should be in its own topic. Do not take over the support topics posted by others. The only thing that happens when you do this is make it more difficult to receive support.

    Often times we get threads like:

    I tried to upload an image and it didn't work. How do I fix this?
    This type of question is very difficult to answer because it provides no real information. vBulletin runs on thousands of server configurations and can be extremely customized. We need to know the details of your specific configuration in order to get your questions answered quickly. Please provide the following information:
    1. vBulletin Version - Viewable in the header of the AdminCP.
    2. PHP Version - Viewable on the AdminCP Home Page.
    3. MySQL Version - Viewable on the AdminCP Home Page.
    4. Any Addons installed.
    5. Does the issue occur in a default style?
    6. Does the issue occur using the English language provided?
    7. Error message on the screen.
    8. Browser and Browser version used.
    9. Did you clear the browser cache and did the error continue?
    10. A list of steps that can be used to recreate the issue.
    11. Output of the error with vBulletin in Debug Mode.
    12. If the issue is an Invalid Server (500 server error) response, the web server and PHP logs that correspond with its timestamp.
    You can find your MySQL version under Maintenance -> Diagnostics -> Server Variables -> MySQL Settings

    You can find your PHP version in the AdminCP under Maintenance -> View PHPInfo

    You can find your addons in the Admin CP under Hooks & Products -> Manage Products.

    To create a new default style go to Styles & Templates -> Style Manager and click Add New Style. Set "Parent" to none, give it a name and save.
    Last edited by Wayne Luke; Tue 9 Nov '21, 8:08am.
    Translations provided by Google.

    Wayne Luke
    The Rabid Badger - a vBulletin Cloud demonstration site.
    vBulletin 5 API
  • Wayne Luke
    vBulletin Technical Support Lead
    • Aug 2000
    • 73981

    #2
    How to determine the actual error on your site:

    1. Download and Install Google Chrome.

    2. Put your site into debug mode by editing your /config.php and changing the following line :
    PHP Code:
    $config['debug'] = false
    To:
    PHP Code:
    $config['debug'] = true
    3. Run Google Chrome. Press F12 to open the developer tools.

    4. Navigate to your site with the developer tools open.

    5. Click on the Network Tab in the Developer Tools.

    6. Recreate the error.

    7. On the network tab in the developer tools, scroll to the last request at the bottom and click on it. This will be your last API call.

    8. Copy the results from the Headers and Response tabs. Put them in your thread or ticket.
    Translations provided by Google.

    Wayne Luke
    The Rabid Badger - a vBulletin Cloud demonstration site.
    vBulletin 5 API

    Comment

    Related Topics

    Collapse

    Working...