aboutsummaryrefslogtreecommitdiffstats
path: root/include
Commit message (Collapse)AuthorAgeFilesLines
* cleanupfriendica2014-11-112-2/+9
|
* slow progress on sys publishing, making sure all the data we need is in the ↵friendica2014-11-112-2/+2
| | | | places we need it but validate it anyway
* a couple of places where we need to look for a sys channel euid.friendica2014-11-111-0/+7
|
* and urlencode that.friendica2014-11-111-2/+2
|
* Most directory searches are POST. get_query_args() only handles GET so that ↵friendica2014-11-111-1/+9
| | | | had to be fixed or page 2 of directory search results wouldn't match the search.
* the code is a bit crufty, but this should fix issue #687friendica2014-11-111-3/+10
|
* Merge https://github.com/friendica/red into pending_mergefriendica2014-11-101-3/+3
|\
| * Merge pull request #685 from zzottel/masterRedMatrix2014-11-111-3/+3
| |\ | | | | | | set channel_w_stream to 0 for forum roles
| | * set channel_w_stream to 0 for forum roleszottel2014-11-101-3/+3
| | |
* | | issue #683 - don't linkify homepage field without validatingfriendica2014-11-101-0/+2
|/ /
* | indicate public forums in directory results (there will be some [possibly ↵friendica2014-11-101-4/+5
| | | | | | | | considerable] lag time before existing forums are correctly tagged).
* | add public forum identification to libzot. No attempt is made to identify ↵friendica2014-11-101-2/+6
|/ | | | other types of forums or weird custom channel permissions. If the channel is auto-accept and taggable, it's a public forum.
* Use consistent terminology for channel directoryStefan Parviainen2014-11-091-1/+1
|
* tgroup_check - decrypt if obscured before checking body text for resharesfriendica2014-11-071-1/+9
|
* revert that bitfriendica2014-11-071-7/+1
|
* visible flag reversedfriendica2014-11-061-1/+1
|
* Provide a way to mark photos as adult and hide them from the default album ↵friendica2014-11-061-4/+10
| | | | view. Still need a button or setting to enable "unsafe viewing". This has no effect anywhere but in the album views. They can still be viewed by flipping through the individual photos with 'prev' and 'next'. We probably need a comprehensive strategy for how to deal with n-s-f-w photos in albums so consider this a band-aid which requires additional work and integration with other facilities which access these photos. It is entirely optional.
* don't overwrite $x (contains import_xchan result) with role permissionszottel2014-11-061-3/+3
|
* make sure the "tagcloud" actually shows hashtags. So we don't confuse folks ↵friendica2014-11-061-1/+1
| | | | with categories.
* category tagblockfriendica2014-11-062-0/+33
|
* logging changes, untranslated stringfriendica2014-11-052-4/+4
|
* some minor cleanup of unreported (and as yet undiscovered) issues with ↵friendica2014-11-052-2/+5
| | | | permissions toggling. No smoking guns and no obvious issues discovered here. Repeated and tried to duplicate zottell's issue as described without seeing any obvious problems.
* ok heads up - potentially destabilising change. I've tried to sort out all ↵friendica2014-11-045-29/+37
| | | | | | | | | | the default connection permissions for those who don't have a predefined (or therefore have a "custom") permissions role. Unfortunately this includes most people that were using this software more than a month ago. The real changes are that the SELF address book entry no longer holds "auto-permissions" but instead holds your "default permissions" (if you have a pre-defined role, the defaults will be pulled from the role table). The auto permissions have moved to a pconfig (uid.system.autoperms). A DB update will move these settings into their new homes. What used to be the "Auto-permissions settings" page is now the "default permissions settings" page and a checkbox therein decides whether or not to apply the permissions automatically. A link to this page will only be shown when you have the "custom" role selected. With luck nobody will notice anything wrong. But at least for the next few days, please review permissions that have been assigned to new connections (either automatically or manually) and make sure they make sense (e.g. they aren't "nothing"). You still need to take action when seeing a message "permissions have changed but not yet submitted" as we always let you review and perhaps adjust the settings _before_ a connection is established (unless you have autoperms turned on).
* Merge https://github.com/friendica/red into pending_mergefriendica2014-11-031-2/+3
|\
| * innodb issueThomas Willingham2014-11-031-2/+3
| |
* | various UI issues related to having an enormous number of entries in the ↵friendica2014-11-032-4/+20
|/ | | | posted_date selector including years/months that had no posts
* provide example import scriptfriendica2014-11-032-0/+376
|
* php warningsfriendica2014-11-021-23/+23
|
* I'm going to try again with the conversation request packets. I've looked ↵friendica2014-11-022-13/+60
| | | | this over and tested a lot of edge cases, and thought about from every angle I can think of to prevent looping. I don't *think* this can loop. I also doubt that this is the problem at friendicared.de, but I don't know for sure what that problem might be.
* add some more safety checks before turning the conversation request messages ↵friendica2014-11-022-4/+6
| | | | back on
* check that we have valid datafriendica2014-11-011-0/+1
|
* Merge https://github.com/friendica/red into pending_mergefriendica2014-11-011-1/+4
|\
| * Merge pull request #671 from pafcu/masterjeroenpraat2014-10-311-1/+4
| |\ | | | | | | Fix problem with default birth date
| | * Fix problem with default birth dateStefan Parviainen2014-10-311-1/+4
| | |
* | | disable request message response until we work through thisfriendica2014-11-012-1/+3
|/ /
* | document request packets a bit morefriendica2014-10-311-1/+4
| |
* | flag notify packets that are sent in response to a message_id request and ↵friendica2014-10-311-4/+5
| | | | | | | | prevent them from recursing
* | What this checkin does is catch the case where a comment arrived and there's ↵friendica2014-10-305-20/+163
| | | | | | | | a missing top-level post to match it with. So we'll send a request back to the sender that you've never seen this thread and please send a fresh copy of the entire conversation to date. We could soon have posts in the matrix from different platforms from days gone by, which have been migrated into the modern world. We'll be polite and not deliver these to everybody. However, if someone comments on one of these antique threads we wouldn't be able to see it in our own matrix because we won't have a copy of the parent post. So this rectifies that situation. Be aware that item deletion may need to change to keep "hard deleted" items indefinitely so that they don't keep coming back. We'll have to null out the important data of the former item to accomplish the deletion aspect.
* | if someone does not have permission to chat do not show the chatrooms tabmarijus2014-10-291-10/+12
| |
* | the default permissions for new connections when using a custom role is ↵friendica2014-10-281-1/+5
| | | | | | | | inadequate. Until we can make it configurable start off with something like a public social role. We're typically taking the person straight to the connection editor so they can change it before any privacy damage is done
* | several unrelated things - auto_follow wasn't working for new accounts, ↵friendica2014-10-272-0/+4
| | | | | | | | error returned in private mention to a collection, and added auto-completion to photo tags; though it only matches people so the hover text is now wrong. Also made the photo edit form XHTML (XML) compliant.
* | add "repository" permissions role and make sure we have a sane "accept" ↵friendica2014-10-271-2/+45
| | | | | | | | default for the custom role.
* | turn down the preview logging. Haven't needed that level of detail recently.friendica2014-10-261-2/+2
| |
* | put privacy role selector in settings page. Change visibility of various ↵friendica2014-10-262-5/+12
| | | | | | | | permissions items accordingly.
* | doh - this needs to be markdown, not bbcodefriendica2014-10-241-2/+2
| |
* | should probably check the body since the title is only going to be rarely set.friendica2014-10-241-1/+1
| |
* | don't decrypt the message body more than once.friendica2014-10-241-2/+7
| |
* | I'm speechless. This is just reckless. Set a context flag in text using a ↵friendica2014-10-231-2/+2
| | | | | | | | context trigger character which is likely to be present in that text already. Without escaping any previous instances of that character. Grrr.
* | generalise the output format of xchan_fetch so it matches the input formatfriendica2014-10-231-1/+11
| |
* | API: xchan get/createfriendica2014-10-232-1/+91
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-13 23:31:04 +0000