CutCodeDown
Squire / Paladin => Milestones => Topic started by: Jason Knight on 7 Dec 2020, 02:29:37 am
-
https://cutcodedown.com/paladinX/milestone_07_Dec_2020_07_13/
This release has been bugfixed for PHP 8, and should still work in 7.x
It has also undergone far more rigourous testing than previous versions, and thank you very much all of you for the bug reports it is greatly appreciated. A set of proper "function testing" for both expected and unexpected results is being added on my end.
You can review the changes in the new fancy formatted changelog:
https://cutcodedown.com/paladinX/milestone_07_Dec_2020_07_13/changeLog.html
If you're interested in an overall directory structure, that's here:
https://cutcodedown.com/paladinX/milestone_07_Dec_2020_07_13/directory.html
Be warned again this is ALPHA and highly subject to change. In fact the next milestone is going to see some directory restructuring to make the application of new pages, extra's, and modals a bit more uniform. They're all just different types of page subsections, so let's treat them as such. The next version may not be structurally compatible for those of you trying to actually use this for production since again....
ALPHA, it's not even function complete yet.
Note, next milestone's changelog will start giving credit to bug reporters. If you have a preference to how you'd like to be credited please speak up!
-
This Milestone has been added to my repo. You can see exact changes here
https://github.com/benanamen/paladinx/commit/8a0773a158eff667b1ec32a62d4541d98ac82a93 (https://github.com/benanamen/paladinx/commit/8a0773a158eff667b1ec32a62d4541d98ac82a93)
FYI: Be aware, if you overwrite your files that the DB name has been changed from paladin to paladintesting
-
Great looking change log. How are you managing it?
Bug: You have td closing th in the changelog.
-
FATAL ERROR PHP 7/8
Triggered by adding user using spaces only in all fields except email.
Warning: Undefined variable $Settings in C:\laragon\www\paladinx\paladin\actions\admin\pages\users\users.create.process.php on line 54
Fatal error: Uncaught Error: Class name must be a valid object or a string in C:\laragon\www\paladinx\paladin\actions\admin\pages\users\users.create.process.php:54 Stack trace: #0 C:\laragon\www\paladinx\paladin\actions\admin\pages\users\users.process.php(24): adminUser_create_process(Object(Database), Array) #1 C:\laragon\www\paladinx\paladin\actions\admin\admin.process.php(51): admin_subProcess(Object(Database), Array) #2 C:\laragon\www\paladinx\paladin\libs\squire.lib.php(81): process_action(Object(Database), Array) #3 C:\laragon\www\paladinx\paladin\libs\main.lib.php(42): action(Object(Database)) #4 C:\laragon\www\paladinx\paladin\index.php(22): main('mysql:dbname=pa...', 'paladin_user', '', Array, 'paladin') #5 {main} thrown in C:\laragon\www\paladinx\paladin\actions\admin\pages\users\users.create.process.php on line 54
-
FATAL ERROR PHP 7/8
Simple typo. Had "$Settings" where it should be just Settings.
#00039
-
FYI: Be aware, if you overwrite your files that the DB name has been changed from paladin to paladintesting
#00040, bug in milestone generator, will go back in next release.
-
Great looking change log. How are you managing it?
Bug: You have td closing th in the changelog.
Same way I have for 30 years. Flat text file with the lines in a specific order. An asterisk indicates the start of a new item, followed by the status, then the code, then the title, then any number of lines until the next item is the description. A line starting with an =sign indicates a milestone, which is added automagically by the milestone maker if the first line of the file isn't one.
*
FIXED
00041
changelog.html /td closing th
Logic error in generator, easy fix.
*
FIXED
00040
default tablename changed to paladinTesting, should be just "paladin"
Bug in milestone generator.
*
For example. Normally I leave it at that, but it's easy enough to read that format into almost anything with just a handful of lines of code. Empty lines and multi-lines are <br> separated in the markup conversion for the description TD.
I SHOULD probably at some point use something "real" for that with creation and last update timestamps, but it's how I've always done it and how project managers USED to do this stuff before Git and its ilk came along. It never used to matter "when" just so long as it got done.
There's a lot of minutia like that people spend time on now that back in the day we never wasted time on... typically on projects way bigger than anything you'd build with a insecure scripting glue like PHP.