Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
EE4 Archives | Page 3 | Page 3 of 5 | Event Espresso - Staging Server

Postmark App & Mandrill Transactional Email Handling Services

Monday, February 18th, 2013

Postmark (http://postmarkapp.com) and Mandrill (http://mandrill.com) are web services that provide peace of mind for all transactional emails that your website sends.

Both services offer officially supported WordPress plugins that you can use to integrate their services with your WordPress powered site.

wpMandrill

Introduction: http://blog.mandrill.com/own-your-wordpress-email-with-mandrill.html

WordPress.org plugin page: http://wordpress.org/plugins/wpmandrill/

Postmark Approved WordPress Plugin

Introduction: http://blog.postmarkapp.com/post/8778033288/wordpress-smtp-problems-are-solved-with-postmark

WordPress.org plugin page: http://wordpress.org/plugins/postmark-approved-wordpress-plugin/

Posted in | Comments Off on Postmark App & Mandrill Transactional Email Handling Services

Using CSS3 to style links

Wednesday, February 13th, 2013

Here is a short video tutorial that shows how you can change the appearance of text links and make them look like buttons:

[s2If current_user_can(access_s2member_ccap_vip_membership) OR current_user_can(access_s2member_level1)]

Resources:

CSS-Tricks Button Maker

WordPress Child Theme Basics

Jetpack’s Custom CSS

Firebug

Event Espresso’s CSS Classes

[/s2If]
[s2If !current_user_can(access_s2member_level1) OR !current_user_can(access_s2member_ccap_vip_membership)]
The page you are trying to access is reserved for Event Espresso licence holders and VIP members. Please purchase a licence, upgrade your support license for Event Espresso, purchase VIP access or log-in. VIP membership does not entitle you to the product download, products must still be purchased as part of a licence or separately. If you think you are receiving this message in error, http://staging.eventespresso.com/contact/contact us.
[/s2If]

Posted in | Comments Off on Using CSS3 to style links

How to Set Up PayPal IPN

Thursday, January 31st, 2013

IPN stands for Instant Payment Notification and in short it is needed for Event Espresso to be notified about the transaction in order to complete the registration on the website.

When setting up PayPal to work with Event Espresso you need to change the settings in the Plugin and in your PayPal account.

Already Set Up but Still Problems?

If your IPN is set up and you require some troubleshooting tips, please click here.

Plugin Settings

There are two types of settings, testing (also known as Sandbox or Debugging) and live.

With the testing settings you will first need to have a PayPal Sandbox account and enter your merchant email address in the PayPal ID option and make sure that the Use the Debugging Feature and the PayPal Sandbox option is ticked.

Any registrations taking place will now head to the Sandbox where no actual money changes hands. You will need to use a Sandbox buyer account details to make a purchase.

For live settings, add your own PayPal email address to the PayPal ID option and make sure that the Debugging Feature and the PayPal Sandbox option is turned off.

An important note about the “Force HTTPS on Return URL” setting:

Please only enable the “Force HTTPS on Return URL” feature if you have an SSL certificate installed for your domain. In most cases, you can order an SSL certificate from your hosting provider.

PayPal Settings

To set up your account to use IPN, log into your PayPal account and click the Profile link in the menu bar.

Click the My Selling Tools option in the left hand menu and then click the update next to Instant Payment Notifications.

On the next screen click the Choose IPN Settings button at the bottom of the page.

On the next page add the url to your Event Espresso notifications page, by default it will be http://www.yoursitename.com/transactions/

Make sure “Receive IPN messages (Enabled)” is enabled and click save.

Server Firewall Settings

If necessary, add PayPal’s IP addresses to any list of trusted IP addresses needed by your firewall or other network devices. Here is the current list of PayPal IP addresses.

Troubleshooting PayPal IPN

Make sure your PayPal account is verified.

Make sure that the 4 required pages in the Event Espresso General Settings are correct and have the correct shortcodes in them.

Make sure that the 4 required pages in the Event Espresso General Settings are publicly viewable and not set to private, draft or password protected.

Make sure there are no ‘maintenance mode’ type plugins active.

Please only enable the “Force HTTPS on Return URL” feature if you have an SSL certificate installed for your domain. In most cases, you can order an SSL certificate from your hosting provider.

If you are running the Bad Behavior plugin, you will need to whitelist the IP addresses of PayPal servers, and keep an eye on the Bad Behavior logs to stay up to date in case PayPal gateway adds or changes the IP addresses they use to notify your site.

If you are experiencing problems with incomplete payments, try the Simplified Transaction template. This can be added to your theme and activated on the Transactions page via the Page Attributes option. See this forum thread.

Check to see if you have outdated or incorrectly modified gateway files in wp-content/uploads/espresso/gateways directory. If so, temporarily rename that directory to force Event Espresso to use the default gateway files.

You can check the IPN log file for errors. The IPN log file is located on your server in the /wp-content/uploads/espresso/logs directory. You can FTP in or view the file using your host’s c-panel file manager.

Incomplete Payment Issues

If you are experiencing problems with incomplete payments, most often it has to do with problems reaching your Transactions page ([ESPRESSO_TXN_PAGE]) from the payment gateway.

You can download our special stripped down Transactions page template in the link below. Included in the zip file is a quick readme with installation instructions.

It is recommended that you try this template after verifying that IPN is turned on, your account is verified, you have a standard or business account (if using PayPal) and — most importantly — that your Transactions page is visible to the internet.

If you have confirmed these four things and you are still having issues with incomplete payments, you can try the download below.

Download Transaction Template

Posted in | Comments Off on How to Set Up PayPal IPN

How to Require Attendees to Agree to a Policy Before Being Allowed to Register

Thursday, January 17th, 2013

At times you may want potential attendees to agree to a certain policy, certain terms and conditions or even a refund policy, before allowing them to register for an event. This tutorial will show you how to use the custom registration form questions to create a checkbox for attendees to select before they can register.

The video is best viewed in high-resolution.


To Get Started:

1) Create a page where you detail your policy.

This could be any page. But you don’t want to add all the policy text to the registration page (although you could if you added it to a Group Description). Instead we’re just going to link to that page from the question on the registration page. That way you can maintain your policy without worrying about the effect on the registration process.

2) Create a custom question which asks the attendees to agree to the policy

Terms and Conditions Policy Question


Question fields:

  • Question: Title the question something similar to: “I agree to the Policy”
    • Add a hyperlink from the question to the policy page by adding a HTML hyperlink <a href=”http://example.com”>Policy</a>.
    • (optional) If you want to have the link to the policy page stand out a little, you can add a <strong> tag to the text (e.g. <a href=”http://example.com”><strong>Policy</strong></a>
  • Type: Select the type of question you want to display. We recommend a Check Box so that it requires the attendee to activate and agree to the question.
  • Values: You want the value/answer displayed to the user to be something similar to “Yes” or “Yes, I agree to the Policy” so they know they are specifically agreeing to the question.
    • (Optional) You can let someone answer “no” if you’d prefer.
  • Required: You can decide to force attendees to answer this question before they are allowed to finish the registration form.
  • Admin View Only: No
  • Required Text: The text you want displayed if they do not answer the question


3) Create or add the question to a question group

Terms and Conditions Policy Group


In order for a question to be added to an event, it must be included in a question group. The question can be added to an existing question group or you can create a new question group.

Select Question Group
4) Add the question group to an event

Once you’ve added the question to a question group, you need to activate that question group for an event. Update the event to apply the question group.

After updating your event you’ll then see that the question group is now added to the registration page and the text of the  Terms and Conditions Policy is now a hyperlink to the policy page.

Agree to Terms

 

Posted in | Comments Off on How to Require Attendees to Agree to a Policy Before Being Allowed to Register

How To Select a Website Developer

Sunday, January 13th, 2013

Selecting a website developer can be difficult, especially if you are not sure how to effectively grade a developers skills and abilities. This guide will help.

 

This article will redirect to http://staging.eventespresso.com/support/how-to-select-a-developer/

Posted in | Comments Off on How To Select a Website Developer

Payment Settings

Thursday, December 20th, 2012

Event Espresso version 3 Documentation for the Payment Settings

The Payment Settings options page has all the settings for every payment gateway that Event Espresso supports.

Payment gateways are split into two broad categories: onsite and offsite. Onsite gateways allow users to pay with their credit card without leaving your website. Offsite gateways, send the user to the payment gateway site to complete the transaction.

You will at first be faced with a lots of grey bars, with the payment gateway names on them. Clicking one will open it to show a green activation button. Click that and the gateway will become active and you will then need to add the appropriate details for the gateway.

The list below links to each payment gateways documentation where you can find set up instructions, troubleshooting and usage tips.

[s2If current_user_can(access_s2member_level2)]

 

[/s2If]

[s2If current_user_can(access_s2member_level2)]

AliPay, First Data Connect 2, WorldPay: Are no longer supported.

2Checkout

  • 2Checkout ID: Your unique ID number available from 2Checkout
  • 2Checkout Username: Your unique username available from 2Checkout
  • Country Currency: Select the currency you are using for your sales.
  • Bypass Payment Overview Page: If this is set as Yes, instead of the user having to select the payment gateway button it will redirect the user to the gateway directly.
  • ImportantThis should only be used when you have one payment gateway, which also must be an offsite gateway like PayPal. It is also highly recommended that you turn off the payment return option to avoid the user being looped back to the gateway if the payment fails.
  • Turn on Debugging Using the 2Checkout Sandbox: Allows you to purchase events using fake credentials in order to test the payment system.
  • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.
  • Button Image URL: This contains the default image supplied by Event Espresso. If you wish to use a different button, change the url here.
  • Current Button Image: A visual representation of the current button.

 

Back to top

Authorize.net AIM

  • Authorize.net AIM Login ID: Your Authorize.net AIM login ID
  • Authorize.net AIM Transaction Key: This can be obtained from your Authorize.net account.
  • Account uses Authorize.net development server: Allows you to purchase events using fake credentials in order to test the payment system.
  • Submit a test transaction: Check this if you are using the development server and wish the test the transactions.
  • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.
  • Display a form header: Tick this if you wish to see a header above the payment form.
  • Header Text: This is the text that will be displayed if the above option is ticked.

 

Back to top

ANZ

  • Merchant ID: Available from your ANZ account.
  • Access Code: Available from your ANZ account.
  • Secure Secret: Available from your ANZ account.
  • Bypass Payment Overview Page: If this is set as Yes, instead of the user having to select the payment gateway button it will redirect the user to the gateway directly.
  • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.
  • Button Image URL: This contains the default image supplied by Event Espresso. If you wish to use a different button, change the url here.
  • Current Button Image: A visual representation of the current button.

 

Note:

If you want to test your account, use the test credentials (the test Merchant ID always starts with the characters ‘TEST’. e.g., if your normal account has a Merchant ID of ‘ANZKANGAROO’, your test merchant ID should be ‘TESTANZKANGAROO’.)

Also, ANZ will provide you wish two Secure Secrets. You may use either one.

Back to top
Back to top

ATOS

  • Notes on Files and Permissions: In order for the Atos gateway to work properly, you will need to upload the files given to you by your provider to the folder matching your selected provider above. Eg, gateways/atos/mercanet/. The file called pathfile will need to be writable by your web server and the two files in gateways/atos/bin/ will need to be executable by your web server. The current implementation uses the Atos provided Linux executables. Please contact support if you are using a Windows server, and would like to sponsor development of a version that will run on your server. For more information on setting file permissions, see: http://codex.wordpress.org/Changing_File_Permissions

 

Back to top

Authorize.net SIM

  • Authorize.net Login ID: Your Authorize.net AIM login ID
  • Authorize.net Transaction Key: This can be obtained from your Authorize.net account.
  • Button Image URL: This contains the default image supplied by Event Espresso. If you wish to use a different button, change the url here.
  • Image URL: This is for your logo.
  • Relay Response URL: This shows the specific the URL to which the gateway should return the relay response for a transaction. This the page should be set in your Authorize.net account. Login to Authorize.net, goto Account > Response/Receipt URLs > Add URL and enter the following URL.
  • Relay Response URL:  e.g. http://www.ee3128.3.dev/?page_id=5
    • This URL can be changed in the “Organization Settings” page, by changing the Notify URL page option.
    • For complete information on configuring relay response, please refer to Reference & User Guides.
  • Account uses Authorize.net development server: Allows you to purchase events using fake credentials in order to test the payment system.
  • Submit a test transaction: Check this if you are using the development server and wish the test the transactions.  USE MD5 check to secure payment response: Use a secure algorithym for your payments.
  • Authorize.net MD5 Hash value: Required for the above to work. To configure an MD5 Hash value for your account:
    • Log on to the Merchant Interface at https://secure.authorize.net.
    • Click Settings under Account in the main menu on the left.
    • Click MD5-Hash in the Security Settings section
    • Enter any random value to use for your MD5 Hash Value. Enter the value again to confirm
    • Click Submit
    • ImportantMAY CAUSE LEGITIMATE PAYMENTS TO BE MARKED “INCOMPLETE”
  • This may be a problem, such as a mismatch, between the authorize.net and Event Espresso MD5 Hash value settings.
  • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.
  • Bypass Payment Overview Page: If this is set as Yes, instead of the user having to select the payment gateway button it will redirect the user to the gateway directly.
  • ImportantThis should only be used when you have one payment gateway, which also must be an offsite gateway like PayPal. It is also highly recommended that you turn off the payment return option to avoid the user being looped back to the gateway if the payment fails.
  • Current Button Image: A visual representation of the current button.

 

Back to top

Electronic Funds Transfer

  • Title: The title to display for the payment gateway.
  • Payment Instructions: Specific instructions on how to initiate the payment or terms.
  • Name On Account: The name on Your account
  • Bank Account #: Your account number
  • Bank Name: Your bank name
  • Bank Address: Your bank address

 

Back to top

Beanstream

  • Beanstream Merchant ID: Available from your Beanstream account.
  • Use Beanstream in Sandbox mode?: Allows you to purchase events using fake credentials in order to test the payment system.
  • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.
  • Display a form header: Tick this if you wish to see a header above the payment form.
  • Header Text: This is the text that will be displayed if the above option is ticked.

 

Back to top

Check(Cheque)/Money Order

  • Title: The title to display for the payment gateway.
  • Payment Instructions: Specific instructions on how to initiate the payment or terms.
  • Payable To: Who the check(cheque) should be made payable to.
  • Address to send Payment: Default is the address set in the Organization Settings section of the General Settings page. Change it here to override this.

 

Back to top

Eway

  • Eway ID: Available from your Eway account.
  • Eway username: Your Eway username.
  • Choose your region: Choose the correct location for your business.
  • The currency set for your region is: This will auto update when you select the Region and update the settings.
  • Image URL: Here you can upload an image to use as a logo on your payment page. Either type in the url or use the link on the far right of the field to use the WordPress Media Uploader.
  • Bypass Payment Overview Page: If this is set as Yes, instead of the user having to select the payment gateway button it will redirect the user to the gateway directly.
  • ImportantThis should only be used when you have one payment gateway, which also must be an offsite gateway like PayPal. It is also highly recommended that you turn off the payment return option to avoid the user being looped back to the gateway if the payment fails.
  • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.
  • Turn on debugging using the Eway Sandbox: Allows you to make test transactions.
  • Button Image URL: This contains the default image supplied by Event Espresso. If you wish to use a different button, change the url here.
  • Current Button Image: A visual representation of the current button.

 

Back to top

Eway Rapid 3.0

  • Eway Rapid 3.0 API Key: Available from your Eway account.
  • Eway Rapid 3.0 API username: Available from your Eway account.
  • Eway Rapid 3.0 API password: Available from your Eway account.
  • Choose your region: Choose the correct location for your business.
  • The currency set for your region is: This will auto update when you select the Region and update the settings.
  • Use Eway Rapid 3.0 in Sandbox Mode: Use this for testing transactions. Remember to turn it off before accepting live transactions.
  • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.
  • Display a form header: Tick this if you wish to see a header above the payment form.
  • Header Text: This is the text that will be displayed if the above option is ticked.

 

Back to top

E-xact

  • E-xact Login ID: Your Authorize.net AIm login ID
  • E-xact Transaction Key: This can be obtained from your Authorize.net account.
  • Button Image URL: This contains the default image supplied by Event Espresso. If you wish to use a different button, change the url here.
  • Image URL: This is for your logo.
  • Relay Response URL: This shows the specific the URL to which the gateway should return the relay response for a transaction. This the page should be set in your Authorize.net account. Login to Authorize.net, go to Account > Response/Receipt URLs > Add URL and enter the following URL.
    • Relay Response URL: http://www.ee3128.3.dev/?page_id=5
    • This URL can be changed in the “Organization Settings” page, by changing the Notify URL page option.
    • For complete information on configuring relay response, please refer to Reference & User Guides.
  • Account uses E-xact.com’s development server: Allows you to purchase events using fake credentials in order to test the payment system.
  • Submit a test transaction: Check this if you are using the development server and wish the test the transactions.
  • Bypass Payment Overview Page: If this is set as Yes, instead of the user having to select the payment gateway button it will redirect the user to the gateway directly.
  • ImportantThis should only be used when you have one payment gateway, which also must be an offsite gateway like PayPal. It is also highly recommended that you turn off the payment return option to avoid the user being looped back to the gateway if the payment fails.
  • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.
  • Current Button Image: A visual representation of the current button.

 

Back to top

First Data

  • First Data Store Number: Available from your First Data account.
  • Accepted Credit Cards: Choose whihc credit cards you would like to accept by ticking the appropriate boxes.
  • Use Verify Peer Option in cURL: In the call between your server and firstdata’s servers, there is an option to verify the ssl certificate of the firstdata server. Normally, you would want to use this for improved security. However, if the CA file on your server is missing or out of date, then you may want to bypass this check, in order to get the First Data gateway to function.
  • Turn on Debugging using the First Data sandbox: Allow test transactions.
  • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.
  • Display a form header: Tick this if you wish to see a header above the payment form.
  • Header Text: This is the text that will be displayed if the above option is ticked.
  • Attention!Place the .pem file in the following folder. Make sure the .pem file has the same name as your store number: www.yoursite.com\wp-content\plugins\event-espresso\gateways\firstdata. First Data uses a special file to help authenticate and secure transactions. In order for the gateway to function correctly you need to place the provided .pem file in the location above.

 

Back to top

First Data E4

  • First Data E4 Payment Page ID: Available from your First Data account.
  • First Data E4 Transaction Key: Available from your First Data account.
  • Button Image URL: This contains the default image supplied by Event Espresso. If you wish to use a different button, change the url here.
  • Image URL: This is for your logo.
  • Relay Response URL: This shows the specific the URL to which the gateway should return the relay response for a transaction. This the page should be set in your Authorize.net account. Login to Authorize.net, goto Account > Response/Receipt URLs > Add URL and enter the following URL: Relay Response URL: http://www.ee3128.3.dev/?page_id=5
    • This URL can be changed in the “Organization Settings” page, by changing the Notify URL page option.
    • For complete information on configuring relay response, please refer to Reference & User Guides.
  • Account uses First Data E4’s development server: Allows you to purchase events using fake credentials in order to test the payment system.
  • Submit a test transaction: Needs to be ticked alongside the above option, if you wish to use test transactions.
  • Bypass Payment Overview Page: If this is set as Yes, instead of the user having to select the payment gateway button it will redirect the user to the gateway directly.
  • ImportantThis should only be used when you have one payment gateway, which also must be an offsite gateway like PayPal. It is also highly recommended that you turn off the payment return option to avoid the user being looped back to the gateway if the payment fails.
  • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.
  • Current Button Image: A visual representation of the current button.

 

Back to top

Google Wallet

Google Wallet Settings Instructions

Setup your Google Wallet merchant acccount here.

You will find your ‘Merchant ID’ and ‘Merchant Key’ in Google Wallet’s management area, by clicking “Settings”, then “Integration”. You must enter them into Event Espresso’s ‘Google Wallet (Checkout) payment settings.

On the Google Wallet (Checkout) Settings Integration page, set the ‘API callback URL’ in Google Checkout to the following:http://ee-3133-fresh.dev?type=google_checkout (a page on your website with an added GET query parameter of ‘type=google_checkout’). Leave the “Callback Contents” as “Notification Serial Number”.

Set the API version to 2.5, and check the box under “Notiication Filtering” stating ” I am integrating using the Order Processing Tutorial documentation and will receive and handle only the following notifications: new-order-notification, authorization-amount-notification, order-state-change-notification.”.

Lastly, don’t forget to save your settings in both Google Wallet (Checkout) AND Event Espresso’s payment settings page.

  • Google Merchant ID: Available from your Google Wallet account.
  • Google Merchant Key: Available from your Google Wallet account.
  • Select the currency for your region: Select your currency from the available options.
  • Use the Debugging Feature and Google Wallet Sandbox: This will enable you to make test transactions. Remember to turn it off before accepting real transactions.
  • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.
  • Default Payment Status on Receipt of ‘New Order Notification’: Google does not confirm the payment has been accepted straight away, on average it takes 15 minutes but can be quicker or take longer. This option sets what you show to the customer after they have completed the transaction. By default it is the more technically correct Pending, but this may confuse customers. Setting it to Complete may reduce queries, but if there payment is rejected you may need to explain why it was marked as complete.

 

Back to top

iDEAL by Mollie

  • Mollie Partner ID: Available from your Mollie account.
  • Use iDEAL in test mode: Selecting this will mean only test transactions go through, live transactions will not occur. YOu need to make sure that test mode is enabled in your Mollie account as well.
  • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.

 

Back to top

Invoices

  • Title: The title to display for the payment gateway.
  • Invoice Instructions: Specific instructions on how to initiate the payment or terms.
  • Payable To: Who the invoice should be made payable to.
  • Address to send Payment: Default is the address set in the Organization Settings section of the General Settings page. Change it here to override this.
  • PDF Settings
    • PDF Title (top right of the invoice): allows you to change the title in the PDF file.
    • Logo URL: Add an image url to insert a logo into the PDF.
    • Invoice instructions on the PDF: Specific instructions on how to initiate the payment or terms.
    • Show as option on the payment page: Default is Yes. If turned to No it will hide the invoice option from the payment page.

Troubleshooting Invoices

I am getting an error and tickets won’t download – If the error mentions a missing or incorrect image file such as “FPDF error: Missing or incorrect image file: http://www.yoursite.com/wp-content/uploads/espresso/ticketing/ticket-bg.jpg”, it is likely due to an incorrect server setting. You can either try amending your PHP.INI file or contacting your host to see and/or enable the “allow_url_fopen” option. You can also check if this is enabled or not by using a plugin such as WordPress phpinfo().

Back to top

Luottokunta

  • Luottokunta ID / Merchant Number: Available from your Luottokunta account.
  • Perform MAC security Check : Turns the MAC security check on or off (see below).
  • Secret MAC key: Available from your Luottokunta account.
  • Luottokunta Payment Page Language: Choose from a list of languages. This is not set by Event Espresso.
  • Bypass Payment Overview Page: If this is set as Yes, instead of the user having to select the payment gateway button it will redirect the user to the gateway directly.
  • ImportantThis should only be used when you have one payment gateway, which also must be an offsite gateway like PayPal. It is also highly recommended that you turn off the payment return option to avoid the user being looped back to the gateway if the payment fails.
  • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.
  • Button Image URL: This contains the default image supplied by Event Espresso. If you wish to use a different button, change the url here.
  • Current Button Image: A visual representation of the current button.
Luottokunta MAC Security Check

Using MAC calculation (MAC = Message Authentication Code) improves the security of the card payments in online store. Use of the MAC calculation is mandatory and the merchant must implement the MAC calculation in two phases in the HTML form interface. If the merchant does not use MAC calculation, the merchant will be responsible for any security risks and damages experienced by Luottokunta.

Luottokunta sends the merchant one secret key for the MAC calculation, enclosed in the service ID codes letter for Luottokunta ePayment Service, and this key is used for actual MAC calculation.

To Activate the Mac Security Check:

Log in to Transaction management section of the web interface of Luottokunta ePayment Service, using a merchant admin user or admin user ID.
Go to the page “Merchant settings”.
Enable the options “Add MAC check to HTML form” and “Add MAC check to Success_Url” (by marking them as checked).
Save your changes by clicking the button “Update”
Lastly, from within Event Espresso’s payments page, set “Perform MAC security Check” to “Yes” and click “Update Luottokunta Settings”

Back to top

Megasoft

  • Affiliation ID: This is available from your Megasoft account.
  • Button Image URL: This contains the default image supplied by Event Espresso. If you wish to use a different button, change the url here.
  • Current Button Image: A visual representation of the current button.
  • Account Uses Megasoft’s development Server: Allows you to send test transactions.
  • Display a form header: Tick this if you wish to see a header above the payment form.
  • Header Text: This is the text that will be displayed if the above option is ticked.

 

Back to top

Merchant Warrior

  • MW Merchant UUID: Available from your Merchant Warrior account.
  • MW API Key: Available from your Merchant Warrior account.
  • MW API Passphrase: Available from your Merchant Warrior account.
  • Select the currency for your country: Choose from a list of currencies. This is not set by Event Espresso.
  • Image URL: Type an URL or upload an image to act as your logo on the Merchant Warrior page.
  • Bypass Payment Overview Page: If this is set as Yes, instead of the user having to select the payment gateway button it will redirect the user to the gateway directly.
  • ImportantThis should only be used when you have one payment gateway, which also must be an offsite gateway like PayPal. It is also highly recommended that you turn off the payment return option to avoid the user being looped back to the gateway if the payment fails.
  • Use the Test Mode for Merchant Warrior: Allows you to send test transactions.
  • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.
  • Button Image URL: This contains the default image supplied by Event Espresso. If you wish to use a different button, change the url here.
  • Current Button Image: A visual representation of the current button.

 

Back to top

Moneris

The Moneris gateway requires some setting up in both the Event Espresso settings and your Moneris account before it can fully integrate with Event Espresso.

Moneris Hosted Paypage Configuration

Log into your Moneris account and navigate to the main Hosted Paypage Configuration page by clicking your configuration or after creating a new configuration.

Under Basic Configuration>Response Method you select Response Method: Sent to your server as a POST. You set the Approval and Declined URLS to the URL that’s the Event Espresso Thank You page. Then Save changes.

Image

Next step: Configure Response Fields.
Then click on the Configure Security button. You check the boxes next to the following items:

  • Return line item details.
  • Return billing details.
  • Return other customer fields. (cust_id, client_email, note . . .)
  • Return ECI value.
  • Return the txn_number. This field is used to perform follow-ons.
  • Automatically prompt cardholder for new card number on decline.

Image

Next Step: Configure Security. On the Security Features page under Referring URL, add full URLs pointing to the home page URL and for the main EE pages: registrations, transactions, thank-you. The cancellation page does not need to be added.

Add each one individually and click the Add URL button after adding the link to the input field.

In the Transaction Verification section, make sure that the Enable Transaction Verification checkbox is selected and then select Displayed as XML on our server from the list of available Response Methods.

After that, enter the full URL for the EE transactions page in the Response URL text input.

Finally click on the Save Verification Settings button.

Image

Event Espresso account settings

  • Moneris Hosted Pay Page Store ID (ps_store_id): Please see your Moneris account for this information.
  • Moneris Hosted Pay Page Key (hpp_key): Please see your Moneris account for this information.
  • Transaction Mode: Has three settings; Development – uses the Moneris testing servers to test payments; Dev + Debug – similar to Development but outputs data onto the website for easier debugging; Production – this is to be used if your site is live and taking real payments.
  • Moneris Canada or USA?: Set your country preference.
  • Language: Set your language preference between English and French. English is default.
  • Invoice Notes: Here you can add a default note that will appear on invoices.
  • Button Image URL: Use a custom button for Moneris on your Event Espresso payment page.

 

Back to top

NAB Transact Direct

  • NAB Merchant ID: This is available from your NAB account
  • NAB Merchant Password: This is available from your NAB account
  • Use NAB Transact Direct post in test mode?: This turns on the test mode to allow test transactions.

 

Back to top

Paychoice

  • PayChoice Username: This is available from your PayChoice account.
  • PayChoice Password: This is available from your PayChoice account.
  • PayChoice Currency Symbol: PayChoice currently only accepts AUD.
  • Use the Test Mode for PayChoice: Allows you to send test transactions.
  • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.
  • Display a form header: Tick this if you wish to see a header above the payment form.
  • Header Text: This is the text that will be displayed if the above option is ticked.

 

Back to top

[/s2If]

PayPal Standard

  • PayPal ID: Available from PayPal, normally your email.
  • Select the Currency for your country: Please choose the correct currency. Event Espresso does not set this.
  • Image URL: Type an URL or upload a file to act as your logo on the Paypal page.
  • Bypass Payment Overview Page: If this is set as Yes, instead of the user having to select the payment gateway button it will redirect the user to the gateway directly.
  • ImportantThis should only be used when you have one payment gateway, which also must be an offsite gateway like PayPal. It is also highly recommended that you turn off the payment return option to avoid the user being looped back to the gateway if the payment fails.
  • Shipping Address Options: Choose an option for whether a delivery address is required or not.
  • Use the Debugging Feature and the Paypal Sandbox: Allows you to send test transactions.
  • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.
  • Button Image URL: This contains the default image supplied by Event Espresso. If you wish to use a different button, change the url here.
  • Current Button Image: A visual representation of the current button.

Using PayPal Sandbox

The PayPal Sandbox is a method of testing payments for PayPal without actually having to pay something. PayPal’s sandbox documentation can be found here.

Setting up the PayPal IPN

We have a guide to help you set up your IPN (Instant Payment Notification) with PayPal. This can be found here.

Troubleshooting PayPal

Users cannot pay by credit card – This is a PayPal setting, check this handy image to find the correct setting.

Per-Event Settings

By setting fields in the Event Meta section of the event editor, you can override the global paypal settings, and direct revenue from an event to a separate account. This feature will not work with the Multiple Event Registration add-on registration process, however. The override fields are:

    • paypal_email

Image

Back to top
[s2If current_user_can(access_s2member_level2)]

Paypal Payments Pro

An SSL certificate is required to use PayPal Pro.

      • PayPal Payments Pro Email: The email you use for PayPal
      • PayPal API username: Available from your PayPal Pro account.
      • PayPal API Password: Available from your PayPal Pro account.
      • PayPal API Signature: Available from your PayPal Pro account.
      • Select the currency for your country: Choose the appropriate currency. This is not set by Event Espresso.
      • Accepted Credit Cards: Tick the boxes for the credit cards you wish to accept.
      • Use PayPal Payments Pro in Sandbox Mode: Allows you to send test transactions.
      • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.
      • Display a form header: Tick this if you wish to see a header above the payment form.
      • Header Text: This is the text that will be displayed if the above option is ticked.

 

Back to top

PayTrace

      • PayTrace User ID: Available from your PayTrace account.
      • PayTrace User Password: Available from your PayTrace account.
      • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.
      • Display a form header: Tick this if you wish to see a header above the payment form.
      • Header Text: This is the text that will be displayed if the above option is ticked.

 

Back to top

PsiGate

      • Canadian PSiGate Store Key (Merchant ID): Available from your PSiGate account.
      • US PSiGate Store Key (Merchant ID): Available from your PSiGate account.
      • Select the currency for your country: Choose the appropriate currency. This is not set by Event Espresso.
      • Luottokunta Payment Page Language: Choose from a list of currencies. This is not set by Event Espresso.
      • Use the Development Site: Turns on the test mode, no real transactions can be made whilst this setting is on.
      • Bypass Payment Overview Page: If this is set as Yes, instead of the user having to select the payment gateway button it will redirect the user to the gateway directly.
      • ImportantThis should only be used when you have one payment gateway, which also must be an offsite gateway like PayPal. It is also highly recommended that you turn off the payment return option to avoid the user being looped back to the gateway if the payment fails.
      • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.
      • Button Image URL: This contains the default image supplied by Event Espresso. If you wish to use a different button, change the url here.
      • Current Button Image: A visual representation of the current button.


Why is there a Canadian and US PSiGate Store Key?

If you will be accepting payments only in USD, you only need to enter a “US PSiGate Store Key”. Conversely, if you are only accepting payments in CAD, you need only enter a “Canadian PsiGate Store Key”.

If, however, some events will be accepting US dollars and others will be accepting Canadian dollars, you will need 2 PSiGate accounts: one accepting CAD and the other for USD. Enter the store keys for each into Event Espresso in the appropriate fields (“Canadian PSiGate Store Key” and “US PSiGate Store Key”).

Then, select a default currency. You may then specify an event as using the other currency by adding an ‘Event Meta’ called ‘event_currency’, and give it a value of either ‘USD’ or ‘CAD’.

When customers go to pay for an event, if the currency is in USD, your US Store Key will be used. If the currency for the event is CAD, the Canadian Store Key will be used.

Back to top

Purchase Order

      • Title: The title to display for the payment gateway.
      • Payment Instructions: Specific instructions on how to initiate the payment or terms.
      • Payable To: Who the invoice should be made payable to.
      • Address to send Payment: Default is the address set in the Organization Settings section of the General Settings page. Change it here to override this.

The Purchase order number will show on the attendee overview page.

Back to top

Quick Books

      • QuickBooks Connection Ticket: Available from your Quick Books account.
      • Use PTC (Development) Server: Use the test server to put through fake transactions. Remember to turn this off before allowing live transactions.
      • Display a form header: Tick this if you wish to see a header above the payment form.
      • Header Text: This is the text that will be displayed if the above option is ticked.

The Purchase order number will show on the attendee overview page.

How to Configure QuickBooks Merchant Services Payment Gateway

  1. First signup for a Merchant Services Account here
  2. After creating the account, click here to link Event Espresso to your QuickBooks Merchant Services account
  3. After you click on the previous link, enter your QuickBooks Merchant Services email and password.
  4. You will then be given a ‘Connection Ticket’, which you must copy and paste into the Field ‘Connection Ticket’ in Event Espresso’s QuickBooks Merchant Services payment settings field.
    (Note: if you change whether you’re using the PTC/Development server, you will need to re-acquire your connection ticket.)
  5. All done! Now just test that payments are working, and you’re done!

Back to top

QuickPay

      • QuickPay ID: Available from your QuickPay account.
      • QuickPay MD5 Secret: Available from your QuickPay account.
      • Payment Window Language: Choose a language which the payment screen will be displayed in.
      • Automatic Capture: Automatic Capture skips the bank authorization process and obtains the money directly. http://quickpay.net/features/autocapture/
      • Currency: Choose a currency for payments.
      • Turn on debugging using the Sandbox: Allows you to send test transactions.
      • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.
      • Button Image URL: This contains the default image supplied by Event Espresso. If you wish to use a different button, change the url here.
      • Current Button Image: A visual representation of the current button.

 

Back to top

RealAuth

      • Merchant ID: Available from your RealAuth account.
      • Shared Secret: Available from your RealAuth account.
      • Country Currency: Choose your countries currency.
      • Button Image URL: This contains the default image supplied by Event Espresso. If you wish to use a different button, change the url here.
      • Use the debugging feature: Turn on the debugging feature to allow you to find errors in the payment process.
      • Bypass Payment Overview Page: If this is set as Yes, instead of the user having to select the payment gateway button it will redirect the user to the gateway directly.
      • ImportantThis should only be used when you have one payment gateway, which also must be an offsite gateway like PayPal. It is also highly recommended that you turn off the payment return option to avoid the user being looped back to the gateway if the payment fails.
      • Auto settle transactions: Used to signify whether or not you wish the transaction to be captured in the next batch or not. If set to “Y” and assuming the transaction is authorised then it will automatically be settled in the next batch. If set to “N” then the merchant must use the realcontrol application to manually settle the transaction. This option can be used if a merchant wishes to delay the payment until after the goods have been shipped. Transactions can be settled for up to 115% of the original amount.
      • Current Button Image: A visual representation of the current button.

In addition to adding the Merchant ID and Shared secret, you will need to contact Realex support and give them a response URL (which is the page on your site with the [ESPRESSO_TXN_PAGE] shortcode. By default, it’s the page set as the notify URL in the Event Espresso>General Settings.

I recommend this documentation for additional info, there is a check-list on page 5 that may help you get up and running:
https://resourcecentre.realexpayments.com/documents/pdf.html?id=141

 

Back to top

Stripe

      • Stripe Secret Key: Available from your Stripe account.
      • Stripe Publishable Key: Available from your Stripe account.
      • Stripe Currency Symbol (USD): Defaults to USD, but as Stripe expands other currencies may become available.
      • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.
      • Display a form header: Tick this if you wish to see a header above the payment form.
      • Header Text: This is the text that will be displayed if the above option is ticked.

 

Back to top

USAePay Offsite

      • Key: Available from your USAePay account.
      • Button Image URL: This contains the default image supplied by Event Espresso. If you wish to use a different button, change the url here.

 

Back to top

USAePay Onsite

      • Key: Available from your USAePay account.
      • Use USAePay Development Server?: Use the test server to enable you to create fake transactions whilst tesrting your site. Make sure you obtain and use the Development Key rather than your own Key.
      • Submit a test transaction: Tick to enable fake transactions.
      • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.
      • Display a form header: Tick this if you wish to see a header above the payment form.
      • Header Text: This is the text that will be displayed if the above option is ticked.

 

Back to top

WePay

      • WePay Client ID: Available from your WePay account.
      • WePay Client Secret: Available from your WePay account.
      • Image URL: This contains the default image supplied by Event Espresso. If you wish to use a different button, change the url here.
      • Select the Account to use: Select the WePay account that you wish to use for Event Espresso.
      • Bypass Payment Overview Page: If this is set as Yes, instead of the user having to select the payment gateway button it will redirect the user to the gateway directly.
      • ImportantThis should only be used when you have one payment gateway, which also must be an offsite gateway like PayPal. It is also highly recommended that you turn off the payment return option to avoid the user being looped back to the gateway if the payment fails.
      • Turn on Debugging using the WePay Sandbox: Allows you to use test transactions.
      • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.
      • Current Button Image: A visual representation of the current button.

 

Back to top

WorldPay

    • WorldPay Installation ID: Available from your WorldPay account.
    • Button Image URL: This contains the default image supplied by Event Espresso. If you wish to use a different button, change the url here.
    • Image URL: This contains the default image supplied by Event Espresso. If you wish to use a different button, change the url here.
    • Select the currency for your country: Choose the appropriate currency. This is not set by Event Espresso.
    • Relay Response URL: This shows the specific the URL to which the gateway should return the relay response for a transaction. This the page should be set in your Authorize.net account. Login to Authorize.net, goto Account > Response/Receipt URLs > Add URL and enter the following URL: Relay Response URL: http://www.ee3128.3.dev/?page_id=5
      • This URL can be changed in the “Organization Settings” page, by changing the Notify URL page option.
      • Bypass Payment Overview Page: If this is set as Yes, instead of the user having to select the payment gateway button it will redirect the user to the gateway directly.
      • ImportantThis should only be used when you have one payment gateway, which also must be an offsite gateway like PayPal. It is also highly recommended that you turn off the payment return option to avoid the user being looped back to the gateway if the payment fails.
      • Turn on Debugging Using the WorldPay Sandbox?: Turns on the test mode, no real transactions can be made whilst this setting is on.
      • Force HTTPS on Return URL: Forces the gateway provider to send the customer back to the return page — or pull the return page from the site — using HTTPS. This is required in some instances to prevent a warning that the page the user is going to is not secure.
      • Current Button Image: A visual representation of the current button.

      Event Espresso version 4 Documentation for the Payment Settings (In Progress)

      This section allows you to set which forms of payments will be displayed to a user if the event has a price other than zero.

      Payment Methods

      This tab shows the core payment gateways and there settings.

      Clicking one of the gateways listed at the top shows the individual gateways activation option, and then the settings.

      A gateway must be activated before it can be used. A grey cog icon means the gateway is not active, a green coloured cog means the gateway is active.

      Settings

      This tab controls site wide gateway settings that span across different gateways.

      Allow Payment-retry for Pending and Deferred Payments
      If a payment is marked as ‘Pending Payment’, or if payment is deferred (ie, an offline gateway like Check, Bank, or Invoice is used), then give registrants the option to retry payment.

      [/s2If]

Posted in | Comments Off on Payment Settings

How to Change Languages

Thursday, December 20th, 2012

This how to will guide you through changing WordPress (single installation) and Event Espresso to use a language other than US English in the dashboard and front end.

Volunteers

Both WordPress and Event Espresso are translated by volunteers. As such translations may not be 100% accurate nor 100% complete. If you would like to help translate or validate a translation for Event Espresso, please contact us via this form. You can find out the current translation level of Event Espresso by checking this page.


Setting up WordPress

WordPress’ Own Guide

WordPress has a detailed guide on translating itself, which can be found here.


In order to allow WordPress to use a different language there are some steps you need to do. You will need FTP or hosting control panel access to accomplish this.

Start by heading over to the WordPress repository here and download a copy of the language files you are after. There will be two for each language/dialect – a PO and an MO file.

Important

Downloading the files from the WordPress SVN repo may not be intuitive. When you find the language you require:

Navigate down through your language, then down through “trunk”, then down through “messages”.


Via FTP find your wp-includes directory and create a new directory inside it called languages. Upload the PO and MO files there.

Navigate to the root (or appropriate location) of your site and find the wp-config.php. Firstly create a backup of the file by downloading it.

Edit the file and look for this code:

define ('WPLANG', '');

Edit that code with the appropriate language code in the following format and save.

define ('WPLANG', 'fr_FR');

That will change the language to French, so long as the French PO and MO have been uploaded to the language directory you created. If WordPress doesn’t find them, it will revert to its default US English.

Some more examples with comments

define ('WPLANG', 'en_GB'); #a dialect file, or English as I like to call it!
define ('WPLANG', 'fi_FI'); #Finnish
define ('WPLANG', 'es_ES'); #Spanish, note how it uses the international code for España
define ('WPLANG', 'nb_NO'); #Norwegian bokmål - another dialect.

Once you log into your WordPress dashboard or refresh, your WordPress installation will now be in French. If at first you don’t notice any translations, check the menu system as stated not all translations are 100% some are very low percentages indeed.


Translating Event Espresso

Multi-lingual Sites

At this time Event Espresso does not natively support multi languages (more than one language at the same time) though has been shown to work alongside WPML and qTranslate.


Version 3.1.29.1.P and newer

This version and up needs no further action once WordPress has had the language files installed. The plugin will automatically detect the language WordPress is using and serve the language file for Event Espresso if it exists.

Version 3.1.29.2.P and newer

From this version, Event Espresso does NOT ship with any language files other than the default US English. We decided to do this in order to make the plugin smaller, and quicker and easier to install.

In order to obtain the language files you will need to visit our Github page, and download the correct MO and PO files.

The plugin will automatically create a new directory located at wp-content/uploads/espresso and you will need to create a folder there called “languages’ and upload the languages files you got from Github to that folder.

Important

Downloading the files from Github may not be intuitive. When you find the language you require:

MO files – left click the link and then on the next page click the View Raw link in the middle.

PO files – are not generally needed so can be ignored.


Once the files are uploaded, as long as WordPress has been updated to accept a new language, Event Espresso will follow suit.

Further Reading

Translating Event Espresso

 

Posted in | Comments Off on How to Change Languages

Troubleshooting Checklist

Tuesday, December 18th, 2012

WordPress is amazing, as it is an open source platform. With that strength however, lies a problem in the fact that you have many plugins and themes, all trying to achieve different goals and all written by different people to wildly different standards.

So when problems strike, the first thing that needs to be done is some basic troubleshooting. This is useful not only for issues with Event Espresso, but any other plugins and themes out there.

These steps are in no particular order but you should try and work through them all in order to pinpoint the problem.

Theme

By disabling your theme and reverting back the default WordPress theme (Twentyeleven or Twentytwelve at the time of writing) you can see if your problem has been caused by a conflict or issue within your theme, as the default themes are coded to a high standard by the makers of WordPress itself.

If you cannot change themes due to the site being live or another reason, you can use a plugin such as Theme Test Drive to test the theme without your visitors being aware.

Plugins

De-activate all the plugins you have with the exception of the plugin that isn’t working correctly (in this case Event Espresso) and see if the issue is resolved. If not try the theme option as well.

If the issue is resolved, start activating your plugins, one by one, testing for the problem each time. With luck you will find the plugin that is causing the issue/conflict and be able to examine it in more detail or simply keep the plugin deactivated.

Javascript

Most conflicts with Event Espresso are down to Javascript: it is either being loaded incorrectly, an old version is being forced to load or something has stopped the Javascript from running. If you use Chrome or Firefox you can use the developer tools Console to pinpoint any blatant Javascript errors.

Also read here, for more Javascript troubleshooting.

Posted in | Comments Off on Troubleshooting Checklist

How to back up your site

Wednesday, December 5th, 2012

Whenever changes are made to your site, whether it be updating your theme, a plugin or WordPress core, it is highly recommended to backup your website.

There are two parts to backing up your site: 1) the Database and 2) the Files.

For the most part you will only need to back your database up when updating plugins, but it is recommended to do a full backup (database and files) on a regular basis.

How to Manually Backup Your Database

The best way to backup your database is by using phpMyAdmin from your hosts control panel (cPanel, Plesk, etc). This will enable you to get the entire database.


Using the built in WordPress exporter plugin will only back up the core database. If a plugin – like Event Espresso – uses its own database tables they will not be saved using the export function.

To manually backup your database using phpMyAdmin:

1. Log into your webhost’s control panel and log into phpMyAdmin

2. On the the main menu, either select your database from the list on the left or click the Databases link and select your database from the list that appears.


If you have several databases there and you are not sure which one you need to choose, you can find your WordPress database by looking at the wp-config.php file in your WordPress folder or your server root folder.


select your database

Select your database



3. You will now see a long list to the different tables available. This should contain your Event Espresso tables (prefixed by wp_events) and your general WordPress tables.

The prefix wp_ is a standard one but some hosts may use something else.

4. On the menu at the top click Export. This will show a couple of options and all your tables should be listed on the left.

The options are Quick and Custom. If you know something about databases you can click the Custom and tweak as needed, otherwise leave it as Quick. Below that is a dropdown for your export type, make sure it is on SQL (the default).

Then press the “Go” button. A pop-up will appear asking you to save the SQL file to your computer.

export the sql

Export the SQL file

That’s it, the database is now backed up.


Only the posts and comments and settings are backed up, your images and files (themes, plugins) are not backed up by this method.

Restoring Your Database

OK, so the reason you backup the database is so if something goes wrong you can revert back to a recently saved version. Here’s how to do that.

1. Log back into phpMyAdmin through your webhost’s control panel.

2. Select all the tables in your database, and in the drop down menu (With Selected) at the bottom, select “Drop”, then press “Go” in the bottom right of the screen.

This will delete your database! It is necessary in order to restore the previous backup, but if you are concerned, make sure your backup is valid and uncorrupted before doing this. You can also rename the database to something else and create a new blank database with the same name as the original.

3. On the top menu click “Import”. Under the “File” to Import section click the “Choose File” and select the “SQL” file you previously exported and click “OK”.

import sql file

Import the SQL file



4. Click the “Go” button.

5. Grab a coffee/tea/beverage of your choice.

 

Reference Material:

http://codex.wordpress.org/WordPress_Backups
http://codex.wordpress.org/Backing_Up_Your_Database

 

Plugins

If you don’t wish to do this manually there are several free and paid for plugins available that can back up your database for you.

http://wordpress.org/extend/plugins/wp-dbmanager/
http://wordpress.org/extend/plugins/backwpup/
http://ithemes.com/purchase/backupbuddy/

Posted in | Comments Off on How to back up your site

How to change wording and text with Poedit

Monday, December 3rd, 2012

It is often useful to be able to change the text or wording of something in Event Espresso in order for it to fit in with your site and audience better. You can hunt through the code to find the strings (text) to replace but there is a much, much easier and recommended way: use Poedit to change the language files.

What happens is you take the language file (in this example we will work with US English) and translate it, in order to change the text.

1) We recommend downloading and installing Poedit for working on translation files.

2) After you install Poedit, you can download a copy of the event_espresso-en_US.po file from our Github repository. Then you can open it in poedit.

Githubs downloading methods are not intuitive:

To download the PO file – left click the link on the main page and then right click the Raw button in the top right of the page that comes up and save as.

To download the MO file – left click the link on the main page, and then left click the View Raw text link in the middle of the page that comes up.

If you don’t do this you may end up with a MO and PO file that contains garbage data and the language wont work.

3) Use the Find tool to pull up the text string you need to modify.

4) Change the string as shown:

poedit

5) Save, then upload the newly generated .mo file to the wp-content/uploads/espresso/languages directory on your server.

6) Keep a copy of the modified language files saved somewhere in case you need to re-edit it or re-upload it.

7) Edit your wp-config.php file. Where it says 

define('WPLANG', '');

change it to 

define('WPLANG', 'en_US');

Obviously if your main language is not American English it is likely that this has already been changed to the correct language but you may need to check, especially if your changes are not occurring.

Changing text strings by using a plugin or a custom function

If you know the exact text string you need to re-word, you can alternatively use the Quick Localisation plugin that can be downloaded here for free:

http://wordpress.org/plugins/quick-localization/

Quick Localisation

Or you can add a custom function to your theme’s functions.php file or the custom_functions.php file that is included with Event Espresso’s Custom Files add-on. Example code follows:

Posted in | Comments Off on How to change wording and text with Poedit

« Older Entries
Newer Entries »
Event Espresso - Staging Server