Problems with venue inside events, and tribe-events-venue-widget

[Ediciones y Recursos Ocio-Culturales]

We have been facing two critical problems whenever we migrate installations to another hosting (now in a hosting with temporary URL for test):

1. Editing o creating events, the venue box gets block at the beggining and it doesn’t load anymore (venue also gets block in event frontend template).

2. Only when we activate EventsC-PRO, the widget “tribe-events-venue-widget” (“Eventos resaltados por lugar”), also blocks widgets page not loading widgets areas or whatever after this widget.

What are the reasons for that?? We need some tips of what to do to solve this.
Thanks in advance.

[Brook]

Howdy,

I am happy to assist you with this.

1. Editing o creating events, the venue box gets block at the beggining and it doesn’t load anymore (venue also gets block in event frontend template).

This seems like a JavaScript “conflict”. In order to proceed we will need to test if a conflict is happening, and if so narrow it down so we can find a fix for it. This guide walks you through how to test for a conflict, and then identify what is conflicting.

2. Only when we activate EventsC-PRO, the widget “tribe-events-venue-widget” (“Eventos resaltados por lugar”), also blocks widgets page not loading widgets areas or whatever after this widget.

This also sounds like a conflict. Can you try testing this issue as well, and see if it is the result a conflict like the first issue?

Cheers!

– Brook

[Ediciones y Recursos Ocio-Culturales]

Thanks for your response.
I have changed to twentyfourteen theme and switched off all the plugins except events-calendar and e.c.pro, but both problems persists. So, no clue how to identify what is happening.
Any other idea?

[Ediciones y Recursos Ocio-Culturales]

Setting the debug log in wp-config, we have found this error when loading for case 1 (Editing o creating events):

[22-Oct-2015 07:34:12 UTC] The Events Calendar Log: Iniciando Tribe Events en Oct, 22nd at 07:10:12 am
[22-Oct-2015 07:34:13 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 81 bytes) in /home/laguiago/public_html/wp-includes/wp-db.php on line 2258

Is it normal that neccesity of memory? If not, how to fix it?

• This reply was modified 10 years, 6 months ago by Ediciones y Recursos Ocio-Culturales.

[Ediciones y Recursos Ocio-Culturales]

The memory issue is being solved with our hosting provider, but now we have detected another problem.

With all the plugins deactivated and the twentyfourteen theme activated, the Tribe events settings page (wp-admin/edit.php?post_type=tribe_events&page=tribe-events-calendar) is blank and fatal errors like these are registered:
[22-Oct-2015 09:30:48 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 81 bytes) in /home/—–/public_html/wp-includes/wp-db.php on line 2258

We think it’s not just a javascript conflict.
Please, any clue?

[Ediciones y Recursos Ocio-Culturales]

Hi again.

The problem came from a conflict in memory limits defined by other configurations in WP instalation.
If it’s useful to anyone, turning off the ini_set function in PHP configuration made it.

Disclaimer: Don’t try this at home if you don’t have a reilable hosting provider 😉

Regards.

[Brook]

That is incredible. Excellent work tracking down the culprit. It would certainly have been unique for a WordPress install to exhaust that much memory. I am glad you were able to narrow down the culprit and find a fix. Sometimes it is best to disable ini_set.

Thank you for sharing the solution. Please let us know if you ever need anything else. Cheers!

– Brook

[Author]

Posts