aboutsummaryrefslogtreecommitdiffstats
path: root/include/items.php
Commit message (Collapse)AuthorAgeFilesLines
* try to reduce the number of simulaneous deliveries of the same post when ↵friendica2014-01-221-13/+20
| | | | dealing with owner relays that have more than one channel instance. If things melt down in the next few hours and I'm not available please revert this. I've reviewed a few times and think it's OK, but this part of the delivery code is traditionally touchy.
* dav: throw exception if channel for requested DAV directory is deletedfriendica2014-01-151-2/+4
|
* some minor cleanup on plinks for some very subtle permissions issuesfriendica2014-01-091-8/+10
|
* use display/ plinks for commentszottel2014-01-091-3/+2
|
* save channel/<channel>/?mid=... plinks with the itemszottel2014-01-091-2/+9
|
* a few fixes to webpage editingfriendica2014-01-041-0/+49
|
* modify tag_deliver and tgroup_check to handle exclusion tagsfriendica2013-12-291-2/+2
|
* remove a couple of mysql reserved words from being used as table or row ↵friendica2013-12-221-1/+1
| | | | names. For this round we're getting 'group' and 'desc'. Warning: potentially destabilising as this touches a lot of code.
* sourced items which are then edited at the source weren't setting up the ↵friendica2013-12-191-1/+8
| | | | second delivery chain.
* Tricky little bug. Allowed somebody to bypass comment permissions. Hopefully ↵friendica2013-12-161-3/+4
| | | | the fix will have no undesired side effects.
* issue #240 - we were using htmlentities instead of htmlspecialchars in ↵friendica2013-12-111-36/+35
| | | | several places, and this was a bit greedy in the set of characters which were converted from utf-8 to HTML entities. Also brought mail attachments up to date so they are rendered identically to item attachments.
* suggestion widget tweaked to make it comanche capable. Remove old versions ↵friendica2013-12-081-3/+9
| | | | of specs that are so obsolete it isn't funny. Zot protocol reference is in red's github wiki, and in the code. We should move the github copy to /doc once it is updated to match the code. There's no point in documenting dfrn in the red code base.
* post_activity_item issuesfriendica2013-12-071-5/+23
|
* include re-organisation and more doco, post_to_red fix ampersands in categoriesfriendica2013-12-041-23/+19
|
* deprecate a->get_curl_code() and $a->get_curl_headers()friendica2013-12-011-192/+0
|
* item store hooksfriendica2013-11-281-0/+15
|
* more loop preventionfriendica2013-11-261-0/+8
|
* ensure that drop_item doesn't recursefriendica2013-11-261-1/+1
|
* add drop_item hookfriendica2013-11-261-0/+3
|
* webpage edit - losing the ability to pass unfiltered html and perhaps some ↵friendica2013-11-201-3/+2
| | | | php due to unsetting uid too early in item_store_update()
* Protocol: now set data['alg'] on all encapsulated encrypted packets, so that ↵friendica2013-11-201-13/+13
| | | | we can more easily retire 'aes256cbc' once it is no longer viable.
* magic auth issuesfriendica2013-11-171-1/+1
|
* fix commented timestampfriendica2013-11-171-3/+4
|
* better job of setting parent createdfriendica2013-11-171-7/+4
|
* pull in some posts when we first connect with a new channel (if allowed to) ↵friendica2013-11-171-7/+20
| | | | - if not allowed to, do it if that condition changes
* populate some posts when somebody is granted "read stream" permissionfriendica2013-11-171-0/+5
|
* allow private mail sender to set an expiration on their messages. Once ↵friendica2013-11-061-0/+6
| | | | expired the message is destroyed at both ends (subject to the granularity of the polling interval) and is gone. Officially it takes some form of language independent string like 2013/11/22, but English speakers can use anything that strtotime() understands, like "+30 minutes" or "next Tuesday".
* private tagged posts weren't creating second delivery chain - they were ↵friendica2013-11-041-1/+14
| | | | incorrectly being marked as "in a reshare" due to being obscured.
* prevent posts from floating to the top after minor editsfriendica2013-10-191-1/+6
|
* turn off endless scroll if we have no more content to load - currently for ↵friendica2013-10-131-0/+1
| | | | mod_display, need to add to other content modules
* preserve the source owner when creating a delivery fork so that we can ↵friendica2013-10-131-4/+28
| | | | uplink back to them without any ambiguity.
* fix a bunch of post editing bugs - though this consolidates some disparate ↵friendica2013-10-041-23/+33
| | | | code and may create some new bugs due to regression
* post signaturesfriendica2013-10-021-46/+91
|
* implement republish permission for use in sourced channelsfriendica2013-09-301-0/+11
|
* RSS feeds as channel sources. It's feasible and within reach, however ↵friendica2013-09-291-45/+35
| | | | | | | | there's a lot of work left to do. How bad does anybody want it? Let's find out...
* Issue #158friendica2013-09-291-2/+2
|
* close commentfriendica2013-09-281-1/+1
|
* fix can_comment_on_post when viewing wall-to-wallfriendica2013-09-281-5/+16
|
* convert to plaintext before matching words in body. Otherwise every post I ↵friendica2013-09-261-1/+5
| | | | make with a link in it is going to match a test for zot.
* aggregate channelsfriendica2013-09-261-26/+86
|
* Add explanation why public comments are disabled.Olaf Conradi2013-09-261-1/+5
|
* bug #150, if deny access is present but nobody has been allowed, create an ↵friendica2013-09-221-1/+22
| | | | allow list containing everybody in your address book. Then subtract those who are denied.
* hopefully(?) the final word on remote comment permissionsfriendica2013-09-201-3/+1
|
* fix contact comment permissionsfriendica2013-09-201-1/+6
|
* hopefully this will go over a bit better - check post owner permissions as ↵friendica2013-09-201-1/+3
| | | | well as local owner permissions for comments during submission, since the comment was being blindly accepted on the local system due to only checking the profile owner. Also change collections query to include only top-level posts by a member of the collection.
* sync item_search with yesterday's network fix for collections. Add ud_addr ↵friendica2013-09-191-6/+12
| | | | to update table to store the target address since it's possible the mirroring directory won't yet have an xchan or hubloc they can link the ud_hash to and therefore mayn't know how to contact them.
* doc update, put more telemetry on notifier and try to ensure that private ↵friendica2013-09-131-0/+3
| | | | posts have recipients.
* remove some debugging stuff now that the problem they were trying to locate ↵friendica2013-09-121-5/+0
| | | | down has been solved.
* make comments work againfriendica2013-09-101-1/+2
|
* well that really stuffed things up...friendica2013-09-101-1/+1
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-23 23:16:25 +0000