nickfmc

ours was on PHP 5.3 just for your records. thanks for the quick reply and free plugin support!

I assumed you fixed this but for other people who find this error, most likely cause is that your php was updated to version 7 and an incompatibility with your theme threw the error. Downgrading to 5.6 will probably solve this issue for a lot of people.

found out what I did, user error ??

I have a client with this issue, havent found a reason yet however using quick edit to change the new page from draft to published seams to be a workaround for them.

so yours is a different set of variables that are causing the issue me and onetrev are seeing. We are never enabling the nested pages menu sync. when we update we loose our menu or do the workaround Kyle suggested and we get all of our pages showing up in the menu as there is no synced state for it to go back to.

Xavier you had a WP menu setup via appearance -> menu had nested pages installed but never used the sync option?

if you have a WP menu you setup through appearance and have never used menu sync the fix does not bring back your menu! well it does bring back a menu but with all pages, not your original WP menu.

I had just used the shortcode yes, didn’t see there was a function for it. either way it worked and doesn’t seem to anywhere now using the shortcode for me. However if support is being dropped for the shortcode I guess its no worry.

no worries I just registered a sidebar where I needed it!

sorry should have been more clear, the do_shortcode I had in my theme files directly in PHP. The text widget I tried when that failed was as you show above without the do_shortcode.

Ya, I was in a rush for launch so didn’t have time to investigate for you, sorry! I will try updating the Dev site later and see if I can replicate the problem.

I deleted the plugin and reinstalled fresh and it looks to be working.

Mine has also stopped working when updating from 2.6.3.2 to 2.7.1

I can confirm this also broke on a clients site of mine. I am using the Pro so switching seams to be a working option for me. I was doing a filter using tag= and it seamed to ignore that and just show all upcoming events not taking the tag attribute into affect.

user error

If it was just stylesheets causing the distortion I missed then that is good. I just though having end users required to upload their images in a correct ratio in order to avoid distortion is terrible UX for a store owner.