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
Merchant Warrior Image | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Merchant Warrior Image

Merchant Warrior Image

Posted: May 20, 2013 at 6:04 pm

Viewing 1 reply thread


karen bowness

May 20, 2013 at 6:04 pm

Hi,

Just having some trouble uploading custom images to the merchant warrior payment gateway. When trying to add in the button image, it will let you browse to pick your image but when you select one, it won’t update the field. Have tried uploading and pasting in the URL separately which seems to work by updating the image in the admin side, but the front-end remains as the default Merchant Warrior button.

Also must have broken something along the way as now when we test it we get: “There was an error processing your transaction – Error: (005:Field ‘logoURL’ contains forbidden characters)”

Any help would be much appreciated!

Have just updated to latest WordPress and Event Espresso. Rego page: http://becsouthernsydney.com.au/event-registration/

Cheers


Sidney Harrell

  • Support Staff

May 20, 2013 at 9:40 pm

I haven’t had a chance to look into the issue with the uploader, but I did confirm and find a fix for the issue on the frontend of it defaulting to the mwarrior default image. Try changing the line 69 in gateways/mwarrior/mwarrior_vars.php, which should now read:

} elseif (file_exists($mwarrior_settings['button_url'])) {

to:

} elseif (@fopen($mwarrior_settings['button_url'],"r")==true) {
Viewing 1 reply thread

The support post ‘Merchant Warrior Image’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso - Staging Server