This issue is commonly seen by users who run their own servers or VMs.  The easiest fix is to place an entry in your hosts file (linux: etc/host) pointing your domain to the local IP address. eg: 10.0.0.168  yourdomain.com The reason the error occurs is because the webserver is converting a URL call to a… Continue reading Clicking An Attachment Results In A White Screen (Or A Message Indicating The File Is Corrupt)

You will see this error in your error.log file if the WordPress debug flags are turned on.  This is because you are using a PHP version earlier than 5.6.30.  The minimum php version we support is 5.6.30.

This happens because new WordPress security capabilities were introduced in version 4.0.0.  If you are using roles that are not standard Awesome Support roles then you might need to modify them to include the additional capabilities: Here are the new capabilities that were added to Awesome Support 4.0: For admins and similar users: ‘view_all_tickets’  (Set this only… Continue reading Missing Tabs or Menu Options After Version 4.0 Upgrade

This can occur for a variety of reasons.  Try any of the following: If you have the POWERPACK/Productivity add-on installed, check to see if the capability edit_ticket_with_full_editor has been assigned to your role.  If so, remove it.  It means that the using the advanced editor for replies is incompatible with your installation. Add this to your wp-config.php… Continue reading Ticket Reply Editor is Disabled and/or You Get A Message That Reply Cannot Be Blank

If emails are not being retrieved, one reason could be that an error is being thrown.  You can turn on the WordPress error logging flags and check the debug.log file to see if a related message is logged in there. If the error message in the log file includes “Malformed Header” as part of the… Continue reading EMAIL PIPING: “Malformed Header” shows up in debug.log and emails are not retrieved

You might sometimes see a vertical line in the middle of your fields on the SUBMIT TICKET page.  You can try adding the following CSS to your DIVI custom css field (DIVI->THEME OPTIONS) to remove this line: .wpas-submission-form-inside-after-subject.container::before { display: none; }

When Awesome Support is installed on the Avada Theme, you sometimes see strange behavior with drop-downs that require searches – eg: the SUPPORT agent drop-down.  This is usually because Avada and Awesome Support are using different versions of the same library (a library named SELECT2). A possible resolution is to enable the full version of… Continue reading Resolving Conflicts With The AVADA Theme