summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2016-05-23upload.php: Add Pantsu.cat copyright year 2016Juuso Lapinlampi
Previous two commits in this topic branch introduced substantial changes.
2016-05-23upload.php: Apply DRY to POMF_FILES_ROOT.$newnameJuuso Lapinlampi
Don't repeat yourself with multiple POMF_FILES_ROOT.$newname for full file path. Use a variable pointer $uploadFile. Improves code readability and robustness.
2016-05-23upload.php: Unnest upload_file() if-else expressionsJuuso Lapinlampi
As phpmd (PHP Mess Detector) linter says: "An if expression with an else branch is never necessary." Well, at least almost never necessary. Improves readability and resolves phpmd cleancode lint errors.
2016-05-20Merge branch 'wub/changelog/v2.0.2-release'Juuso Lapinlampi
- CHANGELOG: Update 2.0.2 changelog (Bootstrap license) - CHANGELOG: Add Pomf 2.0.2 release date (today) Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
2016-05-20Merge branch 'maint'Juuso Lapinlampi
Sync with Pomf 2.0.x maint branch. - package.json: Change version to 2.0.2 (Essentially, this merge is for git-describe(1).)
2016-05-20CHANGELOG: Add Pomf 2.0.2 release date (today)Juuso Lapinlampi
Pomf 2.0.2 has been released today and tagged v2.0.2.
2016-05-20package.json: Change version to 2.0.2Juuso Lapinlampi
This marks the Pomf 2.0.2 release. Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
2016-05-20CHANGELOG: Update 2.0.2 changelog (Bootstrap license)Juuso Lapinlampi
See: 25ec99f6f8b184dc29804358185104c800f2bcdb
2016-05-20Merge branch 'maint'Juuso Lapinlampi
Sync with Pomf 2.0.x maint branch. - css: Add missing Bootstrap license header (Expat)
2016-05-20css: Add missing Bootstrap license header (Expat)Juuso Lapinlampi
Bootstrap is a CSS framework by Twitter, Inc. Pomf uses certain Bootstrap 3 elements, such as .jumbotron and .alert. The credit is due for Twitter, Inc. for Bootstrap, which like Pomf is free software licensed under the Expat license. The CSS snippets about Bootstrap were initially introduced to style.min.css in commit df6cf936d7ef3a819c6ff484b24a8cb5946726a9, then moved into pomf.css uncompressed in commit 152c0257a8ef9a8da7e45717a65578c340a7c178. See: https://getbootstrap.com/ Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
2016-05-08CHANGELOG: Fixup line length to 80 characters (v1.0.0)Juuso Lapinlampi
One v1.0.0 change log line was too long and to wrapped to 80 characters. Fixes commit e09581c06b8340309f86d2dc3ef2a5cd4defeaae.
2016-05-08Merge branch 'wub/expand-1.0.0-changelog'Juuso Lapinlampi
- CHANGELOG: Add full change logs for 1.0.0+8757e9a - CHANGELOG: Track changes to v1.0.0 instead of 1.0.0 - CHANGELOG: Add Pomf 1.0.0 changes since initial commit (ewhal@ admitted he's not going to spend four hours into reviewing the accuracy of these commits, but gave me an OK.) Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
2016-05-08CHANGELOG: Add full change logs for 1.0.0+8757e9aJuuso Lapinlampi
Replaces 1.0.0+8757e9a change log stub with verbose, full change logs. I am so glad I did not have to write every single moe panel change and README.md comment about how moe panel is shit into these logs. The commit history is awful around v1.0.0 and 1.0.0+8757e9a. There are some things here that I took liberally, for example cenci0's case 413 decoding hack which in turn was actually a bug itself and fixed later in 2.0.x. So, I simply called it a "HTML validation" fix. While we are here, clarify that there was no formal release for this version.
2016-05-08CHANGELOG: Track changes to v1.0.0 instead of 1.0.0Juuso Lapinlampi
As explained in v1.0.0 tag message, the 1.0.0 tag is incorrectly positioned to mark a release. v1.0.0 is the superset at the point when it was merged to nokonoko/Pomf.
2016-05-08CHANGELOG: Add Pomf 1.0.0 changes since initial commitJuuso Lapinlampi
Replaces stub 1.0.0 change logs with verbose ones. tits.php was added but then removed before it made into the 1.0.0 "release", and thus not mentioned in these change logs. Grunt was added in, but Swig pages only came in the next commit and the Git history is linear rather than branched. Thus, 1.0.0's Grunt build system is "broken" and only partially implemented.
2016-05-08CHANGELOG: Add "Getting help" fix to Pomf 2.0.2Juuso Lapinlampi
See: 617c4409e76b4a86316c81b50ff1edca70b329e2
2016-05-08Merge branch 'maint'Juuso Lapinlampi
Sync with Pomf 2.0.x maint branch fixes. - README: Add #pomf on Partyvan to getting help
2016-05-08README: Add #pomf on Partyvan to getting helpJuuso Lapinlampi
It turns out that moving to Rizon's IRC network was a bad idea after all. One or more developers (myself included) are unable to connect to Rizon for using Tor or operating Tor exits. Now there's this split: Users and Pomf site maintainers are on #pomfret on Rizon (where I don't have frequent access) and development has moved back to #pomf on Partyvan (where there's also #/g/hostingtalk). Given how I personally play such a big role in leading Pomf development, it has no longer been practical to continue development communication on an IRC network I can't access. There was no interest to finish setting up a mailing list for Pomf development because IRC was considered more important. Thus, the stagnation and stalled development of pantsu/pomf between 2016-01-31 and 2016-04-30 as seen in commit logs. There used to be an IRC channel called #pantsucat on Partyvan's IRC network, before development moved to Rizon. That channel is no longer active. See: pantsu/pomf@5846ba7ccb1aa6af2850b3fcf34c6bd396995161 Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
2016-05-07CHANGELOG: Remove erroneous extra whitespace (2.0.1)Juuso Lapinlampi
2016-05-07Deprecate underscores in PHP function namesJuuso Lapinlampi
camelCase is the preferred coding style for function names in the PSR-2 coding style guide used by Pomf since version 2.0.0. Reference: http://www.php-fig.org/psr/psr-2/
2016-05-07Deprecate get_sha1() in Pomf 2.1.0Juuso Lapinlampi
There are two issues with get_sha1(): - The function name doesn't follow the PSR-2 coding style guide for function naming, followed in Pomf since version 2.0.0. - SHA-1 is no longer considered resilient to collisions, versus SHA-256. In current plans, this feature is to be replaced with getHash() or similar function name in the next major version (Pomf 3.0.0). For consideration for future SHA-256 hashing implementation, the MySQL schema's hash value needs to be changed from char(40) to char(64) to accommodate the longer SHA-256 length of 64 bytes in hexadecimal string.
2016-05-07CHANGELOG: Add missing "the" article (grammar fix)Juuso Lapinlampi
2016-05-07Deprecate file expiration support in Pomf 2.1.0Juuso Lapinlampi
File expiration support has never been properly implemented in Pomf core or moe panel. It serves as legacy baggage before nekunekus got an idea to create nokonoko/Uguu for temporary uploads. In current plans, this non-feature will be removed in the 3.0.0 release which is the next SemVer major version that allows to remove this. Reviewed-by: Austin Gillmann <alucard@cuntflaps.me>
2016-05-04CHANGELOG: Fixup for missing Markdown code tagsJuuso Lapinlampi
Fixes commit 6495e3a214e6c745f06a9b842ef2e59a9c116c7c. Also fix the incorrect name of Gruntfile to Gruntfile.js. Reference: http://www.cirosantilli.com/markdown-style-guide/#what-to-mark-as-code
2016-05-04Merge branch 'wub/update-changelog'Juuso Lapinlampi
- CHANGELOG: Add notes for unreleased 2.0.2 so far - CHANGELOG: Update notes for unreleased 2.1.0 so far Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
2016-05-04CHANGELOG: Update notes for unreleased 2.1.0 so farJuuso Lapinlampi
Add a mention about HTML metadata generator value.
2016-05-04CHANGELOG: Add notes for unreleased 2.0.2 so farJuuso Lapinlampi
2016-04-30Merge branch 'maint'Juuso Lapinlampi
Sync with latest maint branch bugfixes. - Fix/Update LibreJS @source URL to cgit tree - Change package.json bugs contact to bugs@pantsu.cat email, remove URL - package.json: Use lowercase pomf for package name - Gruntfile: Sort grunt-swig options alphabetically Conflicts: Gruntfile.js
2016-04-30Gruntfile: Sort grunt-swig options alphabeticallyJuuso Lapinlampi
Code cleanup, that's all. Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
2016-04-30package.json: Use lowercase pomf for package nameJuuso Lapinlampi
One of NPM's rules [1] is: "New packages must not have uppercase letters in the name." This also follows the convention where Git repository names are lowercase. This change is mostly irrelevant to us, but it's a bug nonetheless. There's no concern over backwards compatibility regarding SemVer as far as I'm aware. This bug was introduced in 7d28ef53a8166cbdcb558a84d5a53cfd73472438. [1]: https://docs.npmjs.com/files/package.json Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
2016-04-30Revert "Remove bugs URL from package.json", set emailJuuso Lapinlampi
Actually on second thought, SemVer doesn't allow us to remove functionality without incrementing the major version number... which we don't want to do for this. Set the bugs email address to bugs@pantsu.cat. Hoping here bugs@ to be an alias to ewhal@ for the time being until a real mailing list will be reachable at that address. This fixes the issue for the time being without removing functionality. It is okay that we made a mistake. We don't need to increment the major version here now, because no release was tagged and released in this branch. Nevermind that Pomf isn't even published on NPM packages, so this "feature" is never seen in its current form in the npm(1) program. We'll still respect SemVer, for what little worth it may be to other tools. This reverts commit 310d8d9fdd33826b9a6d5c1f9b1f8aa1c373c461. Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
2016-04-30Remove bugs URL from package.jsonJuuso Lapinlampi
Why is this a thing? We never used pantsu/pomf issue tracking. It was disabled a long time ago in gogs, and now it doesn't even exist. For consideration, we could provide an email address here. There's no mailing list for bugs (yet) and it's unlikely to see one soon. Compliments commit bf4fbf5f8718c4668a57d7dc09880deb904fef1b. Inspired by ~alucard/pomf at Cuntflaps, though never reported to us. Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
2016-04-30Fix/Update LibreJS @source URL to cgit treeJuuso Lapinlampi
git.pantsu.cat has switched from gogs to cgit. gogs used a slightly different URLs to point to tree, so the old URLs from gogs are no longer valid. For consideration, to ease maintenance we'll just keep pointing the URL to the master branch and not a specific commit or maint branch. ?h=master is not really required here, it's the default branch. I am aware that the current maint and master branches diverge heavily from each other in terms of JavaScript, but this will be an issue that will disappear eventually. Thus, this is the simplest fix. A HTTP redirect will be setup for the old URL to the new one (eventually) to fix broken links. Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
2016-04-30Merge branch 'maint'Juuso Lapinlampi
Sync with v2.0.1 maint branch. Doing this sync any later would make me insane and lost.
2016-04-30Merge branch 'wub/add-html-meta-generator'Juuso Lapinlampi
Add `<meta name="generator" value="Pomf x.y.z">` to page layout, where x.y.z is the current Pomf version number defined in package.json with the help of Grunt. This change is done to satisfy WHATWG's HTML standard, section 4.2.5.1 Standard metadata names. Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
2016-04-30pages: Get metadata generator value from pkg.versionJuuso Lapinlampi
Instead of hardcoding the version number and duplicating version strings in markup, have Grunt grab the version value from package.json. Adds Gruntfile value pkgVersion. For consideration, this will cause some issues in efforts to remove Grunt from Pomf 3.x branch. Right now it's still considerably the best or simplest thing we can do. Suggested-by: Eliot Whalan <ewhal@pantsu.cat> Suggested-by: Austin Gillmann <alucard@cuntflaps.me>
2016-04-30pages: Add metadata generator value to <head>Juuso Lapinlampi
WHATWG's HTML standard vaguely implies in section "4.2.5.1 Standard metadata names" that documents that lack a metadata generator value were written by a user in a text editor. This is not the case for Pomf. The next Pomf release is expected to be version 2.1.0, which was picked here for the value. While we are here, update copyright year to 2016 for this template.
2016-01-31Deprecate Swig bannersJuuso Lapinlampi
I have a belief that Swig banners are a Grunt only thing, and they don't really integrate very well into Swig anyway. It's kind of a hack, and a bad one because we don't need it anymore. By deprecating Swig banners, we should have easier time replacing Grunt/npm with Make in a future release. Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
2016-01-31Merge branch 'wub/add-changelog'Juuso Lapinlampi
Add CHANGELOG.md with human readable change logs for 1.0.0..HEAD. The change log adheres to "Keep a CHANGELOG" [1] convention, not GNU standards. Release notes for 1.0.0 and 1.0.0+8757e9a are stubs. [1]: http://keepachangelog.com/ Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
2016-01-31CHANGELOG: Add initial release notes for Pomf 2.1.0Juuso Lapinlampi
Pomf 2.1.0 has not been released yet, but we're keeping track of changes anyway as per "Keep a CHANGELOG" [1] guidance. Thus, the date is marked "Unreleased". More changes will be tracked as development will continue and progress forward. [1]: http://keepachangelog.com/
2016-01-31CHANGELOG: Add release notes for Pomf 2.0.1Juuso Lapinlampi
2016-01-31CHANGELOG: Add stubs for 1.0.0 and 1.0.0+8757e9aJuuso Lapinlampi
2016-01-31Add CHANGELOG.md for Pomf 2.0.0Juuso Lapinlampi
Includes changelogs for 1.0.0+8757e9a..v2.0.0. The format used is "Keep a CHANGELOG" [1] as a result of conversation with Eliot. For future improvement, changelogs for newer releases (e.g. v2.0.1 and unreleased v2.1.0) should be written. [1]: http://keepachangelog.com/ Acked-by: Eliot Whalan <ewhal@pantsu.cat>
2016-01-28Change package.json version to 2.0.1Juuso Lapinlampi
This marks the Pomf 2.0.1 release. Sorry again that the changelogs didn't make it to this release - we're working on it. Hopefully.
2016-01-27Merge branch 'maint' (sync)Juuso Lapinlampi
Sync with maint branch to merge two patches to master.
2016-01-27Merge branch 'wub/2.0.0-response-patches' into maintJuuso Lapinlampi
- Add missing newline to Response.class.php - Fix undeclared vars in html_success() and text_success() Reviewed-by: Eliot Whalan <ewhal@pantsu.cat> Reviewed-by: clsr <clsr@clsr.net>
2016-01-27Fix undeclared vars in html_success() and text_success()Juuso Lapinlampi
As explained by clsr: > <clsr> With default PHP settings, that'd print a warning, then treat > $result as if it was an empty string before appending. This bug was introduced in commit a92961f24072bc4c3881bf0e2f609562f3703471 and 1411bce1dc13bf6fea66b5899ba29d50d5c53bb0. Reported-by: clsr <clsr@clsr.net> Suggested-by: clsr <clsr@clsr.net>
2016-01-27Add missing newline to Response.class.phpJuuso Lapinlampi
Right before text_error(), there was a missing newline. This bug was introduced in commit a92961f24072bc4c3881bf0e2f609562f3703471.
2016-01-21Merge branch 'maint'Juuso Lapinlampi
Sanity merge. Instead of merging feature branches to both maint and master, we should merge them to maint and then merge maint to master as per gitworkflows(7). This makes sure the branches are in sync and there will be no issues later on. It also simplifies git-log(1) with --graph. Fixes disperancy with `git log master..maint`, which should not list any commits. My fault.
2016-01-21Merge branch 'ewhal/remove-unused-css'Juuso Lapinlampi
Remove page specific style rules. These are unused relics from before 2.0.0 release. This merge compliments 7743e0ec4e1c71e7cc0e0df6203e02d221c82721, which was merged too early.
generated by cgit v1.2.3 (git 2.25.1) at 2026-10-22 18:30:39 +0200