aboutsummaryrefslogtreecommitdiffstats
path: root/util
Commit message (Collapse)AuthorAgeFilesLines
* comanchify mod_search - we've got three modules left to Comanchify: admin, ↵friendica2013-12-201-1077/+1053
| | | | directory and message - each of which introduces "interesting challenges"
* add construct_page hookfriendica2013-12-131-1308/+1152
|
* yeah - that's what I'm going to do. we'll just keep system notifications. If ↵friendica2013-12-061-0/+7178
| | | | somebody wants web pages for the others we'll start fresh. It's easier than starting with curfty friendica code that doesn't work anymore and will never work without starting over.
* some code cleanup - gad I forgot what a mess the "other" notifications tabs ↵friendica2013-12-061-7208/+0
| | | | (everything but system) were in. Maybe I'll just remove them so we can start over.
* include re-organisation and more doco, post_to_red fix ampersands in categoriesfriendica2013-12-041-1/+1
|
* undo last change to comment_email - these are checked for validityfriendica2013-12-021-1/+1
|
* ensure that every imported channel has a primary hublocfriendica2013-12-021-1/+1
|
* add categories and optional backlink to exported WP postsfriendica2013-12-011-7/+28
|
* channel wasn't getting savedfriendica2013-11-291-0/+2
|
* allow zot-info to return results for address= with webbies or naked nicknamesfriendica2013-11-291-3446/+3479
|
* Plurals for conversation.phpOlivier Migeot2013-11-281-3485/+3478
|
* synchronise deletion of comments between red and wpfriendica2013-11-281-0/+33
|
* add photos to red-to-wordpress commentsfriendica2013-11-271-0/+20
|
* add xmlrpc method for importing red commentsfriendica2013-11-271-0/+81
|
* add terms and categories, fix a delivery loop (stops at one cycle but we ↵friendica2013-11-261-1/+1
| | | | don't need a post coming back that we just sent out).
* link the plugins at both ends so that each can discover a post that was ↵friendica2013-11-261-11/+6
| | | | imported/exported to/from the other and keep track of updates accordingly
* delete from the wp side as well as from the red sidefriendica2013-11-261-14/+38
|
* api fixesfriendica2013-11-261-1/+10
|
* wp-to-red: now supports editing, titles, and native permalinksfriendica2013-11-251-3/+8
|
* wordpress publish hook was called before the meta storage hook so the plugin ↵friendica2013-11-241-5/+14
| | | | would only work on edited posts. This may be a wordpress version issue because you'd think somebody would've noticed it before.
* Add some message_id meta information for wordpress posts so we'll know where ↵friendica2013-11-241-1/+5
| | | | to send comments
* wordpress-to-red cross-posting tool ported from Friendicafriendica2013-11-242-0/+325
|
* replaced rhash icontuscanhobbit2013-11-231-1/+1
|
* init_groups_visitor() was still using old array of id output (not the newer ↵friendica2013-11-221-400/+396
| | | | array of hash which we need for permission queries)
* redbasic - set pixel dimensions of conversation top author photo and reply ↵friendica2013-11-151-363/+413
| | | | author photos. Hint: if you set these to something like 64px and 32px respectively and reduce the main font-size to say 0.9em, young people won't complain as much about the "ugly dated UI". You see they're used to companies squeezing every pixel out of the screen (more room for advertising) and they don't yet have bad eyes so they can still read teeny stuff. Big fonts and pictures are for old folks that need glasses and make young people complain about the "dated" interface. It's a sure sign that you're going to find old folks here and not many young adults or teens. What's missing at the moment is that if you shrink these photos, the "item-photo-menu" arrow is no longer in the bottom corner of the picture, but might be outside the photo. Will have to see if there's a way to dynamically position this based on the size.
* doc updatefriendica2013-11-091-588/+710
|
* doc updatesfriendica2013-11-021-159/+190
|
* string updatefriendica2013-10-261-109/+121
|
* Put a status editor on the display page if you're logged in. This fixes ↵friendica2013-10-181-150/+189
| | | | issue #113 and also provides the ability to reshare from that page.
* wrong app namefriendica2013-10-161-2/+2
|
* bug 175 - categories not updated when editingfriendica2013-10-111-143/+232
|
* fix a bunch of post editing bugs - though this consolidates some disparate ↵friendica2013-10-041-808/+893
| | | | code and may create some new bugs due to regression
* string updatefriendica2013-09-281-536/+589
|
* rev updatefriendica2013-09-201-1085/+1099
|
* add -C cfgfile option to shred to allow multiple configurations. I just ↵friendica2013-09-171-1/+4
| | | | added the option for multiple configs, I didn't make it work as it requires quite a bit of change to the shred program flow; which tries to load the default config before doing anything at all.
* several oauth fixes - shred doesn't completely work yet, but it also doesn't ↵friendica2013-09-164-0/+727
| | | | completely NOT work, so at least there's some improvement
* doc update, put more telemetry on notifier and try to ensure that private ↵friendica2013-09-131-365/+427
| | | | posts have recipients.
* provide mimetype selector on edit (pages and blocks)friendica2013-09-061-299/+376
|
* more debugging on localize_item top find out why likes are not translated in ↵friendica2013-08-311-313/+307
| | | | notifications, but are in displayed posts (using 'new' on matrix page) - in one case we're successfully pulling stuff from item['object'] and in the other we aren't - and it's the same object.
* fix xchans more completely after a URL changefriendica2013-08-241-834/+893
|
* issue #82, posted order not working - also doc updatefriendica2013-08-171-478/+656
|
* util/pconfig - if you understand util/config you'll understand this; if you ↵friendica2013-08-141-0/+34
| | | | don't you won't
* string parse error extracting one particular stringfriendica2013-08-093-1279/+1424
|
* move sitekey creation to the account creation function instead of during ↵friendica2013-08-091-328/+285
| | | | channel creation. Channel import bypassed sitekey creation completely. We should do it during install, but it's possible somebody might have to install manually and the sitekey would never get created. This is the best compromise I can come up with. Looks like the doc tree was also updated in this checkin
* basic email invitations - and doc updatefriendica2013-08-021-315/+315
|
* add gz to access denied files to block rotated logs from public accessfriendica2013-07-261-435/+412
|
* private pokes - perhaps a little *too* private.friendica2013-07-191-379/+389
|
* Add self to recipient lists. Sure we already have a copy but it's possible ↵friendica2013-07-141-561/+598
| | | | our nomadic channel clones don't.
* use current channel photo for favicon where applicable - might be browser ↵friendica2013-07-071-308/+382
| | | | dependent but seems to work on FF
* doc update, plus possible fix to "complex delivery chains" issue. Basically ↵friendica2013-06-291-422/+422
| | | | when the top-level post creator replies to a thread he sent to a forum via tags, it isn't getting redelivered to the forum members.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-10 15:31:15 +0000