Skip to content

Releases: tjdraper/template-sync

1.1.1

06 Feb 15:49
Compare
Choose a tag to compare

Fixed

  • Fixed a mkdir bug that could occur when trying to create the _spec directory
  • Fixed a bug with .feed template extensions
  • Fixed a bug where the index template could not be any type of template (issue #8)

1.1.0

16 Jan 20:51
Compare
Choose a tag to compare

New

  • Template Sync now uses the new (as of EE 3.5.0) core_boot hook to perform the sync. This fixes the incompatibility starting somewhere around EE 3.4.0 where models would throw errors on session hooks.
    • This does require EE 3.5.0 or newer since the core_boot hook does not exist prior to that — although having this version of Template Sync installed on older versions of EE 3 should not cause any errors or problems, it just means that no syncing will be performed.

1.0.2

20 Aug 14:52
Compare
Choose a tag to compare

Why is this 1.0.2 not 1.0.1? I got confused when I set the version and tagged the release. ¯_(ツ)_/¯

Updated

Fixed

  • Fixed a bug where templates using . as hidden character would be deleted (Issue #5)
  • Fixed syntax errors in PHP 5.3

1.0.1-b.1

10 Aug 13:49
Compare
Choose a tag to compare
1.0.1-b.1 Pre-release
Pre-release

Updated

  • Updated file and directory permissions when setting and saving files and directories

1.0.0-ee2

18 Mar 18:36
Compare
Choose a tag to compare

Note this release is for ExpressionEngine 2 only. For 1.0.0 for EE 3, look here: https://github.com/tjdraper/template-sync/releases/tag/1.0.0

Fixed

  • Fixed a bug where template group names ending in anything from the character set "group" were mangled.

1.0.0

20 Feb 23:46
Compare
Choose a tag to compare

This is the initial 1.0.0 release of Template Sync

1.0.0-b.7

17 Feb 16:41
Compare
Choose a tag to compare
1.0.0-b.7 Pre-release
Pre-release

New

  • Completely refactored the add-on.
  • Template Sync now works with EE 3's native Template Partials and Template Variables syncing. If you delete one of those from the file system, it will be deleted from the database.
    • Note you should delete the old variables and partials template directories if you were using Template Sync before since EE 3 now uses _partials and _variables.
  • The spec template directory has been updated to _spec to match the _partials and _variables naming convention adopted by EE.
    • You should delete the old spec template directory.

1.0.0-b.6

24 Oct 00:34
Compare
Choose a tag to compare
1.0.0-b.6 Pre-release
Pre-release

New

  • Template Partials and Template Variables will now be synced recursively. The name of the partial/variable will include colons as directory separators. So my_partials/my_var.html would create a partial/variable named my_partials:my_var
  • Template Partials are now name spaced with partial: and Template Variables are now name spaced with variable:

1.0.0-b.5

24 Oct 00:29
Compare
Choose a tag to compare
1.0.0-b.5 Pre-release
Pre-release

This update is a major refactor for ExpressionEngine 3.x. It will not work in ExpressionEngine 2.x at all.

Note

Please note: to use this add-on, you will need this patch for ExpressionEngine 3.0.0:

https://support.ellislab.com/bugs/detail/21221

A near future release of ExpressionEngine will include this patch.

New

  • All database calls refactored to use ExpressionEngine 3’s new native models
  • Completely refactor architecture to use name spacing and load classes as services
  • Add System Template, Template Partials, and Template Variables syncing

Fixed

  • Fixed a bug where an index.html template containing {redirect="404"} would be written if the index template had an extension other than .html

1.0.0-b.4

24 Oct 00:17
Compare
Choose a tag to compare
1.0.0-b.4 Pre-release
Pre-release

New

  • Add ExpressionEngine 3 check for compatibility with the initial release of ExpressionEngine 3.0.0

Please note, this is the last version to offer compatibility with ExpressionEngine 2. All future versions will require ExpressionEngine 3.0.0 or newer.

This version would have and could have gone 1.0.0, but with the release of ExpressionEngine 3, there will be cool new features added that will not work in EE2. But I wanted to leave this as is for EE 2 sites that still exist and even still need to be started on an older and more stable version of EE. This version works well for both EE 2 and 3 for what it does so don’t be afraid to use it.