Forum Replies Created
-
AuthorPosts
-
Michael
ParticipantHi Sky,
Thanks for the information. No, I have not seen any issues with the all
events links but just wanted to check since the bugfix seemed to relate to
that. I’m glad to hear there is no impact.July 21, 2017 at 8:06 am in reply to: Changing Breadcrumb type Event links from …/eventsdefault to calendar page #1324332Michael
ParticipantAndrás (and Barry Hughes),
The PHP snippet solved the issue for me. Thank you for providing an alternative to the redirection plug-in.
Mickey Diener
July 17, 2017 at 11:23 am in reply to: Changing Breadcrumb type Event links from …/eventsdefault to calendar page #1322232Michael
ParticipantHello András,
I hadn’t considered using a redirect plugin. I tested one and it seems to work. However, I do try to minimize my plugins. Is there no way within TEC settings to have the event slug access a custom page without confusing the whole setup?
Thanks
Michael
ParticipantHi Cliff,
Sorry for the delayed response to your posting. I’ve been working on some
other items on my test site and wasn’t able to conduct any testing.I had conducted a number of tests to determine which plug-ins and in what
combination were causing the HTTP 500 crashes. It was quite confusing,
because various combinations were causing a crash. For example, just the
new Divi theme with TEC and TEC Pro would crash. Restoring to a previous
Divi theme or previous versions of TEC all worked. I was unable to test
with the TwentySeventeen theme because TEC widgets were placed in custom
widget areas in Divi. I didn’t want to recreate everything in that theme.Finally I decided to install a 3rd environment on a locally hosted
environment and, voilà, everything worked as it should, no crashes. That
led me to look at the hosting versus local environment. What I realized was
that the hosted environment was running PHP 7.0 and the local environment
was running PHP 5.5. Switching my hosted environment to PHP 5.5 solved the
issue.Clearly, something in PHP 7.0, with newest Divi and TEC (and possibly some
other plugins) was creating a conflict. Just as an aside, when the HTTP 500
errors were thrown, I also received messages from my uptime monitor that
the site was not responding. Therefore, something was definitely causing
the site to come full stop.The bottom line is that all is well. I will keep my PHP version at 5.5.
I hope this long explanation helps if others are having similar issues.
Michael
ParticipantCan I have this reviewed by EC Pro support, please? I am unable to use new features in my theme.
-
AuthorPosts
