Commit graph

654 commits

Author SHA1 Message Date
pewgeuges
46fc9a7c5f Adapt after the 2.5.9d1 accident. 2021-03-05 04:30:50 +01:00
pewgeuges
6b9e602d07
Sync filenames with SVN repo (#57)
Returns to the original file names for the `class/dashboard/` directory (for now at least)
2021-03-04 07:46:19 +00:00
pewgeuges
daf0a8612f WordPress Coding Standards compliance update. Stable Tag 2.5.10. Package version: 2.5.11d0.
git-svn-id: https://plugins.svn.wordpress.org/footnotes/trunk@2486043 b8457f37-d9ea-0310-8a92-e5e31aec5664
2021-03-03 18:58:03 +00:00
pewgeuges
dfcbdc6adc Undo last two commits affecting trunk/ but not the Stable Tag.
= Stable Tag value =
2.5.10 (unchanged)
= Commits undone =
- 2484038 (2021-03-02 05:29:18 +0000 (Tue, 02 Mar 2021)) committer: pewgeuges
-2484015 (2021-03-02 04:22:20 +0000 (Tue, 02 Mar 2021)) committer: pewgeuges
= Rationale =
By renaming a folder (and 3 out of 4 included files), the WordPress Coding Standards compliance upgrade (see changeset 2484015) has broken the traceability of the changes made to the following files:
- footnotes/trunk/class/dashboard/init.php
- footnotes/trunk/class/dashboard/layout.php
- footnotes/trunk/class/dashboard/subpage-diagnostics.php
- footnotes/trunk/class/dashboard/subpage-main.php

git-svn-id: https://plugins.svn.wordpress.org/footnotes/trunk@2485882 b8457f37-d9ea-0310-8a92-e5e31aec5664
2021-03-03 15:15:55 +00:00
ef6dd57310
Update version number to 2.5.10 (#54)
* Update version number to 2.5.10 (current stable tag)

See [here](https://github.com/markcheret/footnotes/pull/54#discussion_r585895136) for discussion; **stable tags only to be used until releases are automated**
2021-03-02 21:47:09 +00:00
pewgeuges
1fe04f9ac6 Sync metadata in trunk/ with current release 2.5.10 (no d version).
git-svn-id: https://plugins.svn.wordpress.org/footnotes/trunk@2484038 b8457f37-d9ea-0310-8a92-e5e31aec5664
2021-03-02 05:29:18 +00:00
pewgeuges
c63d3f629f Update to standardised codebase as on GitHub origin/main/, 2.5.8. Stable Tag value set to 2.5.10 since it’s parsed to determine current release.
git-svn-id: https://plugins.svn.wordpress.org/footnotes/trunk@2484015 b8457f37-d9ea-0310-8a92-e5e31aec5664
2021-03-02 04:22:20 +00:00
pewgeuges
caf3e1136c Convert EOL from CRLF to LF.
to make footnotes/trunk/ diffable against the standardised codebase on GitHub markcheret/footnotes/.
Stable Tag remains 2.5.10.

git-svn-id: https://plugins.svn.wordpress.org/footnotes/trunk@2483994 b8457f37-d9ea-0310-8a92-e5e31aec5664
2021-03-02 03:09:34 +00:00
pewgeuges
ba9d9bc535 Revert to 2.5.8 in the new Stable Tag 2.5.10.
git-svn-id: https://plugins.svn.wordpress.org/footnotes/trunk@2483464 b8457f37-d9ea-0310-8a92-e5e31aec5664
2021-03-01 11:09:29 +00:00
8a859b61f7 Re-standardise codebase to WP Coding Standards (this time without the line ending changes)
git-svn-id: https://plugins.svn.wordpress.org/footnotes/trunk@2483354 b8457f37-d9ea-0310-8a92-e5e31aec5664
2021-03-01 07:57:12 +00:00
05d316ae15 Revert standardise codebase to WP Coding Standards
git-svn-id: https://plugins.svn.wordpress.org/footnotes/trunk@2483350 b8457f37-d9ea-0310-8a92-e5e31aec5664
2021-03-01 07:54:03 +00:00
6a5fcedac3 Standardise codebase to WP Coding Standards
git-svn-id: https://plugins.svn.wordpress.org/footnotes/trunk@2483336 b8457f37-d9ea-0310-8a92-e5e31aec5664
2021-03-01 07:37:59 +00:00
2e0b2f8d98
Merge pull request #50 from markcheret/wp-coding-standard--fresh
Update code to comply with WP Coding Standards (*fourth* time's the charm!)
2021-02-28 20:03:45 +00:00
f129f3a392 Renormalise line endings 2021-02-28 14:13:07 +00:00
pewgeuges
526cde8830 Release urgent bugfix v2.5.8 in response to Forum and per instructions/agreement.
= 2.5.8 =
- Bugfix: Layout: support right-to-left writing direction by replacing remaining CSS values left with start, thanks to @arahmanshaalan bug report.\n- Bugfix: Layout: support right-to-left writing direction by enabling mirrored paddings on HTML dir="rtl" pages, thanks to @arahmanshaalan bug report.

git-svn-id: https://plugins.svn.wordpress.org/footnotes/trunk@2483011 b8457f37-d9ea-0310-8a92-e5e31aec5664
2021-02-28 13:34:24 +00:00
pewgeuges
ef8050477b Backport upcoming bugfix release 2.5.8
Will be released in response to Forum and as agreed.
= 2.5.8 =
- Bugfix: Layout: support right-to-left writing direction by replacing remaining CSS values 'left' with 'start', thanks to @arahmanshaalan bug report.
- Bugfix: Layout: support right-to-left writing direction by enabling mirrored paddings on HTML dir=rtl pages, thanks to @arahmanshaalan bug report.
2021-02-28 14:24:57 +01:00
pewgeuges
8a01584196 Restore lost corrections 2021-02-28 00:53:50 +01:00
25c3f2f12e Replace output escape and input sanitization functions with linter supression messages 2021-02-27 08:49:08 +00:00
74ac6f1cad Rebase to 2.5.7 2021-02-27 08:34:58 +00:00
cbefa2e9d7 Add authorsfile to gitignore 2021-02-27 08:14:09 +00:00
f5b2e1f30f Rebase to 2.5.7 2021-02-27 08:12:17 +00:00
9c88d218a8 Revert "Update code to comply with WP Coding Standards (#38)"
This reverts commit 02c6c1c362.
2021-02-27 08:09:08 +00:00
dac7ffe3a6 Update code to comply with WP Coding Standards (#38)
Co-authored-by: @pewgeuges <pewgeuges@gmail.com>
2021-02-27 08:06:32 +00:00
8d0ebdb859 Append line endings 2021-02-27 08:03:04 +00:00
cf3616f65c Fix indentation 2021-02-27 07:55:43 +00:00
04d1bb390b Alter formatting, add contribution information 2021-02-27 07:55:43 +00:00
Mark Cheret
5c1884f059 Update README.md 2021-02-27 07:55:26 +00:00
Mark Cheret
75f4287aa3 Update CONTRIBUTING.md 2021-02-27 07:54:34 +00:00
Mark Cheret
6297965716 Update README.md
moved image due to repo change
2021-02-27 07:54:34 +00:00
Mark Cheret
9bce76c785 Update readme.txt
update minor language. How do we keep the readme's in sync?
2021-02-27 07:54:34 +00:00
Mark Cheret
0f22292941 Update README.md 2021-02-27 07:54:34 +00:00
5eec0ed6d7 Create SECURITY.md 2021-02-27 07:54:34 +00:00
0f41f1a735 Create LICENSE 2021-02-27 07:54:34 +00:00
6d8c32fc63 Add .phpdoc/ to gitignore 2021-02-27 07:54:34 +00:00
c93271ee65 Generate HTML documentation using phpDocumentor 2021-02-27 07:54:34 +00:00
8cf1930059 Create CONTRIBUTING.md 2021-02-27 07:54:34 +00:00
947a64844a Add more PHPCS tips 2021-02-27 07:54:34 +00:00
f465732b32 Add linting instructions and header image 2021-02-27 07:54:34 +00:00
09b065b463 Add footnotes header image 2021-02-27 07:54:34 +00:00
5ce214cf10 Add getting started instructions to README 2021-02-27 07:54:34 +00:00
b1c6f2fe62 Create README.md 2021-02-27 07:54:34 +00:00
0b1e7c2b0b Update issue templates 2021-02-27 07:54:34 +00:00
pewgeuges
92365f1176 This very urgent bugfix release contains just one added line of code, fixing the footnotes duplication bug.
= 2.5.7 =

- Bugfix: Process: fix footnote duplication by emptying the footnotes list every time the search algorithm is run on the content, thanks to @inoruhana bug report.

This release cannot be delayed as it responds to a user request with [bug report on the Forum](https://wordpress.org/support/topic/footnote-duplicated-in-the-widget/).
Fast-tracking emergency releases as per instructions received and previous agreement.

git-svn-id: https://plugins.svn.wordpress.org/footnotes/trunk@2482506 b8457f37-d9ea-0310-8a92-e5e31aec5664
2021-02-27 01:39:18 +00:00
600910d9ee Remove custom CSS output escaping 2021-02-26 14:40:23 +00:00
221b87a54f
Merge pull request #49 from markcheret/revert-38-wp-coding-standard--fresh
Revert "Update code to comply with WP Coding Standards (third time's the charm!)"
2021-02-26 12:01:21 +00:00
5982f12bd5 Revert "Update code to comply with WP Coding Standards (#38)"
This reverts commit 02c6c1c362.
2021-02-26 08:07:03 +00:00
02c6c1c362
Update code to comply with WP Coding Standards (#38)
Co-authored-by: @pewgeuges <pewgeuges@gmail.com>
2021-02-25 19:17:00 +00:00
pewgeuges
b4df058574
File header class/widgets/reference-container.php
Move date to its tag, …
2021-02-25 17:48:04 +01:00
pewgeuges
c8d526ebc1
Remove dates in class/widgets/base.php
Remove @‌lastmodified date.
Remove purely documentation related @‌date tag.
2021-02-25 17:35:16 +01:00
pewgeuges
422a6d1fa2 File level headings in class/layout/.
Move date to @‌date tag below the @‌since tag.
Delete @‌lastmodified tag as pointless, easily out of sync, and screwing things up when collaborating.
Need to mention however that in many projects, the last modified datestamp is applied and maintained.
That said, some published files on the web out there contain edits post-dating their datestamp.
2021-02-25 14:22:07 +01:00