aboutsummaryrefslogtreecommitdiffstats
path: root/include/items.php
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
* this should fix the foreign language like notifications (again)friendica2013-09-101-2/+4
|
* change wording on item_store message so we can find failures fast with grep ↵friendica2013-09-101-1/+1
| | | | item_store logfile | grep -v created
* provide detailed error to remote site for the myriad of things that can go ↵friendica2013-09-101-19/+44
| | | | wrong inside item_store(), !! this changes the return of item_store !!
* pages feedfriendica2013-09-051-15/+29
|
* issue #59 - this is a real bugger. Might seem fixed but read the code. This ↵friendica2013-09-041-2/+7
| | | | could potentially create a security/permissions issue
* fix private message encryption since the input_filter mangled itfriendica2013-09-031-2/+2
|
* webpage content-type -- needs cleaning up and a security check once all the ↵friendica2013-09-021-7/+3
| | | | important bits are in place.
* Sheesh. Three lines of Javascript. All you have to do is find which of the ↵friendica2013-09-011-0/+11
| | | | three lines is doing something wrong. Or FILE A BUG. Or use a different browser (not *try* a different browser, *use* a different browser), or turn off freaking tinymce. But no - let's argue about browsers instead.
* get rid of ssl_policy - it's implicit in the site urlfriendica2013-08-271-16/+16
|
* email attachments (and fix email photos)friendica2013-08-191-0/+10
|
* item_store logging to discover where object is getting quote mangled.friendica2013-08-181-1/+4
|
* Another try at issue #61 and #62 - an earlier fix was partially working but ↵friendica2013-08-181-9/+14
| | | | the issue persisted - this extends it a bit.
* don't include archived contacts in public posts, unless specifically requestedfriendica2013-08-151-2/+3
|
* typofriendica2013-08-141-1/+1
|
* fix expire so it actually should expire stuff; and mostly the correct stuff ↵friendica2013-08-141-11/+17
| | | | - though it DOESN'T currently send out notifications to connections
* important bits we need to allow php executable content. These must be ↵friendica2013-08-111-18/+35
| | | | explicitly allowed - but only if the account has ACCOUNT_ROLE_ALLOWCODE and *only* for web pages and profile fields. This content cannot be transmitted to other sites.
* remove some un-needed codefriendica2013-08-071-1320/+10
|
* convert all stored json calls to json_decode_plus()friendica2013-08-061-9/+9
|
* add extra logging to tag_deliverfriendica2013-08-051-2/+6
|