|
Will Chapman
|
April 8, 2013 at 11:15 am
Once again – it seems to happen each time there is an update – I got the message that ‘I held an uptodate license but it was only good for one site’. That should be no problem because EE is only in use on one website (http://alrewascanalfestival.org).
So instead of the convenience of upgrading automatically, I downloaded the latest version(which was, unfortunately still called ‘Event Espresso’ without any version numbers to differentiate between previous versions with the result that my system renamed it as ‘Event Espresso_4.zip’ – which, in itself rather dramatically shows how many times auto-uupdate hasn’t worked.
So then I tried uploading the new version via New Plugin and soon found that it wouldn’t work because the size (8.1MB) exceeded the permissible.
So I was forced to manage the update completely manually via FTP. Trouble with is that the version number is shown as 3.1.31.1 rather than 3.1.31.1P as shown on the website and I am left with the worry that maybe the update hasn’t worked. Finger’s crossed!
Come on chaps, I think it is time you got this issue sorted out. It costs us an hour of so of time with all this fiddling about and I’m still left wondering whether I have a working site or not. (My fault – I shouldn’t have taken the risk of upgrading with a live site that is currently taking bookings).
Cheers
Will Chapman
|
|
Will Chapman
|
April 8, 2013 at 11:17 am
That heading is wrong – I don’t know how it got changed but I typed in ‘Update to 3.1.31.1P’
|
|
Josh
|
April 8, 2013 at 1:50 pm
Hi Will,
I’m sorry for the trouble. There was a bug that was fixed after 3.1.28.2 that affected the updater. Was that the one you were trying to update from? Are there any older versions of Event Espresso (not active) still on the server? Is this a single or multi-site installation of WP?
One other thing: we did quite a bit of work to lighten the download size of the core plugin and it’s now just under 4MB zipped. So I’m not sure why it would have told you that ee was over 8MB in size unless you were trying to upload an older version.
|
|
Will Chapman
|
April 11, 2013 at 4:28 am
The site is a single installation of WP but it is a sub-domain existing with several other websites also sub-domains in their own folders (each with their own WP install) off of the main domain/public_html. Only one of these sub-domains uses EE. Could that be a source of these auto-renewal issues?
I’ll check to see if there are any old versions still hanging about (but inactive) and remove any I find. My current license (Personal) only allows me updates of a couple of modules and I may well have some outdated one installed but inactive.
I’ve figured out how my original Post title of ‘Problems with 3.1.31.1 Update’ got changed to ‘Updated to 3.1.28.2…’ When one types in the intended post title your system rather cleverly searches for similar existing posts and it is very easy for that to change your original title to that of the similar thread. (In fact, I this happened to me a few weeks ago and instead of creating a new post I ended up adding a comment to a previous thread (and you asked me not to post into existing threads with new issues!).
I have developed another problem with this upgrade – customers are getting at least a dozen confirmation emails after using Paypal. I’ve studied the earlier, now-closed thread on this but the solution there doesn’t apply so perhaps a re-install of 3.1.31.1P is in order (the P doesn’t show up in the list of installed Plugins; is that indicative of anything?
Regards
Will
|
|
Sidney Harrell
|
April 11, 2013 at 9:37 am
When you are in the admin of the site you are trying to auto-update, what is the url before the /wp-admin part of the url?
|
|
Josh
|
April 11, 2013 at 9:51 am
The P is missing in the version number for 3.1.31. It’s indicative of a typo on our part.
The issue that you’re having with multiple emails since the update may be related to PayPal pinging your server with multiple IPNs if it’s not connecting the first time. Can you post a link to the registration page so we can run a test registration and investigate further?
|
|
Will Chapman
|
April 11, 2013 at 10:26 am
@sidney
The url of the website folder where Event Espresso is located is:
/public_html/alrewascanalfestival.org/wp-content/plugins/event-espresso
The domain within which /public_html/…. exists is http://waterwaywatch.org. I have six websites each of which uses its own copy of WP 3.5.1 in folders that are named to match the registered domain name. Only one of the sub-domains (alrewascanalfestival.org) has Event Espresso installed.
Does that answer your question?
Regards
Will Chapman
|
|
Will Chapman
|
April 11, 2013 at 10:29 am
By the way Seth has administrative access to the site from a previous issue. I could send you the name:password pair privately if that would help.
Regards
Will
|
|
Josh
|
April 11, 2013 at 10:57 am
Hi Will,
I ran a quick test registration and I think I found the reason that people are getting multiple emails after the PayPal payment. The page set as the transacations page is redirecting to this page:
http://alrewascanalfestival.org/eventpaypaltxn/
When I go to that page in my browser says the page is not found. So PayPal may not be getting a notification that the IPN is received and keeps pinging your site with repeated instant payment notifications. Which can trigger another email each time one is sent.
|
|
Sidney Harrell
|
April 11, 2013 at 11:17 am
What are the version numbers of any EE add-ons that you have on the site?
|
|
Will Chapman
|
April 11, 2013 at 11:31 am
@josh That sounds promising – I’ll take a look. I first set up EE around the end of 2010 and I haven’t changed the setups since then so I suppose there is a fairly high chance of something being out of sync.
@sidney I’ve removed all old EE addons except Calendar (2.0.4) which is inactive and EE Requirements Check (o.74) also inactive. EE itself is 3.1.31.1
|
|
Will Chapman
|
April 11, 2013 at 12:10 pm
@josh I took a look at the settings and it seems to follow all the recommended shortcode rules.
The only thing I spotted that was a bit unusual is that I have two pages using the shortcode [ESPRESSO_PAYMENTS], one is the page linked in Settings and the other appears to be a test that I used and actually has a title of [ESPRESSO_PAYMENTS] – maybe I should trash that? (I’m really nervous about changing anything ‘cos my site is live!)
I also have a page called [ESPRESSO_TXN_PAGE] which has the same shortcode as body text and appears to be correctly linked in Settings. It is also set to private.
|
|
Josh
|
April 11, 2013 at 1:05 pm
Hi Will,
The [ESPRESSO_TXN_PAGE] page should not be set to private. If it’s set to private, PayPal can’t deliver IPN notices to your site. The four pages set in Event Espresso>General Settings under page settings all need to be publicly viewable pages. Note: they don’t need to be in the site’s navigation menu, but they do need to be accessible.
|
|
Will Chapman
|
April 11, 2013 at 2:44 pm
Josh
Now that is interesting – I have completely misinterpreted the instruction:
[code]This page should hidden from your navigation, but still viewable to the public (not password protected).[/code]
I read the mention of password protection as implying that it could be private as long as it wasn’t password protected. (As only private posts can be protected by a password the last part of the sentence is redundant).
I’ve made the change and hopefully that will be the solution. Thanks very much to you both for your attention.
Regards
Will
|
