aboutsummaryrefslogtreecommitdiffstats
path: root/include
Commit message (Collapse)AuthorAgeFilesLines
* try to fix bad addresses that got into the networkfriendica2013-08-251-0/+3
|
* Try to ensure full paths don't leak into xchan_addr and hubloc_addrfriendica2013-08-251-1/+1
|
* extra logging for translating likes in notification emails - which is still ↵friendica2013-08-221-0/+3
| | | | failing on occasion.
* possible fix for mention tags not posting to mentioned forum (when send ↵friendica2013-08-221-3/+25
| | | | stream permission is blocked)
* add detailed logging to public recips - find out why some public recipients ↵friendica2013-08-221-0/+3
| | | | are getting bypassed (David Benfells' problem with tagging groups, etc.)
* make premium channels a featurefriendica2013-08-221-2/+1
|
* add zid to connect_urlfriendica2013-08-221-1/+1
|
* premium/restricted channel connections implemented, configure at ↵friendica2013-08-212-2/+14
| | | | yoursite/channel/nickname - this basically redirects "follow" requests to a premium channel's sell page if it has one configured. You can still click through and create a connection request (introduction), but this provides a means for the channel owner to state their terms. If you don't abide by the terms, you will likely be blocked or the channel deleted. This facility is extensible in a number of ways.
* progress on generic sellpage - is not yet linked from existing connect ↵friendica2013-08-211-1/+2
| | | | buttons and editing has not been completed
* implement premium channel discoveryfriendica2013-08-211-5/+14
|
* fix superblock for commentsfriendica2013-08-202-2/+16
|
* email attachments (and fix email photos)friendica2013-08-192-2/+57
|
* localize_item() thinks all likes on posts are likes on comments because we ↵friendica2013-08-191-1/+1
| | | | didn't pass any info in the activity object to distinguish them from each other.
* some sane permission defaults.friendica2013-08-183-4/+51
|
* 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.
* Issue #99Thomas Willingham2013-08-181-0/+1
|
* get rid of more variables with dashes in the names - use underscore *except* ↵friendica2013-08-153-4/+4
| | | | in CSS. These were probably already here, but if you see any - please keep them out of PHP and MySQL where they sometimes get interpreted as a subtraction operation and are a bugger to find.
* Merge pull request #98 from cvogeley/masterfriendica2013-08-151-0/+2
|\ | | | | Partial fix for Issue #97
| * Fix Load mobile themeChristian Vogeley2013-08-161-0/+2
| |
* | don't include archived contacts in public posts, unless specifically requestedfriendica2013-08-152-4/+5
| |
* | issues marking for deathfriendica2013-08-151-14/+15
|/
* Merge pull request #96 from beardy-unixer/masterfriendica2013-08-141-0/+39
|\ | | | | Webpages
| * More progress on pages - extend writepages widget, add pagelist widgetThomas Willingham2013-08-141-2/+29
| |
| * Merge remote-tracking branch 'upstream/master'Thomas Willingham2013-08-147-31/+364
| |\
| * | Initial shot at write_pages widgetThomas Willingham2013-08-101-0/+12
| | |
* | | most of expire is now ported from friendica, but the protocol bits to push ↵friendica2013-08-143-6/+19
| |/ |/| | | | | out the delete notifications for the entire batch to all recipients of the original post are not complete and will take quite a bit more work. As a consequence, expire has been completely disabled until it is fully implmented since it could result in completely un-removable posts reminiscent of the infamous "Bonnie Nadri" incident at Diaspora which we do not wish to re-live.
* | 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
* | menu management is now functional with the exception of acl's (and of course ↵friendica2013-08-131-1/+3
| | | | | | | | a way to display the menus you create, and probably a bit more input sanity checking)
* | menu management complete (as opposed to menu *content* management, which is ↵friendica2013-08-131-0/+23
| | | | | | | | not). As usual, this means functionally complete - as theming and presentation have been left for those more suited to the task.
* | debugging issue #58 - seems to work but needs (more) themingfriendica2013-08-131-3/+10
| |
* | untested patch for issue #58 - will require theming if it worksfriendica2013-08-131-0/+18
| |
* | a bit more work on menusfriendica2013-08-131-0/+8
| |
* | block content-type (called ITEM_BUILDBLOCK to avoid confusion with content ↵friendica2013-08-121-0/+5
| | | | | | | | that is blocked)
* | more menu manage functions - should be everything we need to get startedfriendica2013-08-111-0/+187
| |
* | debugging user menusfriendica2013-08-111-6/+4
| |
* | check these in so I can go back and find out why the stylsheet is horkedfriendica2013-08-111-0/+40
| |
* | Merge https://github.com/friendica/red into zpullfriendica2013-08-111-0/+1
|\ \
| * | Missing include for new_keypairThomas Willingham2013-08-101-0/+1
| |/
* | important bits we need to allow php executable content. These must be ↵friendica2013-08-112-18/+51
| | | | | | | | 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.
* | don't import any hubloc that doesn't have a sitekey. Eventually we should ↵friendica2013-08-111-2/+7
|/ | | | also verify that it is a valid key, as we've already seen one case where one character got mangled and messed up communication.
* move sitekey creation to the account creation function instead of during ↵friendica2013-08-092-9/+7
| | | | 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
* malformed ru string filefriendica2013-08-081-1/+1
|
* Add public visibility setting to privacy groups (collections). This doesn't ↵friendica2013-08-071-3/+4
| | | | yet make them visible, but allows them to be visible (like a Cc: instead of a Bcc:)
* remove some un-needed codefriendica2013-08-071-1320/+10
|
* big changes to photo->store() which is now photo->save() and takes an array ↵friendica2013-08-072-10/+136
| | | | instead of a list of args. Also the beginning of the migration to using photo_flags to indicate special purpose photos such as profile photos and contact photos and "thing" photos.
* convert all stored json calls to json_decode_plus()friendica2013-08-065-22/+22
|
* we've been storing json_encoded structures on disk in several places because ↵friendica2013-08-063-6/+13
| | | | it's a lot easier to parse than xml - but OMG do they get mangled - stored as single quoted strings when escaped as if double quoted. We need to use my new function json_decode_plus() wherever we need to parse one of these babies to make sure we get it right. Maybe we should've just used serialize().
* add extra logging to tag_deliverfriendica2013-08-051-2/+6
|