Support

Home Forums Event Espresso Premium Support licence keys – which one does what?

Support licence keys – which one does what?

Posted: September 19, 2014 at 6:56 am

Viewing 41 reply threads


Ian Just

September 19, 2014 at 6:56 am

My profile page shows three. The documentation makes it sound like there is one for EE Core and one per purchased addon.

Two of the three have a ‘_FREE’ suffix, including one which has ee3_FREE at the end. Are these for EE4 Decaf and EE3 Lite? If not, what are they for?

When I saw there was an update for EE4, I put the third one in the ‘support licence key’ bit of the EE4 settings. The key symbol is now green ๐Ÿ™‚ but I still didn’t have access to the one click update ๐Ÿ™ and that key is still showing in my profile page as “not currently activated” :/

(As using an ‘upgrade uploaded themes and plugins in place’ plugin didn’t work, I had to deactivate / delete / upload / install to do the upgrade.)


Lorenzo Orlando Caum

  • Support Staff

September 19, 2014 at 7:22 am

Hi Ian,

The free keys are used for the free versions of Event Espresso (lite for ee3 & decaf for ee4).

Could you try re-saving your support license key again through your WordPress dashboard?


Lorenzo


Ian Just

September 19, 2014 at 7:37 am

Ah, so I was right about that guess.

Just done that (twice, because I noticed that it looks like updating lost the postal code for the organisation) – it still shows a green key in the dashboard and ‘not currently activated’ in the profile.


Lorenzo Orlando Caum

  • Support Staff

September 19, 2014 at 7:52 am

Hi,

Would you happen to have any firewall or security plugins running on your site?


Lorenzo


Ian Just

September 19, 2014 at 8:20 am

Everything is open going out, and most ports are blocked coming in (80 is an obvious exception).

As it’s in the middle of being set up, it is in maintenance mode via a plugin that sends a 503 to anyone looking at it who’s not logged in.

(Anyone trying to access wp-login also needs a password to get there, but as you don’t / shouldn’t have the login details, that shouldn’t be an issue.)


Lorenzo Orlando Caum

  • Support Staff

September 19, 2014 at 9:19 am

Hi, could you disable maintenance mode and then re-save the support license key.

Then you can reactivate it.

Maintenance mode may also block some areas of Event Espresso such as the PayPal IPN.


Lorenzo


Ian Just

September 19, 2014 at 9:24 am

Tried that between my reply and yours. Nope, same thing.


Jonathan Wilson

September 19, 2014 at 9:28 am

Ian,

Can you remove the key from the field in your Event Espresso General Settings, save the blank field, then reenter the key and save again?

Let me know if you have anymore issues. I’m here to help.


Jonathan Wilson

September 19, 2014 at 9:31 am

Ian,

Can you ?remove the key from the field in your Event Espresso General Settings, save the blank field, then reenter the key and save again?

Let me know if you have anymore issues. I’m here to help.


Ian Just

September 19, 2014 at 1:47 pm

Done. The only plugins active were EE4 and the EE GB international pack.

Still showing as not currently activated. What’s it do on the Dashboard when it works?


Lorenzo Orlando Caum

  • Support Staff

September 19, 2014 at 6:53 pm

Hi Ian,

I’ve just rolled over your Support License Key and created a new one for you.

You can find it in your Event Espresso account:

REDACTED

Deactivate any maintenance mode or firewall/security plugins.

Then login to your WordPress admin and locate Event Espresso in the admin menu. Then click on General Settings. Now copy the new support license key from your account page. Then erase the existing key and click on Save on the right side of the screen. After the page refreshes, please paste your new support license key and click on Save once more.

These steps will refresh your Support License Key.


Lorenzo


Ian Just

September 20, 2014 at 2:31 am

Nope.

This is WP en-gb 4.0; EE4 4.4.1.p; EE4 UK ‘states’, no other plugins active. Permalinks are set to %postname%… any other settings you want to know?

There is an external firewall blocking unsolicited stuff coming in at any other port than 80, but this is sufficient to get the New @ Event Espresso news feed without a problem. Similarly, it looks like the PUE code you use is doing its stuff via wp_remote_get and this works fine for the WP install knowing there are updates.

If you’re doing something tricky to do this, let me know what (and why!) and I can set things up accordingly. It’s hosted on a DigitalOcean VPS running Debian Wheezy, so I have control over everything.


Josh

  • Support Staff

September 24, 2014 at 1:47 pm

Hi Ian,

It may be the firewall blocking things. I checked our logs and I’m not seeing any requests from your server. I’ll send a note over to the developer of the Plugin Update Engine to see if he has any suggestions for you.


Darren Ethier

September 25, 2014 at 8:38 am

Hi Ian,

I’m the primary developer responsible for the updates code. Our server is not recording any requests from your server domain. Can I have the ip address of the server Event Espresso is hosted on and I’ll check our logs and see if it is getting blocked. Again, I need the ip address of the server your Event Espresso site is installed on, not your own computer ip address.


Ian Just

September 25, 2014 at 12:35 pm

It’s 178.62.7.183


Ian Just

September 25, 2014 at 1:08 pm

I’ve just done a ‘delete the key and save, then re-insert it and save’.

The news has the “Scheduled Website Maintenance Sept. 24, 10PM MT” item, so the site is communicating with something at your end.


Josh

  • Support Staff

September 25, 2014 at 2:16 pm

Hi Ian,

It would be good to see the response from wp_remote_get(). Can you throw a little debug code into the pue-client.php file? It’s located at /core/third_party_libs/pue/pue-client.php. On line 680 you’ll see this:

$result = wp_remote_get(
	$url,
	$options
);

Then add this:

print_r($result['response']);

Then save, and then when you re-save the General Settings page it will output the response.


Ian Just

September 25, 2014 at 2:55 pm

As line 684?

I’m not seeing any obvious output – where would it be on the page?


Ian Just

September 25, 2014 at 3:07 pm

I’ve tried using file_put_contents to save the info to a file, and that file never gets created.

Either I’m doing something wrong, or I’m not sure it’s executing this code.


Josh

  • Support Staff

September 25, 2014 at 3:14 pm

The output should get displayed right at the top of the General Settings page, right after you save the General Settings.


Ian Just

September 26, 2014 at 12:33 am

Nope.

Are you seeing anything from the UXIP stats collection from it?


Josh

  • Support Staff

September 26, 2014 at 7:50 am

Yeah I checked and we’re getting the UXIP stats, but the key isn’t activating.

If it’s okay, can you send temp WordPress admin level log in + FTP credentials via the contact form on this page?

https://eventespresso.com/send-login-details/

This will allow us to investigate further.


Ian Just

September 26, 2014 at 1:53 pm

There isn’t a ftp server running on it – I use sftp if I want to transfer files. Is this likely to be an issue?


Ian Just

September 26, 2014 at 3:31 pm

Sticking print_r in several places tells me that the requestInfo function is never being called when the key is entered.

If I do it for every function in that file, the ones called with the key as a parameter are:

__construct
_verify_options
_set_slug_and_slug_props


Darren Ethier

September 26, 2014 at 3:39 pm

Ian, the thought just occurred to me and its likely a question that should have been asked a lot earlier. Are you trying to add the key on the subsite of a WordPress Multi-site installation?


Ian Just

September 26, 2014 at 4:00 pm

No.

There are several subdomains in use on the server – as in 2014.example.com, 2015.example.com, and bookings.example.com as well as example.com – but they’re all individual WP installations.


Darren Ethier

September 26, 2014 at 5:20 pm

Hmm… very unusual. I appreciate the troubleshooting steps you are taking. The code for sending the site-license-key verification request to our servers is in the same method as the code that sends uxip stats and we have received the stats, so its very puzzling as to why our server is not recording receiving your license key.

I know its likely already been asked, but can you double check and ensure there is no whitespace on either side of the license key when you paste it in the field?


Ian Just

September 27, 2014 at 2:06 am

Yep, no spaces (one advantage of r_print-ing out the arguments to the function arguments!)

I think you’re not getting it because it’s never been sent. What’s the call stack when it is, i.e. what calls the code that calls the code that sends it?


Darren Ethier

September 27, 2014 at 7:19 am

the PluginUpdateEngineChecker class is basically instantiated on every admin page load. However, in the callback which runs on every init hook (‘hook_into_wp_update_api’), there is a listener for the ‘site_license_key’ key in the $_POST global. If its present, then we trigger a update check. This is so update checks can be forced by saving the EE general settings page.

In all our testing this has been working as expected. It appears that this isn’t getting called in your case? Have you made any changes to core EE files by any chance?


Ian Just

September 27, 2014 at 7:36 am

Well, that function never gets called.

No, no changes at all, apart from the ‘print diagnostic info’ to this file.


Darren Ethier

September 27, 2014 at 7:41 am

Yeah and that’s really puzzling, because in our testing, when we save the general options page it always gets called…

But you know what, I think I know why you aren’t seeing the results of the print_r()… its because there’s actually a redirect that happens after the options are saved.

So:

1. Make sure the general options page is loaded.
2. Add the print_r() to the to return the response of the wp_remote_get()
3. add an exit; right after that line (to prevent a redirect)
4. Add the key and save the options page.

That should show you the response of the wp_remote_get().

Don’t forget to remove your debugging code after you are done.

  • This reply was modified 10 years, 2 months ago by Darren Ethier.


Ian Just

September 27, 2014 at 7:52 am

Some MD5s:

dd036207ac07bd56cdd0a22e2a38fc2a core/EE_Addon.core.php
c88127417bbe58f86e98d99bd3028ef0 core/EE_Base.core.php
b10a754c94d745b3b9340e9b6c191bd5 core/EE_Cart.core.php
97d4addd715dd3e41697468fdfb00430 core/EE_Config.core.php
d8500b2e274028e958826c04526700e0 core/EE_Configurable.core.php
34df634b17f67aad92407546a1056e8d core/EE_Data_Mapper.core.php
d99edae457936e62b907ac59014c9576 core/EE_Data_Migration_Manager.core.php
ae5b7f31f4e16e01d1f64b216d4fb349 core/EE_Data_Migration_Script_Base.core.php
69245140706c08a6ab5013a37f70405a core/EED_Module.module.php
1e507b67a17619ea7900a0cd546fe4df core/EE_Encryption.core.php
eecef8dd41a1d26a6e623c1e10f384bd core/EE_Error.core.php
a237c531883c71e910adad288210b934 core/EE_Front_Controller.core.php
d33773ca02c73674bcacfeda2bb98d03 core/EE_Load_Textdomain.core.php
0ce366cf5e6549dd2f0290dda8cfd425 core/EE_Log.core.php
b3ef9da4ffc6e6b19bf0247bd3f9b4fe core/EE_Maintenance_Mode.core.php
9594e90d0f5dc91809a982113a040c8c core/EE_Module_Request_Router.core.php
f06840630b7b550c947cbf627f450918 core/EE_Network_Config.core.php
e4485d0af0807e4af8c0517f94e8638b core/EE_PUE.core.php
e903eefb80eb7b0aae16f9dcd5eb198b core/EE_Registry.core.php
7b9dceea8ff860cb42b0bfeb699b1a1e core/EE_Request_Handler.core.php
f902ea3ffed7ea0dcc13bdafd7e83b53 core/EE_Session.core.php
b1c7fd294c0dcbff30ec3e22ad667b16 core/EES_Shortcode.shortcode.php
86492f080ed17e831bc4bd8b00480e81 core/EE_System.core.php
96137494913a1f730a592e8932af394e core/index.php


Darren Ethier

September 27, 2014 at 8:02 am

now we’re getting somewhere, but that’s still VERY puzzling as its the first time I’ve seen something like that.

So just to be clear, this should be the debugging code in your pue-client.php file (I’ve added a couple of extra param checks):

$result = wp_remote_get(
	$url,
	$options
);

print_r( $url );
print_r( $options );
print_r( $result );
exit();

I apologize if you are very familiar with php and this comes across as condescending, its not the intent – we just have people hit our forums with varying degrees of familiarity with php and code in general so I don’t like to make assumptions one way or the other.

Thanks! I may not respond right away after your next post because I’m signing off for the weekend. If you still get that response I’d have to consult with my other colleagues as well because that is the first time I’ve seen that response to a wp_remote_get() request. It suggests that there’s some other code in your machine that filtering the request/response.

  • This reply was modified 10 years, 2 months ago by Darren Ethier.


Ian Just

September 27, 2014 at 9:34 am

Just changing the actual key to (*key*) it’s…

REDACTED


Ian Just

September 27, 2014 at 9:44 am

If I try to wget that URL from the server myself.. (something on this site doesn’t like ‘h t t p’ etc so that’s been edited!)

$ wget h_t_t_p://eventespresso.com?pu_checking_for_updates=1&pu_request_plugin=event-espresso-core-reg&pu_plugin_api=(*core*)&new_pue_chk=1&pue_active_version=4.4.1.p&site_domain=bookings.bicon.org.uk
[1] 5732
[2] 5733
[3] 5734
[4] 5735
[5] 5736
Resolving eventespresso.com (eventespresso.com)… 204.13.110.232
Connecting to eventespresso.com (eventespresso.com)|204.13.110.232|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: unspecified [text language=”/html”][/text]
Saving to: `index.html?pu_checking_for_updates=1.1′
2014-09-27 15:36:25 (113 KB/s) – `index.html?pu_checking_for_updates=1.1′ saved [40361]

^C
[1] Done wget h_t_t_p://eventespresso.com?pu_checking_for_updates=1
[2] Done pu_request_plugin=event-espresso-core-reg
[3] Done pu_plugin_api=(*key*)
[4]- Done new_pue_chk=1
[5]+ Done pue_active_version=4.4.1.p


Ian Just

September 27, 2014 at 10:14 am

..and if I try that URL from my PC’s browser, I get a different response:

REDACTED

.. and it’s now showing in my profile as assigned to the right site.

But the site itself still isn’t picking up that there is an update.


Ian Just

September 28, 2014 at 4:47 am

The site’s just picked up that there’s a theme update available at wordpress.org, so that mechanism is working.


Josh

  • Support Staff

September 29, 2014 at 1:56 pm

Thanks for the updates. I’ve sent a note over to Darren on this.


Ian Just

October 1, 2014 at 7:38 am

One option would be to set up a DigitalOcean VPS with the same settings as this one – you could then see exactly what’s going on.


Josh

  • Support Staff

October 7, 2014 at 9:15 am

Hi Ian,

It turns out we have a few of our sites we use internally hosted on Digital Ocean. I installed EE4 on one of them and tested the Plugin Update Engine with success. I guess you’d need to specify what your settings are in order to for us to know what those are.


Ian Just

October 15, 2014 at 11:11 am

I can do that, but if you set up a VPS and give me the login details, I can duplicate the settings and you can tweak away until it works…

It’s one way to take advantage of Digital Ocean’s ‘less than a cent per hour’ pricing.

(Back from a week away.)


Josh

  • Support Staff

October 15, 2014 at 11:16 am

Maybe this will help:

You spin up another server with a vanilla WP install, install Event Espresso, and test the license key update there.

Viewing 41 reply threads

The support post ‘Support licence keys – which one does what?’ 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