| fe9d054b | 15-Jan-2024 |
Andreas Gohr <andi@splitbrain.org> |
Feed creation refactoring
This breaks up the humongous functions from feed.php into multiple classes. To keep compatibility with existing Plugin events, the basic principle of how the feed is assemb
Feed creation refactoring
This breaks up the humongous functions from feed.php into multiple classes. To keep compatibility with existing Plugin events, the basic principle of how the feed is assembled has not been changed:
* depending on the given mode and other options lose arrays of items are gathered * these items are then converted (again based on the various options) into proper FeedItems * the FeedItems are then added to the Feed
The conversion from loosely typed item data to something more structured is now done by the FeedItemProcessor classes. Some very basic tests have been added. It does not cover erverything but covers more than before (which was nothing).
Manual testing before merging this is highly recommended. I am not confident that I ported over everything correctly.
No new features have been added, but especially media support could and should be improved in the future.
show more ...
|
| ac56bec8 | 17-Jan-2024 |
Andreas Gohr <andi@splitbrain.org> |
fall back to empty (root) dir for base dir detection
When a basedir could not be detected, the default previously was '.' resulting in a valid but weird URL (http://example.com/./doku.php). We now d
fall back to empty (root) dir for base dir detection
When a basedir could not be detected, the default previously was '.' resulting in a valid but weird URL (http://example.com/./doku.php). We now default to an empty dir, resulting in a more sensible URL of http://example.com/doku.php
This should not matter in real web server setups but will be in effect while testing.
show more ...
|
| b5284271 | 09-Jan-2024 |
Andreas Gohr <andi@splitbrain.org> |
API: add backward compatibility to API Version 11
This adds legacy support for the old API calls. This is mostly untested but should work. Returns might not be 100% compatible in all cases but I did
API: add backward compatibility to API Version 11
This adds legacy support for the old API calls. This is mostly untested but should work. Returns might not be 100% compatible in all cases but I did my best to return the same things as before.
This will be removed in the future of course and is just to not completely break any API usage immeadiately.
show more ...
|
| 7de5ac55 | 06-Jan-2024 |
Andreas Gohr <andi@splitbrain.org> |
Another argument parsing fix for ApiCall
When using named parameters, you can expect to be able to leave out any optional parameter and have it take it's default, even when you specify another "late
Another argument parsing fix for ApiCall
When using named parameters, you can expect to be able to leave out any optional parameter and have it take it's default, even when you specify another "later" parameter. Luckily we already know all the defaults from reflection anyway.
show more ...
|