Sākums Izpētīt Palīdzība
Reģistrēties Pierakstīties
Omnimaga
/
SMF2.1
spogulis no [email protected]:Omnimaga/SMF2.1.git
2
0
Atdalīts 0
Faili Problēmas 0 Vikivietne

Thoughts, Ideas and bits of code for SMF (2.1)

Koks: 193c166199
Atzari Tagi
SMF2.1
ZIP TAR.GZ
Peter Spicer 193c166199 ! As per #708 this should fix some of the cases where queries were being made expecting to be case insensitively but weren't; not all systems treat LIKE as a case insensitive operator. There are still some in the search backend and related to banning which will require further examination, but this should resolve the rest. Needs more testing, too. 11 gadi atpakaļ
Packages c8e62fe029 ! Fix many of the phpdocumentor errors with our docblock's 12 gadi atpakaļ
Smileys c8e62fe029 ! Fix many of the phpdocumentor errors with our docblock's 12 gadi atpakaļ
Sources 193c166199 ! As per #708 this should fix some of the cases where queries were being made expecting to be case insensitively but weren't; not all systems treat LIKE as a case insensitive operator. There are still some in the search backend and related to banning which will require further examination, but this should resolve the rest. Needs more testing, too. 11 gadi atpakaļ
Themes 46699b9bc9 ! Fix Mantis issue 4912: if a scheduled task throws an error, note it and pass it back in the event of running tasks manually from the ACP. 11 gadi atpakaļ
attachments c8e62fe029 ! Fix many of the phpdocumentor errors with our docblock's 12 gadi atpakaļ
avatars ab4aa21af9 ! Removed wolf icon due to the fact that it's someone else's logo as per #558. 11 gadi atpakaļ
cache a18e888838 10610 12 gadi atpakaļ
other d6c4f4eb82 + Allow users to turn off whether bans go into the error log or not. And if they do, let's have a category just for them. 11 gadi atpakaļ
.gitattributes 3e46fa2644 More PHP 5.5 fixes found while working on 2.0 PHP 5.5 Combat 11 gadi atpakaļ
.gitignore 7cc1428fdc Fixed login on upgrade not working on first try. 11 gadi atpakaļ
DCO.txt b486a1e52a Adding a Developer's Certifcate of Origin to be used when submitting contributions. 12 gadi atpakaļ
README.md 10f8066483 Update README.md with instructions on how to contribute (sorry for the direct commit...) 12 gadi atpakaļ
SSI.php aec98628cb ! Oops, that shouldn't have been Wedge style code. 11 gadi atpakaļ
agreement.txt a18e888838 10610 12 gadi atpakaļ
contributors.txt 8afad0752c Corrected missing comma. 11 gadi atpakaļ
favicon.ico a18e888838 10610 12 gadi atpakaļ
index.php 5d594b0d9e Disregard -> Unwatch 11 gadi atpakaļ
ssi_examples.php 2c50939f27 Copyright update per BoD 11 gadi atpakaļ
ssi_examples.shtml b17452c904 ! update ssi_examples shtml ... we are not longer rc4 or llc :P 12 gadi atpakaļ
subscriptions.php 2c50939f27 Copyright update per BoD 11 gadi atpakaļ

README.md

SMF, www.simplemachines.org

This is a SMF 2.1 development repository. The software is licensed under BSD 3-clause license.

Contributions to documentation are licensed under CC-by-SA 3. Third party libraries or sets of images, are under their own licenses.

######Notes:

Feel free to fork this repository and make your desired changes.

Please see the Developer's Certificate of Origin in the repository: by signing off your contributions, you acknowledge that you can and do license your submissions under the license of the project.

######Branches organization:

  • master - is the main branch, only used to merge in a "final release"
  • development - is the branch where the development of the "next" version/s happens
  • release-2.1 - is the branch where bug fixes for the version 2.1 are applied

######How to contribute:

  • fork the repository. If you are not used to Github, please check out fork a repository.
  • branch your repository, to commit the desired changes.
  • sign-off your commits, to acknowledge your submission under the license of the project.
    • an easy way to do so, is to define an alias for the git commit command, which includes -s switch (reference: How to create Git aliases)
  • send a pull request to us.

######How to submit a pull request:

  • If you want to send a bug fix for the version 2.1, send it to the branch release-2.1
  • If you want to send a new feature, use the branch development
  • You should never send any pull request against the master branch For more informations, the ideal branching we would like to follow is the one described in this article

Finally, feel free to play around. That's what we're doing. ;)