When placing an order, the order shows up in your Shopp order menu, but your customer does not receive an email, nor does the shop owner. When attempting to send a message from a Shopp Order, the message is not received.
This could come from several factors including misconfigured host, over taxed email server or SPAM filters. To determine if the cause is your hosting provider, first confirm that WordPress can send emails.
- New user account notifications
- Password recovery notifications
- New comment notifications
If WordPress is successfully sending the above notifications, then the problem is not likely with the server.
Contact your hosting provider to find out what steps must be taken to send emails from php successfully on your site.
Bad Merchant Address
Some hosting providers do not permit sending an email that is address from a different domain name than your site’s domain name.
For instance: Your website address is superiorsprockets.com, but your merchant email address is set to firstname.lastname@example.org in your wp-admin → Shopp → Settings page.
Many hosting providers will permit you to create email aliases that have a matching domain name to your site.
Example: email@example.com could be setup to direct mail to firstname.lastname@example.org. Contact your hosting provider to determine if this is possible.
If it is not possible, make-up a fake email address at your domain name, such as email@example.com. This will at least permit emails to be sent to your customers, if not to you. You may be able to create a Bcc: firstname.lastname@example.org entry in the header of your order.php and notify.php email templates, to workaround this problem.
Invalid Email Templates
By default, Shopp comes with several template PHP files that are used to create the automated email messages you and your customers receive.
If you have made modifications to any of these three files, your modifications could potentially be causing the email failure.
When you modify your files with your text editor in Windows, the line ending characters may be replaced with Carriage-Return/Line Feed characters (CRLF), replacing the original Line Feed ending (LF). If your text editor has a setting to control the line ending characters, set it to save only LF character line endings.
In addition, your FTP program may translate these line endings when you upload your modified template file to the server. If your FTP program has the option of uploading in Ascii (Text) mode or Binary mode, select Binary. This will ensure that your line endings are not translated when the file is uploaded.
For translated websites, often the header lines in your order.php and notify.php files will be improperly translated. These fields at the very top of your template, displayed as:
Content-type: text/html; charset=utf-8 From: [from] To: [to] Subject: [subject]
This header information should not be altered, unless you are hard-coding the From: field, or adding a Bcc: header. Do not translate these headers into your language.
Rename or delete your order.php, notify.php, and receipt.php template files located in your wp-content/themes/your-theme/shopp/ directory, and reinstall them from WordPress Admin Page → Shopp → Settings → Presentation.
- Unable To Save Products With Large Amount of Variations
- Shopp Compatibility List
- SuPHP Permission Issues
- Issues with WordPress MU Domain Mapping Plugin
- Activation Fails With Blank Page
- Error: open_basedir Restriction in Effect.
- CURLPROTO FILE Cannot Be Activated
- Permalink Issue Results in 404 Error
- Find Full File Path
- Download Failed due to Bad Request or Not Authorized