|
Brandon Pierce
|
March 14, 2013 at 6:54 am
We need to Reset one of our Licenses due to site rebuild. I already paid the $10 to get one of our licenses reset.
I am delayed in working on this project because I can’t finish the site build without a working license for Event Espresso. It is VERY frustrating to have to go through this forum to get something simple like this done quickly.
We added one of our 5 dev licenses to the root site of a multi-site install. The multi-site install was so problematic when trying to configure Event Espresso we are scrapping that approach and going with a one site per license approach.
We haven’t used Event Espresso for long (not event a month yet), so we’re doing a lot of trial and error while we get our approach solidified.
The first license was for a site we are moving to the main directory (this site has been terminated as we switched away from multi-site):
events.meetingservicesinc.com/nasva/
The second license was used when the main directory was part of a multi-site. Now we are using just the main directory (but that license is coming up as used, even though it’s the same web address as before when it was part of a multi-site):
events.meetingservicesinc.com
We are in a rush to get this completed and I don’t want to pay $10 every time I burn through a license trying to get the configuration right.
Thanks for your help.
|
|
Brandon Pierce
|
March 14, 2013 at 6:55 am
Sorry the topic is wrongly named… I can’t describe how frustrated I am right now. I wanted this topic named: “We need to Reset one of our Licenses due to site rebuild.”
|
|
Josh
|
March 14, 2013 at 9:05 am
Hi Brandon,
I’m sorry for the trouble you are having. I’ve reset your keys.
The license keys will not work on a multisite installation. This is a technical limitation that we one day hope to overcome with the license key system. The license keys do not actually hinder the functionality of Event Espresso, they only serve the purpose of verifying a support license. You can run a site with Event Espresso without a support license.
In the future, if you need to reset a license key the reasons like you had, or you’re switching from a development server to a live server, you do not need to pay. If you request a reset and skip the payment, we’ll still reset it for you.
|
|
Brandon Pierce
|
March 14, 2013 at 9:10 am
I’m having some serious issues getting the NASVA site to launch, hence requesting the reset. Currently the site is coming up with error messages.
Here’s the location: events.meetingservicesinc.com
Here are the error messages:
Warning: session_start(): open(/tmp/sess_ruqbJARG36GYKHNVBngH-3, O_RDWR) failed: Permission denied (13) in /home/msievents2/events.meetingservicesinc.com/wp-content/plugins/event-espresso/espresso.php on line 53
Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /home/msievents2/events.meetingservicesinc.com/wp-content/plugins/event-espresso/espresso.php:53) in /home/msievents2/events.meetingservicesinc.com/wp-content/plugins/event-espresso/espresso.php on line 53
I need this site to launch today, but EventEspresso is not working properly. We host with Dreamhost. Is this something on their end?
We’ve used the plugin only on one other site, and it’s working great. Different hosting provider though.
|
|
Josh
|
March 14, 2013 at 9:49 am
Hi Brandon,
The permission denied errors indicate a file permissions issue where WordPress cannot write to the session.save_path, or that the location set as the session save path is missing. You can check with your host and ask them to verify whether WordPress can write to the session save path.
The headers already sent errors may be from extra spaces in wp-config.php outside the php tags. Here is a link to the WordPress codex that may help:
http://codex.wordpress.org/FAQ_Troubleshooting#How_do_I_solve_the_Headers_already_sent_warning_problem.3F
|
|
Brandon Pierce
|
March 14, 2013 at 10:20 am
How do I find out what the session.save path is? Or is this something the hosting provider would know, not us?
The wp-config.php file was auto-generated, and I couldn’t find any extra spaces in it.
Thanks for all your help.
|
|
Josh
|
March 14, 2013 at 10:28 am
Hi Brandon,
The session.save path is set in the php.ini file, and you might find the path by going to the Event Espresso system status page. The system status page will not necessarily indicate whether it’s writable. You can check with your host and ask them to verify whether WordPress can write to the session save path.
|
