Source Code public repository?

[edthered]

Is there a publicly accessible repository for the ZenCart source? Just looking for read-only access. Svn or git.

Thanks!

[mc12345678]

Is there a publicly accessible repository for the ZenCart source? Just looking for read-only access. Svn or git.

Thanks!

ZC is available in github, but download of the software is publicly available where all of the code for that version of ZC is readable/modifiable. Almost all past versions of ZC are available from http://www.zen-cart/getit. (I say almost all as there are some very early versions that may not be available. But definitely 1.3.x on are avail.)

What is the need for this?

[lat9]

The github repository is here: https://github.com/zencart/zencart

[edthered]

What is the need for this?

I just upgraded a client site to 1.5.4 and when I added the new files to subversion I encountered a massive headache from inconsistent line endings from the official release. If I can check out the tags directly I can eliminate all that trouble.

I'm sure by the next release I'll have forgotten that I need to run dos2unix on the release before merging the changes into my current project.

Thanks to all for the links.

[DrByte]

You could also use a text-file-compare utility like WinMerge to do the comparison of files, and tell it to ignore line-endings.
Then, after you've identified the customizations you need to re-make in the new version, you can make those edits and upload the complete new fileset to the server.
And, since that's what the documented upgrade instructions advise anyway, that approach is in keeping with existing recommendations.

[edthered]

You could also use a text-file-compare utility like WinMerge to do the comparison of files, and tell it to ignore line-endings.
Then, after you've identified the customizations you need to re-make in the new version, you can make those edits and upload the complete new fileset to the server.
And, since that's what the documented upgrade instructions advise anyway, that approach is in keeping with existing recommendations.

This is not about what goes on the live server, that was fine, but what goes into the development subversion repository after I've upgraded. When I add the new files into the local set (svn add) subversion won't take them if the line endings are inconsistent, so I have to go through file by file as the adds fail and fix them. I'm just looking for an easy way to get around that for next time. If I have a local checkout then I'll grab the new through subversion and won't run into this again, hopefully.

I do have a script to run over the directory now, but I doubt I'll remember that come next upgrade.

[DrByte]

It's been a long time since I used SVN, but I know git allows for setting some configuration parameters for handling line-endings.
Just mentioning in case that's worth exploring.

But, as you say, using the utility to manage files downloaded from your server may be the best solution ... just a matter of remembering ;)

[lhungil]

By the way, Welcome to the Zen Cart community!

It's been a long time since I used SVN, but I know git allows for setting some configuration parameters for handling line-endings.
Just mentioning in case that's worth exploring. ...

Ahh yes, the joys of Subversion.

Modern SVN does support configuration for handling OS specific line-endings (very similar to GIT), just this mode is not usually enabled out of box. Basically you set the svn:eol-style attribute native before checking in a TEXT file. This can be automated on the first commit by your SVN client (commandline, tortoise-svn, etc) by configuring auto-props.

Alternatively a SVN repository administrator can have a pre-commit script on the server (to basically do what auto-props does)... But usually it is easier to just configure the SVN client (unless you have lots of people regularly committing new files)...


While this ensures consistency in SVN (and GIT if configured the same), if other methods of transferring files between computers is used (such as SMB, EMAIL, IM, etc) they may not have consistent EOLs. To handle this case one will want to ensure the tool used to do comparisons does support an option to "ignore EOL differences".


NOTE: Using auto-props and svn:eol-style is discussed in the SVN manual and also on stackoverflow.

[edthered]

It's been a long time since I used SVN, but I know git allows for setting some configuration parameters for handling line-endings.
Just mentioning in case that's worth exploring.

But, as you say, using the utility to manage files downloaded from your server may be the best solution ... just a matter of remembering ;)

git is fine. and i've already cloned the zencart repo so i can keep up to date. memory though... that's a fleeting thing these days. ;)

thanks for you efforts and taking the time to answer these questions.

[edthered]

By the way, Welcome to the Zen Cart community!



Ahh yes, the joys of Subversion.

Modern SVN does support configuration for handling OS specific line-endings (very similar to GIT), just this mode is not usually enabled out of box. Basically you set the svn:eol-style attribute native before checking in a TEXT file. This can be automated on the first commit by your SVN client (commandline, tortoise-svn, etc) by configuring auto-props.

Alternatively a SVN repository administrator can have a pre-commit script on the server (to basically do what auto-props does)... But usually it is easier to just configure the SVN client (unless you have lots of people regularly committing new files)...


While this ensures consistency in SVN (and GIT if configured the same), if other methods of transferring files between computers is used (such as SMB, EMAIL, IM, etc) they may not have consistent EOLs. To handle this case one will want to ensure the tool used to do comparisons does support an option to "ignore EOL differences".


NOTE: Using auto-props and svn:eol-style is discussed in the SVN manual and also on stackoverflow.

It's been years since I set up the repo so there may be some new flags, or things I didn't set in the first place. I just know that if I check something out it's taken care of for me. Who knows, maybe I have a script in there doing that.