|
Adele Haswell
|
February 5, 2015 at 10:09 pm
Wordpress v4.1 and EE4.4.10
Today all of the open events on the website changed to Sold Out. It started with just one Event and then all of the rest changed too. I changed them back by changing the Status to Pending Review and clicking on the Publish button.
None of the Events had reached the maximum number of tickets or gone past the Sell to date.
|
|
Lorenzo Orlando Caum
|
February 6, 2015 at 12:17 pm
Hi Adele, that is a strange issue as Event Espresso will only change an event to sold out if the tickets have been sold out.
Also, updating one event won’t update another as events are stored individually.
Does anyone else have access to your site?
—
Lorenzo
|
|
Adele Haswell
|
February 6, 2015 at 6:16 pm
Hi Lorenzo,
Other people do have access to the backend of the site. One of them reported the first event being Sold Out to me and the others were copied on the email. Changing an event to Sold Out isn’t something that could be done easily or accidentally – especially not to all of them.
Is there a way of finding out who has edited an event? I looked to see if I could view the Revisions in the Screen Options and it was there.
Adele
|
|
Adele Haswell
|
February 6, 2015 at 6:17 pm
Sorry I meant the Revisions option wasn’t available in the Screen Options.
|
|
Adele Haswell
|
February 6, 2015 at 6:25 pm
Further update to the above. I went into the backend to have a look at an Event and I have seen that just by me editing the Event the Status has changed to Sold Out.
Under Available Tickets there are 100 Tickets for sale with 0 sold and 0 Regs even though it is showing that there are 7 Approved Registrations for it. The Sell until date is 14 Feb.
|
|
Tony
|
February 7, 2015 at 7:04 am
Hi Adele,
If you open up Chrome Dev Tools on the event editor page and view the console do you see any errors?
We’ve not seen this issue before so I suspect this may be a theme or plugin conflict.
Is this a live site or dev?
You can test another theme using a plugin such as Theme Test Drive which will allow you to set the site to disable one of the default themes such as twentyfourteen to the admin. If you do this and re-test, does the same happen?
Troubleshooting a plugin conflict will need all non EE plugins to be de-activated, re-test to check EE works as expected, then activate the plugins one by one retesting between each one to see which one conflicts. This is best done on a development site rather than live.
I would recommend creating a full site backup before troubleshootin this, just to be safe.
|
|
Adele Haswell
|
February 10, 2015 at 5:10 pm
I have upgrade to v4.6.4 and this issue seems to have gone away!
|
