Resolving Common Portal Errors
This article helps you troubleshoot common errors in the TargetX Portal.
Issue/Error |
Resolution |
---|---|
Extra white space on Portal |
Cause: Using the Video Widget to implement CSS or Google Analytics. DISCLAIMER: This CSS tag is not supported or maintained by TargetX, and is simply meant as an example of how you may choose to use CSS within our products. Some or all of the customizations these tags provide may change or no longer apply to your instance at any time. If at any time the CSS impedes expected functionality in the TargetX product, our recommendation will be for you to remove the CSS to regain functionality. Add the following Style code into the Video Widget in Portal Builder: <style> |
'Duplicate Field Selected' error in Portal | If a custom field is created that duplicates a field name in the Base package, you may encounter issues with your Portal. It is important to ensure that any custom fields do not duplicate TargetX fields (excluding the namespace). If necessary, make changes to your custom fields to avoid conflicts. For example, if you wish to create a new 'Role' field, consider naming the field 'Custom Role' to prevent interference with the 'Role' object in the Base package. |
'Show Reply to Offer' Button not displaying on the Student Portal |
Issue: A student goes to view their Application Decision and pay the deposit but they cannot pay.
|
"You do not have permissions to view this page" error | Cause: This error is due to incorrect permissions. Resolution: Validate the user's permissions using either Permission Scanner or Permission Viewer. Pay particular attention to ensuring that the appropriate Visualforce Pages have been enabled for the profile. It is crucial to meticulously verify that all necessary permissions are correctly assigned to avoid any access issues or functionality limitations within the TargetX platform. |
Published Portal is blank and unable to save |
Console errors often mention method: "evaluateConditionalContent". (Example: "Visualforce Remoting Exception: unexpected token: 'FROM'" action: "TargetX_Base.XBuilder" method "evaluateConditionalContent") Conditional sections are often the primary cause of a malfunctioning Portal. To troubleshoot, carefully review your Condition Sets to confirm the following criteria are met:
Identifying the specific condition set that is causing the issue can be challenging. A recommended approach is to clone the original condition set. Then, systematically remove pages, sections, and individual criteria, followed by testing the publication. Once the Portal displays correctly, the problematic criteria will have been isolated to the elements that were removed. |
The institution logo isn't displaying in the Events Portal |
1. Validate that the Community Theme record has an Owner set to one of your Users. |
Login page is different on each of your portals | The Visualforce page utilized for self-registration and login remains consistent across each portal. However, the appearance is tailored through a Community theme record. The branding of your page can exhibit various images, header text, and other elements depending on the Site URL used to access the page. Create a default Community Theme and, based on the number of different themes you desire, you can create additional themes and apply them to your various Sites, Communities, or Portals. |
For details on viewing Console errors, see Troubleshooting using Console Mode.