How to know what code has changed in a file from one version of TEC to another?

Home Forums Calendar Products Events Calendar PRO How to know what code has changed in a file from one version of TEC to another?

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #1375381
    Sean
    Participant

    Hi!

    We have previously made some customization’s (template overrides) to The Events Calendar files. We are going to be updating to the latest versions, but are not sure what the best process is for determining what (if anything) has changed from the version we have installed to the latest version. In other words, what’s the quickest and easiest way to see what the differences are from the “core” files in the version we have installed vs. the latest version, so that we know what we need to update/change in our customized files/template overrides?

    Thank you in advance for any advice!
    Karly

    #1376494
    Victor
    Member

    Hi Karly!

    Thanks for getting in touch with us! I’d be happy to help you with this topic.

    When making a template override, you should not modify any of the core plugin files, but instead you should be creating a new folder inside your active theme’s folder called tribe-events. In it, you should place the modified templates you want to target.

    This way, you won’t loose your changes when updating the plugins. Let me point you to our Themer’s Guide where you can learn more about how template overrides work > https://theeventscalendar.com/knowledgebase/themers-guide/

    I hope that helps! Let me know if you have any follow up questions.

    Best,
    Victor

    #1376610
    Sean
    Participant

    Hi Victor,

    Thanks for your reply. Sorry if I wasn’t clear in my initial post. I am aware of the themers guide and how to create template overrides. We already have our customization’s in our child theme, within the tribe-events folder. What we’re trying to do is determine what has changed in the core files from the version we have installed, to the latest version. That will help us figure out what, if anything, we need to update in our customized files.

    Do you or any of the other Modern Tribe team members have a recommended process for determining what changes have been made to core files so that users such as ourselves can tell what code we need to update in our modified files?

    Thanks.

    #1376911
    Victor
    Member

    Hi Karly!

    No problem! Thanks for clearing that out.

    For The Events Calendar plugin and Event Tickets plugin you can browse their files history in the Github repository > https://github.com/moderntribe/the-events-calendar/ and https://github.com/moderntribe/event-tickets/

    Our premium plugins are not publicly available but you can always use a tool to compare files between versions. I’ve found this online tool to compare files > https://www.diffchecker.com/

    If you use Sublime Text as your text editor, you can use this tool which I have tried and works fine for me > https://www.sublimerge.com/.

    Reading the changelogs is another way to be aware of what changes were made in each version. You can always access them in the readme.txt file inside each of the plugins directories.

    I hope that helps! Let me know if you have any follow up questions and I’d be happy to help.

    Best,
    Victor

    #1376913
    Sean
    Participant

    Thanks Victor. This is very helpful!

    #1376924
    Victor
    Member

    Happy to help Karly!

    In addition to that, I’ve just remembered that you can also find out about the recent template changes by going to your wp-admin > Events > Help.

    Under the Recent Template Changes section you’ll get information about recent changes and potentially impacted template overrides.

    Since you marked this Resolved I’ll go ahead and close it, but don’t hesitate to open a new topic if anything comes up.

    Cheers,
    Victor

Viewing 6 posts - 1 through 6 (of 6 total)
  • The topic ‘How to know what code has changed in a file from one version of TEC to another?’ is closed to new replies.