aboutsummaryrefslogtreecommitdiffstats
path: root/mod
Commit message (Collapse)AuthorAgeFilesLines
* indicate public forums in directory results (there will be some [possibly ↵friendica2014-11-102-0/+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-0/+16
| | | | other types of forums or weird custom channel permissions. If the channel is auto-accept and taggable, it's a public forum.
* class is a reserved wordfriendica2014-11-101-4/+4
|
* menu page cleanupfriendica2014-11-091-15/+17
|
* remove extraneous loggingfriendica2014-11-091-4/+1
|
* directory listing shows phantom keywordsfriendica2014-11-091-1/+3
|
* New layout for directoryStefan Parviainen2014-11-092-191/+49
|
* Merge https://github.com/friendica/red into pending_mergefriendica2014-11-071-5/+6
|\
| * provide lockstate for photo editmarijus2014-11-071-5/+6
| |
* | fix broken photo edits when adult flag is changedfriendica2014-11-071-8/+7
|/
* Provide a way to mark photos as adult and hide them from the default album ↵friendica2014-11-061-27/+31
| | | | 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.
* provide a lockstate for photo uploadsmarijus2014-11-061-1/+4
|
* crude skeleton for location manager and the UI sucks but at least it's on a ↵friendica2014-11-051-28/+42
| | | | webpage and you don't have to do it by hand.
* some minor cleanup of unreported (and as yet undiscovered) issues with ↵friendica2014-11-051-0/+1
| | | | 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.
* changed notification descriptionfriendica2014-11-041-1/+1
|
* minor adjustments to make the form work as designedfriendica2014-11-041-2/+3
|
* ok heads up - potentially destabilising change. I've tried to sort out all ↵friendica2014-11-041-10/+18
| | | | | | | | | | 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).
* configurable visual alerts/notificationsfriendica2014-11-042-72/+166
|
* wall posted comment to a top-level wall post which arrived via a route (e.g. ↵friendica2014-11-031-0/+3
| | | | was posted to a forum) had no route, hence downstream recipients report route mismatch
* if uploading a photo go away to albummarijus2014-11-031-2/+7
|
* if deleting a photo go away to albummarijus2014-11-031-1/+3
|
* even more photos workmarijus2014-11-011-11/+9
|
* check that we have valid datafriendica2014-11-011-10/+16
|
* do not reload page for photo uploadmarijus2014-10-311-12/+8
|
* more work on photo uploadmarijus2014-10-311-7/+5
|
* Merge https://github.com/friendica/red into pending_mergefriendica2014-10-301-36/+13
|\
| * some work on photo uploadmarijus2014-10-301-36/+13
| |
* | What this checkin does is catch the case where a comment arrived and there's ↵friendica2014-10-302-2/+16
| | | | | | | | 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.
* | allow feed pagingfriendica2014-10-291-0/+3
|/
* if any privacy tags are created on a top level post, restrict the post; ↵friendica2014-10-281-1/+14
| | | | since it could have been quite sensitive. If there were errors processing the actual tag restrict the post to the profile owner. Also make the "privacy tag over-rides ACL" behaviour configurable. Default is that privacy tags over-ride the ACL.
* Merge https://github.com/friendica/red into pending_mergefriendica2014-10-282-28/+65
|\
| * change the way tagrm works to allow tag removal on the flymarijus2014-10-282-28/+65
| |
* | change photo tag bubble tipfriendica2014-10-281-1/+1
|/
* several unrelated things - auto_follow wasn't working for new accounts, ↵friendica2014-10-272-5/+6
| | | | 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.
* Merge https://github.com/friendica/red into pending_mergefriendica2014-10-271-27/+21
|\
| * do not reload page for edit album and some minor cleanupmarijus2014-10-271-27/+21
| |
* | add "repository" permissions role and make sure we have a sane "accept" ↵friendica2014-10-271-0/+6
|/ | | | default for the custom role.
* a couple of photo tag issuesfriendica2014-10-262-23/+34
|
* couple of other places where we need to reset stuff completely if the role ↵friendica2014-10-261-6/+11
| | | | changes
* reset ACL just in case it was custom already.friendica2014-10-261-1/+1
|
* put privacy role selector in settings page. Change visibility of various ↵friendica2014-10-261-117/+107
| | | | permissions items accordingly.
* use intval rather than dbesc since these are ints. Should work regardless, ↵friendica2014-10-261-2/+2
| | | | but this makes it consistent with the way we do most other queries.
* Merge https://github.com/friendica/red into pending_mergefriendica2014-10-261-3/+37
|\ | | | | | | | | Conflicts: mod/like.php
| * some work on photos like/dislikemarijus2014-10-252-4/+37
| |
* | allow photos without comments to be likedfriendica2014-10-261-2/+15
|/
* make bbcode/html includes work in markdown help pages and vice versazottel2014-10-241-7/+19
|
* Issue #661Thomas Willingham2014-10-241-1/+1
|
* don't offer forum (@name+) completion in comments, since it won't do anything.friendica2014-10-231-2/+2
|
* improved wall-to-wall detection for comments so we can handle Diaspora ↵friendica2014-10-221-6/+16
| | | | | | | signing and wall-to-wall attribution correctly. Do it at the point of submission. This also fixes a potential bug in yesterday's wall-to-wall permission setting, if it was a local comment to a remote post.
* Merge pull request #655 from pafcu/masterRedMatrix2014-10-221-7/+26
|\ | | | | Better handling of incorrect info entered in event
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-22 10:37:35 +0000