Debugging
To troubleshoot issues with the AB Split Test plugin, you can use your browser’s developer (or JavaScript) console. Here’s how you can access the developer console on various browsers:
Apple Safari
Enable the Developer Menu
- Go to Safari Menu > Preferences.
- Select the Advanced tab.
- Check the box that says “Show Develop menu in menu bar”.
Open the Developer Console
- Click on Develop > Show JavaScript Console.
- Use the shortcut Option + ⌘ + C.
The console will open either within the existing Safari window or in a new window. Ensure the Console tab is selected.
Google Chrome
Open the Developer Console
- Open the Chrome Menu (three vertical dots) in the upper-right-hand corner.
- Select More Tools > Developer Tools.
- Use the shortcut Option + ⌘ + J (macOS) or Shift + CTRL + J (Windows/Linux).
The console will open within the existing Chrome window or in a new window. Make sure the Console tab is selected.
Mozilla Firefox
Open the Developer Console
- Click on the Firefox Menu (three horizontal lines) in the upper-right-hand corner.
- Select More Tools > Browser Console.
- Use the shortcut Shift + ⌘ + J (macOS) or Shift + CTRL + J (Windows/Linux).
The Browser Console will open in a new window.
Microsoft Edge
Open the Developer Console
- Open the Edge Menu (three horizontal dots) in the upper-right-hand corner.
- Select More Tools > Developer Tools.
- Press CTRL + Shift + i to open it.
The console will open within the existing Edge window or in a new window. Ensure the Console tab is selected.
Checking for Issues
Once you have the developer console open, look for any messages or warnings related to the AB Split Test plugin. These messages can provide insights into what might be going wrong and help you or our support team resolve the issue more efficiently.
If you find any errors or need further assistance, please provide the details or a screenshot of the console output, and our support team will be happy to help you debug the issue.
If you see no messages at all related to ab split test, please clear your website cache and try again