|
African Drumming
|
July 21, 2013 at 4:42 pm
Hi EE
I came into work this morning to find EE had thrown it’s toys out the pram and seemed have to reset itself. It took its pages out from under parents and into the main navigation, though thankfully all events seem to be intact… thankfully, I’ve spent hours populating the calendar
Why did this happen? Is this going to happen again?
Was working Friday arvo, Monday it was messed up (and made scrambled eggs of my main nav bar)
Would like to know
Cheers, Krystal
|
|
Sidney Harrell
|
July 21, 2013 at 8:10 pm
There aren’t any calls in Event Espresso that affect the wp_posts post_parent field. The only time we affect the pages is if when the EE general settings page is loaded, it can’t find the EE pages, it will create them, but it doesn’t sound like that is what happened.
I would recommend you use a service like Vaultpress, that will give you a minimum of 30 days of daily DB backups, so that you could narrow down what was changed in the wp_posts table and when.
|
|
African Drumming
|
July 21, 2013 at 8:24 pm
Righty-o, thanks for that… I think
Not the friendliest tone of reply and doesn’t make much sense to someone like I (non-WP-guru), but I do appreciate you taking the time to answer
All the best
|
|
Dean
|
July 22, 2013 at 3:36 am
Hi,
I think what Sidney is trying to say is that this should not be caused by Event Espresso. The only time we actually affect pages is when we create the 4 custom pages in activation.
We certainly haven’t seen anything like this before.
Regarding the vaultpress comment, vaultpress is a back up system (premium) by the makers of WordPress. If there was a daily backup then they could be examined to see what exactly occurred.
Does anyone else have access to your site? If so could they have attempted changes? Have you checked your site for potential security issues? Were there any updates done just before or over the weekend (WordPress, themes, plugins, etc)?
“It took its pages out from under parents and into the main navigation”
One thought is that because the pages were under a parent page, this perhaps could have caused issues. There are no issues that we are specifically aware of, but our general advice is to not have the pages set up as “children” of another page.
I did some tests in respect to this and saw nothing unusual, but of course my server is set up differently to yours, so it may still be a factor.
|
|
Sidney Harrell
|
July 22, 2013 at 3:39 am
Sorry. Like my wife says, I’m better with code than with people. The gist of it, though, is that it’s going to be almost impossible for us to figure out what happened without either being able to reproduce the problem, or logs of all the calls made to the database (which almost no one has their server set up to record). But since I’ve never heard of this problem being reported before, the odds are good that it was a fluke and that you won’t have it happen again.
If, however, you are worried about it happening again, or worse, losing your event or attendee data, etc, then I would highly recommend signing up for the $5 a month VaultPress service (http://vaultpress.com/plans/). The 30 day backup archive would let you roll the site back to the way it was on Friday, for example, or even allow you to roll back the state of the pages while keeping any attendee’s data from signups made over the weekend.
|
|
African Drumming
|
July 24, 2013 at 9:07 pm
Thanks for the follow up chaps; it’s much appreciated and I do have a better idea of the situation now. I didn’t know that the pages aren’t designed to be filed away under parents, so I’ve fixed that up. Thanks for recommending vault press too
Hope I didn’t come across too strongly, was aiming for more a ‘constructive criticism’ angle!
Thanks for your time
Krystal
|
|
Dean
|
July 25, 2013 at 4:19 am
Hi Krystal,
No offence taken, we appreciate constructive criticism, it helps us provide better service and a better plugin.
Please let us know if this error persists/occurs again, like I mentioned previously it is something we haven’t seen before, could be unique to your system, or could be something else.
|
