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
Ticketing & HTTPS Issues | Event Espresso - Staging Server

Support

Home › Forums › Ticketing › Ticketing & HTTPS Issues

Ticketing & HTTPS Issues

Posted: April 19, 2013 at 5:26 pm

Viewing 1 reply thread


Christopher Castro

April 19, 2013 at 5:26 pm

Hello,

I want to follow up on an issue that I posted a few months ago at http://staging.eventespresso.com/topic/https-conflicting-with-ticketing/.  I had to just cut out the ticketing for that event to get it ready to launch – but I’m setting up another event and would like to get a resolution.

This left off at support asking if php had access to write to a /tmp folder.  I actually can’t locate that folder, so I’m wondering if I should create that directory and adjust permissions.  If you can weigh in and let me know what I should try next, that would be great.

Regards,

Christopher Castro

 


Dean

  • Support Staff

    •

April 22, 2013 at 12:50 am

Hello Christopher,

If I am correct, thats the standard tmp folder that most servers have (it is for PHP to create sessions), and depending on your server setup it is normally in the root of your site, so where the public_html folder is.

Viewing 1 reply thread

The support post ‘Ticketing & HTTPS Issues’ 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.

Status: closed

Updated by Dean 11 years, 9 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server